mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add some notes about unimplemented aspects of PITR backup/recovery.

Browse Source
This commit is contained in:
Tom Lane 2004-08-04 17:37:09 +00:00
parent 576856b698
commit 8515efa128
1 changed files with 30 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
doc/src/sgml/backup.sgml
View File

@ -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">