From: Heikki Linnakangas Date: Tue, 26 Oct 2010 19:50:31 +0000 (+0300) Subject: Note explicitly that hash indexes are also not replicated because they're not X-Git-Tag: REL9_0_2~46 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=b887f7b3526627d22d01d0cdb74a21ead08934a7;p=pg-rex%2Fsyncrep.git 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 . Also remove the false statement from hot standby caveats section that hash indexes are not used during hot standby. --- diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index eabd844fa3..74684f7d0c 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 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. diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml index a28f1dba51..1b02f5f563 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -187,14 +187,15 @@ CREATE INDEX name ON table - + Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with 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. - +