Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit f0e7f9e

Browse files
committed
Update text that stated GiST indexes aren't WAL-logged.
1 parent d544ec8 commit f0e7f9e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/backup.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.65 2005/04/19 01:39:50 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.66 2005/06/20 13:52:17 tgl Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -1136,7 +1136,7 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows
11361136
<itemizedlist>
11371137
<listitem>
11381138
<para>
1139-
Operations on non-B-tree indexes (hash, R-tree, and GiST indexes) are
1139+
Operations on hash and R-tree indexes are
11401140
not presently WAL-logged, so replay will not update these index types.
11411141
The recommended workaround is to manually <command>REINDEX</> each
11421142
such index after completing a recovery operation.

0 commit comments

Comments
 (0)