From c5c7ba1b103847439949762d6fdeec4144b9ceed Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Thu, 17 Apr 2008 20:57:07 +0000 Subject: [PATCH] TODO Done: > * -Allow administrators to safely terminate individual sessions --- doc/TODO | 13 ++----------- doc/src/FAQ/TODO.html | 12 ++---------- 2 files changed, 4 insertions(+), 21 deletions(-) diff --git a/doc/TODO b/doc/TODO index bd336ced30d..3c7d50a78e9 100644 --- a/doc/TODO +++ b/doc/TODO @@ -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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 4150a5d734c..bc64564eb8f 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -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> -- GitLab