TODO Done:

> * -Allow administrators to safely terminate individual sessions
This commit is contained in:
Bruce Momjian 2008-04-17 20:57:07 +00:00
parent c4fd93b3f3
commit c5c7ba1b10
2 changed files with 4 additions and 21 deletions

View File

@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Wed Apr 16 13:49:50 EDT 2008
Last updated: Thu Apr 17 16:56:51 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -20,17 +20,8 @@ http://developer.postgresql.org.
Administration
==============
* Allow administrators to safely terminate individual sessions either
* -Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
Lock table corruption following SIGTERM of an individual backend
has been reported in 8.0. A possible cause was fixed in 8.1, but
it is unknown whether other problems exist. This item mostly
requires additional testing rather than of writing any new code.
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
* Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly

View File

@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Wed Apr 16 13:49:50 EDT 2008
Last updated: Thu Apr 17 16:56:51 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>.
@ -26,16 +26,8 @@ first. There is also a developer's wiki at<br/>
<h1><a name="section_2">Administration</a></h1>
<ul>
<li>Allow administrators to safely terminate individual sessions either
<li>-<em>Allow administrators to safely terminate individual sessions either</em>
via an SQL function or SIGTERM
<p> Lock table corruption following SIGTERM of an individual backend
has been reported in 8.0. A possible cause was fixed in 8.1, but
it is unknown whether other problems exist. This item mostly
requires additional testing rather than of writing any new code.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php</a>
</p>
</li><li>Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php</a>