Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit075c0ca

Browse files
committed
Document WAL recovery now uses checkpoints.
Simon Riggs
1 parent83078e9 commit075c0ca

File tree

1 file changed

+19
-3
lines changed

1 file changed

+19
-3
lines changed

‎doc/src/sgml/backup.sgml

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.83 2006/08/17 23:04:02 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.84 2006/09/15 21:55:07 momjian Exp $ -->
22

33
<chapter id="backup">
44
<title>Backup and Restore</title>
@@ -855,7 +855,9 @@ SELECT pg_stop_backup();
855855
<listitem>
856856
<para>
857857
Start the server. The server will go into recovery mode and
858-
proceed to read through the archived WAL files it needs. Upon completion
858+
proceed to read through the archived WAL files it needs. Should the
859+
recovery be terminated because of an external error, the server can
860+
simply be restarted and it will continue recovery. Upon completion
859861
of the recovery process, the server will rename
860862
<filename>recovery.conf</> to <filename>recovery.done</> (to prevent
861863
accidentally re-entering recovery mode in case of a crash later) and then
@@ -935,7 +937,21 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
935937
recover to such a time, you must go back to your previous base backup
936938
and roll forward from there.)
937939
</para>
938-
</note>
940+
</note>
941+
942+
<para>
943+
If recovery finds a corruption in the WAL data then recovery will
944+
complete at that point and the server will not start. The recovery
945+
process could be re-run from the beginning, specifying a
946+
<quote>recovery target</> so that recovery can complete normally.
947+
If recovery fails for an external reason, such as a system crash or
948+
the WAL archive has become inaccessible, then the recovery can be
949+
simply restarted and it will restart almost from where it failed.
950+
Restartable recovery works by writing a restartpoint record to the control
951+
file at the first safely usable checkpoint record found after
952+
<varname>checkpoint_timeout</> seconds.
953+
</para>
954+
939955

940956
<sect3 id="recovery-config-settings" xreflabel="Recovery Settings">
941957
<title>Recovery Settings</title>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp