PostgreSQL TODO List

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

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

Last updated:Wed Apr26 22:41:35 EDT 2006

Last updated:Thu Apr27 11:56:04 EDT 2006

The most recent version of this document can be viewed at

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

This would allow administrators to see more detailed information from

specific sections of the backend, e.g. checkpoints, autovacuum, etc.

Another idea is to allow separate configuration files for each module,

or allow arbitrary SET commands to be passed to them.

* -Re-enable the GUC full_page_writes in 8.2 when reliability issues have

been addressed

<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:Wed Apr26 22:41:35 EDT 2006

Last updated:Thu Apr27 11:56:04 EDT 2006

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

</li><li>Allow log_min_messages to be specified on a per-module basis

<p> This would allow administrators to see more detailed information from

specific sections of the backend, e.g. checkpoints, autovacuum, etc.

Another idea is to allow separate configuration files for each module,

or allow arbitrary SET commands to be passed to them.

</li><li>-<em>Re-enable the GUC full_page_writes in 8.2 when reliability issues have</em>

been addressed