mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update PITR setence to mention WAL and file system dump.

Browse Source
This commit is contained in:
Bruce Momjian 2005-04-18 17:40:40 +00:00
parent 7aa066f11d
commit 01979d1bd5
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Mon Apr 18 10:42:34 EDT 2005
Last updated: Mon Apr 18 11:03:14 EDT 2005
</p>
<p>The most recent version of this document can be viewed at the PostgreSQL web<br/>
site, <a href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</a>.
@ -103,10 +103,10 @@ first.
logs
<p> Currently only full WAL files are archived. This means that the most
recent transactions aren't available for recovery in case of a disk
failure.
failure. This could be triggered by a user command or a timer.
</p>
</li><li>Force archiving of partially-full WAL files when pg_stop_backup() is
called or the server is stopped
</li><li>Automatically force archiving of partially-filled WAL files when
pg_stop_backup() is called or the server is stopped
<p> Doing this will allow administrators to know more easily when the
archive contins all the files needed for point-in-time recovery.
</p>

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

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.63 2005/04/18 13:11:04 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.64 2005/04/18 17:40:40 momjian Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@ -741,10 +741,10 @@ SELECT pg_stop_backup();
<literal>0000000100001234000055CD.007C9330.backup</>. (The second
number in the file name stands for an exact position within the WAL
file, and can ordinarily be ignored.) Once you have safely archived
the WAL segment files used during the file system backup (as
specified in the backup history file), you can delete all archived
WAL segments with names numerically less. Keep in mind that only
completed WAL segment files are archived, so there will be delay
the file system backup and the WAL segment files used during the
backup (as specified in the backup history file), you can delete all
archived WAL segments with names numerically less. Keep in mind that
only completed WAL 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.