From: Bruce Momjian Date: Tue, 8 Aug 2006 17:40:02 +0000 (+0000) Subject: Done: X-Git-Tag: REL8_2_BETA1~377 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2392cdb7956dccb115835b605bd1ead4289998b6;p=thirdparty%2Fpostgresql.git Done: < o Automatically force archiving of partially-filled WAL files when > o -Automatically force archiving of partially-filled WAL files when < < Doing this will allow administrators to know more easily when < the archive contains all the files needed for point-in-time < recovery. < http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < < o Add reporting of the current WAL file and offset, perhaps as > o -Add reporting of the current WAL file and offset, perhaps as < < The offset allows parts of a WAL file to be archived using < an external program. < --- diff --git a/doc/TODO b/doc/TODO index 4e50dbedbdd..93e22857b51 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Mon Aug 7 21:24:28 EDT 2006 +Last updated: Tue Aug 8 13:39:58 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -151,20 +151,10 @@ Administration most recent transactions aren't available for recovery in case of a disk failure. - o Automatically force archiving of partially-filled WAL files when + 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. - http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php - - o Add reporting of the current WAL file and offset, perhaps as + 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index baf2b3e28e4..f070fa8a2ea 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: Mon Aug 7 21:24:28 EDT 2006 +Last updated: Tue Aug 8 13:39:58 EDT 2006

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -137,18 +137,10 @@ first. most recent transactions aren't available for recovery in case of a disk failure.

-
  • Automatically force archiving of partially-filled WAL files when +
  • -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. - http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php -

    -
  • Add reporting of the current WAL file and offset, perhaps as +
  • -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. -

  • %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 @@ -762,7 +754,7 @@ first.
  • Make SET CONNECTION thread-aware, non-standard?
  • Allow multidimensional arrays
  • Add internationalized message strings -
  • Add COPY TO STDIN handling +
  • COPY FROM STDIN not implemented because not useful?
  • libpq