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. <
This commit is contained in:
parent
e7d490f91d
commit
2392cdb795
16
doc/TODO
16
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
|
||||
|
@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
||||
Last updated: Mon Aug 7 21:24:28 EDT 2006
|
||||
Last updated: Tue Aug 8 13:39:58 EDT 2006
|
||||
</p>
|
||||
<p>The most recent version of this document can be viewed at<br/>
|
||||
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
|
||||
@ -137,18 +137,10 @@ first.
|
||||
most recent transactions aren't available for recovery in case
|
||||
of a disk failure.
|
||||
</p>
|
||||
</li><li>Automatically force archiving of partially-filled WAL files when
|
||||
</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 contains all the files needed for point-in-time
|
||||
recovery.
|
||||
<a href="http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php">http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php</a>
|
||||
</p>
|
||||
</li><li>Add reporting of the current WAL file and offset, perhaps as
|
||||
</li><li>-Add reporting of the current WAL file and offset, perhaps as
|
||||
part of partial log file archiving
|
||||
<p> The offset allows parts of a WAL file to be archived using
|
||||
an external program.
|
||||
</p>
|
||||
</li><li>%Create dump tool for write-ahead logs for use in determining
|
||||
transaction id for point-in-time recovery
|
||||
</li><li>Allow a warm standby system to also allow read-only statements
|
||||
@ -762,7 +754,7 @@ first.
|
||||
</li><li>Make SET CONNECTION thread-aware, non-standard?
|
||||
</li><li>Allow multidimensional arrays
|
||||
</li><li>Add internationalized message strings
|
||||
</li><li>Add COPY TO STDIN handling
|
||||
</li><li>COPY FROM STDIN not implemented because not useful?
|
||||
</li></ul>
|
||||
</li><li>libpq
|
||||
<ul>
|
||||
|
Loading…
Reference in New Issue
Block a user