mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Note explicitly that hash indexes are also not replicated because they're not

Browse Source 
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.
This commit is contained in:
Heikki Linnakangas 2010-10-26 22:50:31 +03:00
parent 3579a94d6a
commit 5c38782cc8
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/src/sgml/high-availability.sgml
View File

@ -1845,8 +1845,7 @@ LOG: database system is ready to accept read only connections
<listitem> <listitem>
<para> <para>
Operations on hash indexes are not presently WAL-logged, so Operations on hash indexes are not presently WAL-logged, so
replay will not update these indexes. Hash indexes will not be replay will not update these indexes.
used for query plans during recovery.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>

9
doc/src/sgml/indices.sgml
View File

@ -187,14 +187,15 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
</synopsis> </synopsis>
</para> </para>
<note> <caution>
<para> <para>
Hash index operations are not presently WAL-logged, Hash index operations are not presently WAL-logged,
so hash indexes might need to be rebuilt with <command>REINDEX</> so hash indexes might need to be rebuilt with <command>REINDEX</>
after a database crash. after a database crash. They are also not replicated over streaming or
For this reason, hash index use is presently discouraged. file-based replication.
For these reasons, hash index use is presently discouraged.
</para> </para>
</note> </caution>
<para> <para>
<indexterm> <indexterm>