PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)

Last updated:Sat Jul30 23:28:17 EDT 2005

Last updated:Sun Jul31 09:54:46 EDT 2005

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

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

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>

Last updated:Sat Jul30 23:28:17 EDT 2005

Last updated:Sun Jul31 09:54:46 EDT 2005

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

<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.

</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><li>Tablespaces