88< body bgcolor ="#FFFFFF "text ="#000000 "link ="#FF0000 "vlink ="#A00000 "alink ="#0000FF ">
99< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
1010< p > Current maintainer: Bruce Momjian (< a href ="mailto:bruce@momjian.us "> bruce@momjian.us</ a > )< br />
11- Last updated:Mon Apr14 09:33:40 EDT 2008
11+ Last updated:Tue Apr15 09:55:33 EDT 2008
1212</ p >
1313< p > The most recent version of this document can be viewed at< br />
1414< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -26,16 +26,8 @@ <h1><a name="section_1">PostgreSQL TODO List</a></h1>
2626< h1 > < a name ="section_2 "> Administration</ a > </ h1 >
2727
2828< ul >
29- < li > Allow administrators to safely terminate individual sessions either
29+ < li > - < em > Allow administrators to safely terminate individual sessions either</ em >
3030 via an SQL function or SIGTERM
31- < p > Lock table corruption following SIGTERM of an individual backend
32- has been reported in 8.0. A possible cause was fixed in 8.1, but
33- it is unknown whether other problems exist. This item mostly
34- requires additional testing rather than of writing any new code.
35- </ p >
36- < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php "> http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</ a >
37- < a href ="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php "> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php</ a >
38- </ p >
3931</ li > < li > Check for unreferenced table files created by transactions that were
4032 in-progress when the server terminated abruptly
4133< p > < a href ="http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php "> http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php</ a >