database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-18 12:22:09 +03:00
Code Activity

Update PITR wording, per Simon.

Browse Source
This commit is contained in:
Bruce Momjian
2005-04-19 01:40:02 +00:00
parent 92645c42c8
commit 0a2400e964
1 changed files with 17 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.54.4.4 2005/04/18 01:29:08 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.54.4.5 2005/04/19 01:40:02 momjian Exp $
--> -->
<chapter id="backup"> <chapter id="backup">
<title>Backup and Restore</title> <title>Backup and Restore</title>
@@ -688,7 +688,13 @@ SELECT pg_start_backup('label');
<programlisting> <programlisting>
SELECT pg_stop_backup(); SELECT pg_stop_backup();
</programlisting> </programlisting>
If this returns successfully, you're done. This should return successfully.
</para>
</listitem>
<listitem>
<para>
Once the WAL segment files used during the backup are archived as part
of normal database activity, you are done.
</para> </para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@@ -735,13 +741,15 @@ SELECT pg_stop_backup();
<literal>0000000100001234000055CD.007C9330.backup</>. (The second <literal>0000000100001234000055CD.007C9330.backup</>. (The second
number in the file name stands for an exact position within the WAL number in the file name stands for an exact position within the WAL
file, and can ordinarily be ignored.) Once you have safely archived file, and can ordinarily be ignored.) Once you have safely archived
the WAL segment files used during the file system backup (as the file system backup and the WAL segment files used during the
specified in the backup history file), you can delete all archived backup (as specified in the backup history file), all archived WAL
WAL segments with names numerically less. Keep in mind that only segments with names numerically less are no longer needed to recover
completed WAL segment files are archived, so there will be delay the file system backup and may be deleted. However, you should
between running <function>pg_stop_backup</> and the archiving of consider keeping several backup sets to be absolutely certain that
all WAL segment files needed to make the file system backup you are can recover your data. Keep in mind that only completed WAL
consistent. segment files are archived, so there will be delay between running
<function>pg_stop_backup</> and the archiving of all WAL segment
files needed to make the file system backup consistent.
</para> </para>
<para> <para>
The backup history file is just a small text file. It contains the The backup history file is just a small text file. It contains the