From 03a68a7caee0f1e2ebc537ed8bb2c7dde166c091 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 26 Sep 2006 11:18:29 +0000 Subject: Done: < o Add command to archive partially filled 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. < Reorder: < o %Create dump tool for write-ahead logs for use in determining < transaction id for point-in-time recovery > o %Create dump tool for write-ahead logs for use in determining > transaction id for point-in-time recovery --- doc/src/FAQ/TODO.html | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 5f7754cc015..b4a5c37f79b 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: Wed Sep 20 19:01:42 EDT 2006 +Last updated: Tue Sep 26 07:18:13 EDT 2006

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

Point-In-Time Recovery (PITR)

Add command to archive partially filled 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. -
-
%Create dump tool for write-ahead logs for use in determining - transaction id for point-in-time recovery -
Allow a warm standby system to also allow read-only statements +
Allow a warm standby system to also allow read-only statements [pitr]
This is useful for checking PITR recovery.
+
%Create dump tool for write-ahead logs for use in determining + transaction id for point-in-time recovery
Allow the PITR process to be debugged and data examined

-- cgit v1.2.3