diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-10-26 22:50:31 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-10-26 22:53:41 +0300 |
| commit | 5c38782cc8b3219d43ac2ccaf4254fd590bde758 (patch) | |
| tree | dc49e1b3e03a54a68d3de3a1aab0840cc03fbb2a /doc/src | |
| parent | 3579a94d6acd9374fbc3b45d0be593331ffd414d (diff) | |
| download | postgresql-5c38782cc8b3219d43ac2ccaf4254fd590bde758.tar.gz postgresql-5c38782cc8b3219d43ac2ccaf4254fd590bde758.zip | |
Note explicitly that hash indexes are also not replicated because they're not
WAL-logged. Make the notice about the lack of WAL-logging more visible by
making it a <caution>. Also remove the false statement from hot standby
caveats section that hash indexes are not used during hot standby.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 3 | ||||
| -rw-r--r-- | doc/src/sgml/indices.sgml | 9 |
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 1f5ec85ecae..bbcc6b68220 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1845,8 +1845,7 @@ LOG: database system is ready to accept read only connections <listitem> <para> Operations on hash indexes are not presently WAL-logged, so - replay will not update these indexes. Hash indexes will not be - used for query plans during recovery. + replay will not update these indexes. </para> </listitem> <listitem> diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml index 15c3320e2fd..98d5b38ed6c 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -187,14 +187,15 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> </synopsis> </para> - <note> + <caution> <para> Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with <command>REINDEX</> - after a database crash. - For this reason, hash index use is presently discouraged. + after a database crash. They are also not replicated over streaming or + file-based replication. + For these reasons, hash index use is presently discouraged. </para> - </note> + </caution> <para> <indexterm> |