Add description for backend termination:
< 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.
This commit is contained in:
parent
bebe7c5600
commit
22dbd54047
6
doc/TODO
6
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
|
||||
|
||||
|
@ -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 @@ first.
|
||||
</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
|
||||
|
Loading…
x
Reference in New Issue
Block a user