|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/create_index.sgml,v 1.60 2007/01/31 23:26:03 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/create_index.sgml,v 1.61 2007/04/03 22:38:35 momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -332,7 +332,20 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] <replaceable class="parameter">name</re |
332 | 332 | uniqueness violation in a unique index, the <command>CREATE INDEX</> |
333 | 333 | command will fail but leave behind an <quote>invalid</> index. This index |
334 | 334 | will be ignored for querying purposes because it might be incomplete; |
335 | | - however it will still consume update overhead. The recommended recovery |
| 335 | + however it will still consume update overhead. The <application>psql</> |
| 336 | + <command>\d</> command will mark such an index as <literal>INVALID</>: |
| 337 | + |
| 338 | +<programlisting> |
| 339 | +postgres=# \d tab |
| 340 | + Table "public.tab" |
| 341 | + Column | Type | Modifiers |
| 342 | +--------+---------+----------- |
| 343 | + col | integer | |
| 344 | +Indexes: |
| 345 | + "idx" btree (col) INVALID |
| 346 | +</programlisting> |
| 347 | + |
| 348 | + The recommended recovery |
336 | 349 | method in such cases is to drop the index and try again to perform |
337 | 350 | <command>CREATE INDEX CONCURRENTLY</>. (Another possibility is to rebuild |
338 | 351 | the index with <command>REINDEX</>. However, since <command>REINDEX</> |
|