From cb6f5f1552d1dbba2465f513c75c1335d0a446d3 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 25 Jul 2006 15:21:48 +0000 Subject: Update PITR: < write-ahead logs [pitr] > write-ahead logs? [pitr] < recovery. > recovery. A function call to do this would also be useful. --- doc/src/FAQ/TODO.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 9ddd24a2f78..f5d4489f4c8 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Tue Jul 25 00:11:20 EDT 2006 +Last updated: Tue Jul 25 11:21:42 EDT 2006

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -132,7 +132,7 @@ first.

Point-In-Time Recovery (PITR)

Allow point-in-time recovery to archive partially filled - write-ahead logs [pitr] + write-ahead logs? [pitr]
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. This could be triggered by a user command or @@ -142,7 +142,7 @@ first. pg_stop_backup() is called or the server is stopped
Doing this will allow administrators to know more easily when the archive contains all the files needed for point-in-time - recovery. + recovery. A function call to do this would also be useful. http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
%Create dump tool for write-ahead logs for use in determining -- cgit v1.2.3