From 03a68a7caee0f1e2ebc537ed8bb2c7dde166c091 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 26 Sep 2006 11:18:29 +0000
Subject: [PATCH] Done:
< 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.
<
Reorder:
< o %Create dump tool for write-ahead logs for use in determining
< transaction id for point-in-time recovery
> o %Create dump tool for write-ahead logs for use in determining
> transaction id for point-in-time recovery
---
doc/TODO | 12 +++---------
doc/src/FAQ/TODO.html | 13 ++++---------
2 files changed, 7 insertions(+), 18 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index b8bede9dacf..f43d747371e 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Wed Sep 20 19:01:42 EDT 2006
+Last updated: Tue Sep 26 07:18:13 EDT 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -139,19 +139,13 @@ Administration
* Point-In-Time Recovery (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.
-
- 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
[pitr]
This is useful for checking PITR recovery.
+ o %Create dump tool for write-ahead logs for use in determining
+ transaction id for point-in-time recovery
o Allow the PITR process to be debugged and data examined
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 5f7754cc015..b4a5c37f79b 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: Wed Sep 20 19:01:42 EDT 2006
+Last updated: Tue Sep 26 07:18:13 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>.
@@ -127,17 +127,12 @@ first.
</li></ul>
</li><li>Point-In-Time Recovery (PITR)
<ul>
- <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.
-</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
+ <li>Allow a warm standby system to also allow read-only statements
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> This is useful for checking PITR recovery.
</p>
+ </li><li>%Create dump tool for write-ahead logs for use in determining
+ transaction id for point-in-time recovery
</li><li>Allow the PITR process to be debugged and data examined
</li></ul>
</li></ul>
--
GitLab