From 8515efa128ccc415ebbf9144082ee2ce836733d9 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 4 Aug 2004 17:37:09 +0000
Subject: [PATCH] Add some notes about unimplemented aspects of PITR
backup/recovery.
---
doc/src/sgml/backup.sgml | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 3b45ec17def..49b3afa4f73 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.41 2004/08/03 23:42:59 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.42 2004/08/04 17:37:09 tgl Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -891,6 +891,35 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
timelines that branched off earlier than the base backup.
</para>
</sect2>
+
+ <sect2 id="backup-online-caveats">
+ <title>Caveats</title>
+
+ <para>
+ At this writing, there are several limitations of the on-line backup
+ 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
+ manually <command>REINDEX</> each such index after completing a
+ recovery operation.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect2>
</sect1>
<sect1 id="migration">
--
GitLab