aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/backup.sgml14
1 files changed, 3 insertions, 11 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 7a3c4f73ff9..af06249203a 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.46 2004/08/08 04:34:43 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.47 2004/08/29 21:08:47 tgl Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -902,19 +902,11 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
<para>
At this writing, there are several limitations of the on-line backup
- technique. These will probably be fixed in future releases.
+ technique. These will probably be fixed in future releases:
<itemizedlist>
<listitem>
<para>
- The effects of <command>CREATE DATABASE</>, <command>DROP DATABASE</>,
- <command>CREATE TABLESPACE</>, and <command>DROP TABLESPACE</> are
- not fully reflected in the WAL log. It is recommended that you take
- a new base backup after performing one of these operations.
- </para>
- </listitem>
- <listitem>
- <para>
Operations on non-btree indexes (hash, R-tree, and GiST indexes) are
not presently WAL-logged, so replay will not update these index types.
The recommended workaround, if you use any non-btree indexes, is to
@@ -932,7 +924,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
since we may need to fix partially-written disk pages. It is not
necessary to store so many page copies for PITR operations, however.
An area for future development is to compress archived WAL data by
- removing unnecesssary page copies.
+ removing unnecessary page copies.
</para>
</sect2>
</sect1>