Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dd1486c

Browse files
committed
Briefly document in two places that pg_dump and pg_dumpall cannot be
used for continuous archiving.
1 parent 9dd6c46 commit dd1486c

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

doc/src/sgml/backup.sgml

+14-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.143 2010/02/22 11:47:30 heikki Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.144 2010/02/22 17:15:10 momjian Exp $ -->
22

33
<chapter id="backup">
44
<title>Backup and Restore</title>
@@ -484,6 +484,16 @@ tar -cf backup.tar /usr/local/pgsql/data
484484
</itemizedlist>
485485
</para>
486486

487+
<note>
488+
<para>
489+
<application>pg_dump</application> and
490+
<application>pg_dumpall</application> do not produce file-system-level
491+
backups and cannot be used as part of a continuous-archiving solution.
492+
Such dumps are <emphasis>logical</> and do not contain enough
493+
information to used by WAL reply.
494+
</para>
495+
</note>
496+
487497
<para>
488498
As with the plain file-system-backup technique, this method can only
489499
support restoration of an entire database cluster, not a subset.
@@ -744,7 +754,9 @@ SELECT pg_start_backup('label', true);
744754
<listitem>
745755
<para>
746756
Perform the backup, using any convenient file-system-backup tool
747-
such as <application>tar</> or <application>cpio</>. It is neither
757+
such as <application>tar</> or <application>cpio</> (not
758+
<application>pg_dump</application> or
759+
<application>pg_dumpall</application>). It is neither
748760
necessary nor desirable to stop normal operation of the database
749761
while you do this.
750762
</para>

0 commit comments

Comments
 (0)