summaryrefslogtreecommitdiff
path: root/doc/src/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/FAQ')
-rw-r--r--doc/src/FAQ/TODO.html10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 59ac9949fe6..6872320c749 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -26,8 +26,16 @@ first. There is also a developer's wiki at<br/>
<h1><a name="section_2">Administration</a></h1>
<ul>
- <li>-<em>Allow administrators to safely terminate individual sessions either</em>
+ <li>Allow administrators to safely terminate individual sessions either
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>