open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Adjust TODO spacing.

Browse Source
REL8_5_ALPHA1_BRANCH
Bruce Momjian 18 years ago
parent 3ff83c333e
commit 3a1e7b24a7
2 changed files with 17 additions and 17 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 20
      doc/TODO
  2. 14
      doc/src/FAQ/TODO.html

20
doc/TODO
Unescape View File

@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Mon Mar 17 17:09:20 EDT 2008
Last updated: Mon Mar 17 17:45:06 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -154,20 +154,20 @@ Administration
* Point-In-Time Recovery (PITR)
o Allow a warm standby system to also allow read-only statements
[pitr]
o Allow a warm standby system to also allow read-only statements
[pitr]
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
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
This is useful for checking PITR recovery.
This is useful for checking PITR recovery.
o Allow recovery.conf to support the same syntax as
postgresql.conf, including quoting
o Allow recovery.conf to support the same syntax as
postgresql.conf, including quoting
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
Data Types

14
doc/src/FAQ/TODO.html
Unescape 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: Mon Mar 17 17:09:20 EDT 2008
Last updated: Mon Mar 17 17:45:06 EDT 2008
</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>.
@ -144,16 +144,16 @@ first. There is also a developer's wiki at<br/>
</li><li>Point-In-Time Recovery (PITR)
<ul>
<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> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php</a>
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php</a>
</p>
</li><li>%Create dump tool for write-ahead logs for use in determining
transaction id for point-in-time recovery
<p> This is useful for checking PITR recovery.
transaction id for point-in-time recovery
<p> This is useful for checking PITR recovery.
</p>
</li><li>Allow recovery.conf to support the same syntax as
postgresql.conf, including quoting
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php</a>
postgresql.conf, including quoting
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php</a>
</p>
</li></ul>
</li></ul>

Write Preview
Loading…
Cancel
Save