PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Tue Mar 11 11:48:41 EDT 2008
+Last updated: Tue Mar 11 11:51:58 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
* Allow statistics collector information to be pulled from the collector
process directly, rather than requiring the collector to write a
filesystem file twice a second?
+* Allow statistics last vacuum/analyze execution times to be displayed
+ without requiring stats_row_level to be enabled
* Allow log_min_messages to be specified on a per-module basis
This would allow administrators to see more detailed information from
<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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated: Tue Mar 11 11:48:41 EDT 2008
+Last updated: Tue Mar 11 11:51:58 EDT 2008
</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>.
</li><li>Allow statistics collector information to be pulled from the collector
process directly, rather than requiring the collector to write a
filesystem file twice a second?
+ </li><li>Allow statistics last vacuum/analyze execution times to be displayed
+ without requiring stats_row_level to be enabled
</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.