88< body bgcolor ="#FFFFFF " text ="#000000 " link ="#FF0000 " vlink ="#A00000 " alink ="#0000FF ">
99< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
1010< p > Current maintainer: Bruce Momjian (< a href ="mailto:bruce@momjian.us "> bruce@momjian.us</ a > )< br />
11- Last updated: Tue Jul 25 00: 11:20 EDT 2006
11+ Last updated: Tue Jul 25 11:21:42 EDT 2006
1212</ p >
1313< p > The most recent version of this document can be viewed at< br />
1414< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -132,7 +132,7 @@ <h1><a name="section_2">Administration</a></h1>
132132 </ li > < li > Point-In-Time Recovery (PITR)
133133 < ul >
134134 < li > Allow point-in-time recovery to archive partially filled
135- write-ahead logs [< a href ="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr "> pitr</ a > ]
135+ write-ahead logs? [< a href ="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr "> pitr</ a > ]
136136< p > Currently only full WAL files are archived. This means that the
137137 most recent transactions aren't available for recovery in case
138138 of a disk failure. This could be triggered by a user command or
@@ -142,7 +142,7 @@ <h1><a name="section_2">Administration</a></h1>
142142 pg_stop_backup() is called or the server is stopped
143143< p > Doing this will allow administrators to know more easily when
144144 the archive contains all the files needed for point-in-time
145- recovery.
145+ recovery. A function call to do this would also be useful.
146146 < a href ="http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php "> http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php</ a >
147147</ p >
148148 </ li > < li > %Create dump tool for write-ahead logs for use in determining
0 commit comments