Add description:

< This would require a new global table that is dumped to flat file for < use by the postmaster. We do a similar thing for pg_shadow currently. > This would add a function to load the SQL table from > pg_hba.conf, and one to writes its contents to the flat file. > The table should have a line number that is a float so rows > can be inserted between existing rows, e.g. row 2.5 goes > between row 2 and row 3.

Add description:
< This would require a new global table that is dumped to flat file for < use by the postmaster. We do a similar thing for pg_shadow currently. > This would add a function to load the SQL table from > pg_hba.conf, and one to writes its contents to the flat file. > The table should have a line number that is a float so rows > can be inserted between existing rows, e.g. row 2.5 goes > between row 2 and row 3.
a85e5d1b · Bruce Momjian · d42cf5a4 · a85e5d1b · a85e5d1b
Commit a85e5d1b authored Aug 01, 2005 by Bruce Momjian
Hide whitespace changes
Inline Side-by-side

Showing with 12 additions and 6 deletions

doc/TODO doc/TODO +6 -3

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +6 -3

No files found.
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Sun Jul 31 09:54:46 EDT 2005
+Last updated:		Sun Jul 31 20:52:25 EDT 2005
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -68,8 +68,11 @@ Administration
 	  to defaults
 	o Allow pg_hba.conf settings to be controlled via SQL
-	  This would require a new global table that is dumped to flat file for
+	  This would add a function to load the SQL table from
-	  use by the postmaster.  We do a similar thing for pg_shadow currently.
+          pg_hba.conf, and one to writes its contents to the flat file.
+	  The table should have a line number that is a float so rows
+	  can be inserted between existing rows, e.g. row 2.5 goes
+	  between row 2 and row 3.
 	o Allow postgresql.conf file values to be changed via an SQL
 	  API, perhaps using SET GLOBAL

--- 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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated:           Sun Jul 31 09:54:46 EDT 2005
+Last updated:           Sun Jul 31 20:52:25 EDT 2005
 </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>.
@@ -65,8 +65,11 @@ first.
    </li><li>Allow commenting of variables in postgresql.conf to restore them
          to defaults
    </li><li>Allow pg_hba.conf settings to be controlled via SQL
-<p>          This would require a new global table that is dumped to flat file for
+<p>          This would add a function to load the SQL table from
-          use by the postmaster.  We do a similar thing for pg_shadow currently.
+          pg_hba.conf, and one to writes its contents to the flat file.
+          The table should have a line number that is a float so rows
+          can be inserted between existing rows, e.g. row 2.5 goes
+          between row 2 and row 3.
 </p>
    </li><li>Allow postgresql.conf file values to be changed via an SQL
          API, perhaps using SET GLOBAL