Add description for backend termination:

bmomjian · bmomjian · commit 22dbd5404785 · 2005-06-05T03:39:54.000Z
&lt;   cleaned up properly.  A new signal is needed for safe termination.
&gt;   cleaned up properly.  A new signal is needed for safe termination
&gt;   because backends must first do a query cancel, then exit once they
&gt;   have run the query cancel cleanup routine.
diff --git a/doc/TODO b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Sat Jun  4 20:45:17 EDT 2005
+Last updated:		Sat Jun  4 23:39:40 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -96,7 +96,9 @@ Administration
 
   Right now, SIGTERM will terminate a session, but it is treated as
   though the postmaster has paniced and shared memory might not be
-  cleaned up properly.  A new signal is needed for safe termination.
+  cleaned up properly.  A new signal is needed for safe termination
+  because backends must first do a query cancel, then exit once they
+  have run the query cancel cleanup routine.
 
 * Un-comment all variables in postgresql.conf
 
diff --git 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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated:           Sat Jun  4 20:45:17 EDT 2005
+Last updated:           Sat Jun  4 23:39:40 EDT 2005
 </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>.
@@ -92,7 +92,9 @@ <h1><a name="section_2">Administration</a></h1>
   </li><li>Allow administrators to safely terminate individual sessions
 <p>  Right now, SIGTERM will terminate a session, but it is treated as
   though the postmaster has paniced and shared memory might not be
-  cleaned up properly.  A new signal is needed for safe termination.
+  cleaned up properly.  A new signal is needed for safe termination
+  because backends must first do a query cancel, then exit once they
+  have run the query cancel cleanup routine.
 </p>
   </li><li>Un-comment all variables in postgresql.conf
 <p>  By not showing commented-out variables, we discourage people from
