Skip to content

Commit 8515efa

Browse files
committed
Add some notes about unimplemented aspects of PITR backup/recovery.
1 parent 576856b commit 8515efa

File tree

1 file changed

+30
-1
lines changed

1 file changed

+30
-1
lines changed

doc/src/sgml/backup.sgml

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.41 2004/08/03 23:42:59 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.42 2004/08/04 17:37:09 tgl Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -891,6 +891,35 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
891891
timelines that branched off earlier than the base backup.
892892
</para>
893893
</sect2>
894+
895+
<sect2 id="backup-online-caveats">
896+
<title>Caveats</title>
897+
898+
<para>
899+
At this writing, there are several limitations of the on-line backup
900+
technique. These will probably be fixed in future releases.
901+
902+
<itemizedlist>
903+
<listitem>
904+
<para>
905+
The effects of <command>CREATE DATABASE</>, <command>DROP DATABASE</>,
906+
<command>CREATE TABLESPACE</>, and <command>DROP TABLESPACE</> are
907+
not fully reflected in the WAL log. It is recommended that you take
908+
a new base backup after performing one of these operations.
909+
</para>
910+
</listitem>
911+
<listitem>
912+
<para>
913+
Operations on non-btree indexes (hash, R-tree, and GiST indexes) are
914+
not presently WAL-logged, so replay will not update these index types.
915+
The recommended workaround, if you use any non-btree indexes, is to
916+
manually <command>REINDEX</> each such index after completing a
917+
recovery operation.
918+
</para>
919+
</listitem>
920+
</itemizedlist>
921+
</para>
922+
</sect2>
894923
</sect1>
895924

896925
<sect1 id="migration">

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy