A doc patch to add an example of what an invalid index looks like in psql, as requested by a commenter and Bruce. Index: doc/src/sgml/ref/create_index.sgml =================================================================== RCS file: /home/stark/src/REPOSITORY/pgsql/doc/src/sgml/ref/create_index.sgml,v retrieving revision 1.60 diff -c -r1.60 create_index.sgml *** doc/src/sgml/ref/create_index.sgml 31 Jan 2007 23:26:03 -0000 1.60 --- doc/src/sgml/ref/create_index.sgml 3 Apr 2007 17:19:25 -0000 *************** *** 332,338 **** uniqueness violation in a unique index, the CREATE INDEX command will fail but leave behind an invalid index. This index will be ignored for querying purposes because it might be incomplete; ! however it will still consume update overhead. The recommended recovery method in such cases is to drop the index and try again to perform CREATE INDEX CONCURRENTLY. (Another possibility is to rebuild the index with REINDEX. However, since REINDEX --- 332,352 ---- uniqueness violation in a unique index, the CREATE INDEX command will fail but leave behind an invalid index. This index will be ignored for querying purposes because it might be incomplete; ! however it will still consume update overhead. The psql ! \d command will mark such an index as INVALID: ! ! ! postgres=# \d tab ! Table "public.tab" ! Column | Type | Modifiers ! --------+---------+----------- ! col | integer | ! Indexes: ! "idx" btree (col) INVALID ! ! ! The recommended recovery method in such cases is to drop the index and try again to perform CREATE INDEX CONCURRENTLY. (Another possibility is to rebuild the index with REINDEX. However, since REINDEX -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate