Suggest syntax:

< o Allow postgresql.conf file values to be changed via an SQL API > o Allow postgresql.conf file values to be changed via an SQL > API, perhaps using SET GLOBAL

Suggest syntax:
< o Allow postgresql.conf file values to be changed via an SQL API > o Allow postgresql.conf file values to be changed via an SQL > API, perhaps using SET GLOBAL
b1258771 · Bruce Momjian · 73b574c1 · b1258771 · b1258771
Commit b1258771 authored Jul 31, 2005 by Bruce Momjian
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 4 deletions

doc/TODO doc/TODO +3 -2

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

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:		Sat Jul 30 23:28:17 EDT 2005
+Last updated:		Sun Jul 31 09:54:46 EDT 2005

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -71,7 +71,8 @@ Administration
 	  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.

-	o Allow postgresql.conf file values to be changed via an SQL API
+	o Allow postgresql.conf file values to be changed via an SQL
+	  API, perhaps using SET GLOBAL
 	o Allow the server to be stopped/restarted via an SQL API



--- 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:           Sat Jul 30 23:28:17 EDT 2005
+Last updated:           Sun Jul 31 09:54:46 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>.
@@ -68,7 +68,8 @@ first.
 <p>          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.
 </p>
-    </li><li>Allow postgresql.conf file values to be changed via an SQL API
+    </li><li>Allow postgresql.conf file values to be changed via an SQL
+          API, perhaps using SET GLOBAL
    </li><li>Allow the server to be stopped/restarted via an SQL API
  </li></ul>
  </li><li>Tablespaces