Commitf0e7f9e

committed

Update text that stated GiST indexes aren't WAL-logged.

1 parentd544ec8 commitf0e7f9eCopy full SHA for f0e7f9e

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,5 @@`
`1`	`1`	`<!--`
`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 $`
`3`	`3`	`-->`
`4`	`4`	`<chapter id="backup">`
`5`	`5`	`<title>Backup and Restore</title>`
`@@ -1136,7 +1136,7 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows`
`1136`	`1136`	`<itemizedlist>`
`1137`	`1137`	`<listitem>`
`1138`	`1138`	`<para>`
`1139`		`- Operations onnon-B-tree indexes (hash,R-tree, and GiSTindexes) are`
	`1139`	`+ Operations on hash andR-treeindexes are`
`1140`	`1140`	`not presently WAL-logged, so replay will not update these index types.`
`1141`	`1141`	`The recommended workaround is to manually <command>REINDEX</> each`
`1142`	`1142`	`such index after completing a recovery operation.`

Comments

(0)