|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.143 2010/02/2211:47:30 heikki Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.144 2010/02/2217:15:10 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="backup"> |
4 | 4 | <title>Backup and Restore</title> |
@@ -484,6 +484,16 @@ tar -cf backup.tar /usr/local/pgsql/data |
484 | 484 | </itemizedlist> |
485 | 485 | </para> |
486 | 486 |
|
| 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 | + |
487 | 497 | <para> |
488 | 498 | As with the plain file-system-backup technique, this method can only |
489 | 499 | support restoration of an entire database cluster, not a subset. |
@@ -744,7 +754,9 @@ SELECT pg_start_backup('label', true); |
744 | 754 | <listitem> |
745 | 755 | <para> |
746 | 756 | 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 |
748 | 760 | necessary nor desirable to stop normal operation of the database |
749 | 761 | while you do this. |
750 | 762 | </para> |
|