TODO Done:

> * -Allow administrators to safely terminate individual sessions

diff --git a/doc/TODO b/doc/TODO
index bd336ced30d484baf7a009eb4881d7f7fa28496b..3c7d50a78e90114375d2c608f3bb163946860338 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-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
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 4150a5d734cad51d4bc8bb800cb785c74f22b6a1..bc64564eb8f80fa11c73e79cc1c01a0418be4e5a 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-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.
@@ -26,16 +26,8 @@ first.  There is also a developer's wiki at
 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
   http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php