mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-11-27 07:21:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Reorder items:

Browse Source 
< 	  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.
This commit is contained in:
Bruce Momjian 2006-07-26 17:23:02 +00:00
parent 9a7483714f
commit 5ffa0bb47a
2 changed files with 19 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/TODO
View File

@ -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

20
doc/src/FAQ/TODO.html
View File

@ -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: Tue Jul 25 20:34:56 EDT 2006
Last updated: Wed Jul 26 13:22:49 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>.
@ -131,19 +131,22 @@ first.
</li></ul>
</li><li>Point-In-Time Recovery (PITR)
<ul>
<li>Allow point-in-time recovery to archive partially filled
write-ahead logs? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<li>Add command to archive partially filled write-ahead logs? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> 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.
</p>
</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 function call to do this would also be useful.
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
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
@ -152,11 +155,6 @@ first.
<p> This is useful for checking PITR recovery.
</p>
</li><li>Allow the PITR process to be debugged and data examined
</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></ul>
</li></ul>
<h1><a name="section_3">Monitoring</a></h1>