> 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.
(<a href="http://postgresguide.com/performance/indexes.html#primary-keys-and-indexes" rel="nofollow">http://postgresguide.com/performance/indexes.html#primary-ke...</a>)<p>This directly contradicts with what the PostgreSQL documentation says.<p>> Adding a primary key will automatically create a unique btree index on the column or group of columns used in the primary key.
(<a href="http://www.postgresql.org/docs/9.1/interactive/ddl-constraints.html#AEN2493" rel="nofollow">http://www.postgresql.org/docs/9.1/interactive/ddl-constrain...</a>)<p>Is there a fundamental difference to the default pkey index versus an explicitly created index?
They ink to PostgreSQL 9.0 High Performance (<a href="http://www.amazon.com/gp/product/184951030X/" rel="nofollow">http://www.amazon.com/gp/product/184951030X/</a>), which I agree is a great book if you're a sysadmin supporting PostgreSQL.
"Curated"? As opposed to a what, an automatically generated one?<p>SELECT RANDOM(GUIDE) FROM DATABASES WHERE DATABASE_NAME = 'POSTGRES'; ?!<p>The original article, thankfully, says nothing about being "curated".