database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-29 10:41:53 +03:00
Code Activity

Remove inaccurate "Incrementally Updated Backups" documentation section;

Browse Source 
already removed from 9.0+.

Applied to 8.3 and 8.4.
This commit is contained in:
Bruce Momjian
2012-11-26 17:36:21 -05:00
parent 60511606fb
commit 67b5effe8c
1 changed files with 0 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1856,46 +1856,6 @@ if (!triggered)
</para> </para>
</sect2> </sect2>
<sect2 id="backup-incremental-updated">
<title>Incrementally Updated Backups</title>
<indexterm zone="backup">
<primary>incrementally updated backups</primary>
</indexterm>
<indexterm zone="backup">
<primary>change accumulation</primary>
</indexterm>
<para>
In a warm standby configuration, it is possible to offload the expense of
taking periodic base backups from the primary server; instead base backups
can be made by backing
up a standby server's files. This concept is generally known as
incrementally updated backups, log change accumulation, or more simply,
change accumulation.
</para>
<para>
If we take a backup of the standby server's data directory while it is processing
logs shipped from the primary, we will be able to reload that data and
restart the standby's recovery process from the last restart point.
We no longer need to keep WAL files from before the restart point.
If we need to recover, it will be faster to recover from the incrementally
updated backup than from the original base backup.
</para>
<para>
Since the standby server is not <quote>live</>, it is not possible to
use <function>pg_start_backup()</> and <function>pg_stop_backup()</>
to manage the backup process; it will be up to you to determine how
far back you need to keep WAL segment files to have a recoverable
backup. You can do this by running <application>pg_controldata</>
on the standby server to inspect the control file and determine the
current checkpoint WAL location, or by using the
<varname>log_checkpoints</> option to print values to the server log.
</para>
</sect2>
</sect1> </sect1>
<sect1 id="migration"> <sect1 id="migration">