PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (bruce@momjian.us)

Last updated:Tue Jul 2500:11:20 EDT 2006

Last updated:Tue Jul 25 11:21:42 EDT 2006

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

* Point-In-Time Recovery (PITR)

o Allow point-in-time recovery to archive partially filled

write-ahead logs [pitr]

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

Doing this will allow administrators to know more easily when

the archive contains all the files needed for point-in-time

recovery.

recovery.A function call to do this would also be useful.

http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php

o %Create dump tool for write-ahead logs for use in determining

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>

Last updated: Tue Jul 2500:11:20 EDT 2006

Last updated: Tue Jul 25 11:21:42 EDT 2006

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

</li><li>Point-In-Time Recovery (PITR)

<li>Allow point-in-time recovery to archive partially filled

write-ahead logs [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]

write-ahead logs? [<ahref="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

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.

recovery.A function call to do this would also be useful.

<ahref="http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php">http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php</a>

</li><li>%Create dump tool for write-ahead logs for use in determining