SELECT RANDOM(GUIDE) FROM DATABASES WHERE DATABASE_NAME = 'POSTGRES'; ?!
The original article, thankfully, says nothing about being "curated".
11–14 of 14 posts
SELECT RANDOM(GUIDE) FROM DATABASES WHERE DATABASE_NAME = 'POSTGRES'; ?!
The original article, thankfully, says nothing about being "curated".
> Its of note that Postgres does not automatically create an index when creating the primary key, it is a separate step which you must do if not using an ORM. ( http://postgresguide.com/performance/indexes.html#primary-ke... ) This directly contradicts with what the PostgreSQL documentation says. > Adding a primary key will automatically create a unique btree index on the column or group of columns used in the primar…
perhaps he meant a foreign key, not primary key. postgresql doesn't automatically create indexes for foreign keys. > Is there a fundamental difference to the default pkey index versus an explicitly created index? i don't know of any in practice.
It might make a difference in the heuristic for finding functional dependencies for group by though. This feature was introduced in 9.1 and allows one to not always have to list all columns in the GROUP BY clause.
While the idea is nice, please note that the official name is PostgreSQL and Postgres is an accepted alias. "Postgre SQL" is just plain wrong.
It's wrong, but probably unavoidable. Attaching a spoken acronym to the end of a pronounced name is just so bizarre (has anyone else ever done that?) that people will simply skip it. I've heard people say "post-gre", and like a new English speaker saying "We goed to the park", this overgeneralization isn't at all surprising. In computers, acronyms after names are very common, and it's typically harmless to omit them,…
I frequently, but not exclusively, say it like that. You knew someone would show up to say this. I admit I get weird looks. My coworkers all call it "Postgres."
I think you're right, but I also think if that's the best thing we have to complain about we have it pretty good.
They ink to PostgreSQL 9.0 High Performance ( http://www.amazon.com/gp/product/184951030X/ ), which I agree is a great book if you're a sysadmin supporting PostgreSQL.
what's up w the third book link tho? some crappy book by a guy named CJ