From 5ffa0bb47a3ca975f257d665e38f2ba89625e112 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 26 Jul 2006 17:23:02 +0000 Subject: [PATCH] Reorder items: < o Allow point-in-time recovery to archive partially filled < write-ahead logs? [pitr] > o Add command to archive partially filled write-ahead logs? [pitr] < of a disk failure. This could be triggered by a user command or < a timer. > of a disk failure. < recovery. A function call to do this would also be useful. > recovery. > o Add reporting of the current WAL file and offset, perhaps as > part of partial log file archiving > > The offset allows parts of a WAL file to be archived using > an external program. > < o Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < < The offset allows parts of a WAL file to be archived using < an external program. --- doc/TODO | 21 ++++++++++----------- doc/src/FAQ/TODO.html | 20 +++++++++----------- 2 files changed, 19 insertions(+), 22 deletions(-) diff --git a/doc/TODO b/doc/TODO index 12be227361..0733e9227d 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Tue Jul 25 20:34:56 EDT 2006 +Last updated: Wed Jul 26 13:22:49 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -144,22 +144,26 @@ Administration * Point-In-Time Recovery (PITR) - o Allow point-in-time recovery to archive partially filled - write-ahead logs? [pitr] + 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. This could be triggered by a user command or - a timer. + of a disk failure. o Automatically force archiving of partially-filled WAL files when 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. A function call to do this would also be useful. + recovery. http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php + o Add reporting of the current WAL file and offset, perhaps as + part of partial log file archiving + + The offset allows parts of a WAL file to be archived using + an external program. + o %Create dump tool for write-ahead logs for use in determining transaction id for point-in-time recovery o Allow a warm standby system to also allow read-only statements @@ -168,11 +172,6 @@ Administration This is useful for checking PITR recovery. o Allow the PITR process to be debugged and data examined - o Add reporting of the current WAL file and offset, perhaps as - part of partial log file archiving - - The offset allows parts of a WAL file to be archived using - an external program. Monitoring diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 79d37480c1..816047e113 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 20:34:56 EDT 2006 +Last updated: Wed Jul 26 13:22:49 EDT 2006

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

  • Point-In-Time Recovery (PITR)

    • Monitoring

    -- 2.40.0