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.

diff --git a/doc/TODO b/doc/TODO
index 603614fd51a056a74c22863b07e6d754fda838a2..163eeeb120c142c0c63da3d36bbfb91249c520f3 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-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
-     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.
 
    o Allow postgresql.conf file values to be changed via an SQL
      API, perhaps using SET GLOBAL

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index c6d3497f3f4ff7a31acccf71fda1e96a9d118616..d818a1defd8816bb3f4c4237a2337d3a9d37b948 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-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.
@@ -65,8 +65,11 @@ first.
     Allow commenting of variables in postgresql.conf to restore them
           to defaults
     Allow pg_hba.conf settings to be controlled via SQL
-          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.
 
     Allow postgresql.conf file values to be changed via an SQL
           API, perhaps using SET GLOBAL