diff options
| author | Bruce Momjian <bruce@momjian.us> | 2006-07-25 15:21:48 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2006-07-25 15:21:48 +0000 |
| commit | cb6f5f1552d1dbba2465f513c75c1335d0a446d3 (patch) | |
| tree | b5a6e2dabbb3268b2f5da3383fea50c522cc8916 | |
| parent | bd112776cdacbe60f7e09fdbcba5061b90618e5e (diff) | |
| download | postgresql-cb6f5f1552d1dbba2465f513c75c1335d0a446d3.tar.gz postgresql-cb6f5f1552d1dbba2465f513c75c1335d0a446d3.zip | |
Update PITR:
< write-ahead logs [pitr]
> write-ahead logs? [pitr]
< recovery.
> recovery. A function call to do this would also be useful.
| -rw-r--r-- | doc/TODO | 6 | ||||
| -rw-r--r-- | doc/src/FAQ/TODO.html | 6 |
2 files changed, 6 insertions, 6 deletions
@@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Tue Jul 25 00: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. @@ -145,7 +145,7 @@ Administration * 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 @@ -157,7 +157,7 @@ Administration 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 9ddd24a2f78..f5d4489f4c8 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -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 00:11:20 EDT 2006 +Last updated: Tue Jul 25 11:21:42 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>. @@ -132,7 +132,7 @@ first. </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>] + 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 @@ -142,7 +142,7 @@ first. 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. <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>%Create dump tool for write-ahead logs for use in determining |