PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Jun 24 00:40:44 EDT 2005
+Last updated: Fri Jun 24 17:28:23 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
* Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
+
+ Currently SIGTERM of a backend can lead to lock table corruption.
+
* Un-comment all variables in postgresql.conf
By not showing commented-out variables, we discourage people 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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Fri Jun 24 00:40:44 EDT 2005
+Last updated: Fri Jun 24 17:28:23 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>.
</p>
</li><li>Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
+<p> Currently SIGTERM of a backend can lead to lock table corruption.
+</p>
</li><li>Un-comment all variables in postgresql.conf
<p> By not showing commented-out variables, we discourage people from
thinking that re-commenting a variable returns it to its default.
projects / postgresql / commitdiff