| PostgreSQL 8.2.3 Documentation | ||||
|---|---|---|---|---|
| Prev | Fast Backward | Chapter 50. GiST Indexes | Fast Forward | Next |
Usually, replay of the WAL log is sufficient to restore the integrity of a GiST index following a database crash. However, there are some corner cases in which the index state is not fully rebuilt. The index will still be functionally correct, but there may be some performance degradation. When this occurs, the index can be repaired by VACUUMing its table, or by rebuilding the index using REINDEX. In some cases a plain VACUUM is not sufficient, and either VACUUM FULL or REINDEX is needed. The need for one of these procedures is indicated by occurrence of this log message during crash recovery:
LOG: index NNN/NNN/NNN needs VACUUM or REINDEX to finish crash recovery
or this log message during routine index insertions:
LOG: index "FOO" needs VACUUM or REINDEX to finish crash recovery
If a plain VACUUM finds itself unable to complete recovery fully, it will return a notice:
NOTICE: index "FOO" needs VACUUM FULL or REINDEX to finish crash recovery
No comments could be found for this page.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
In order to submit a comment, you must have a community account.
* denotes required field