diff options
| author | Bruce Momjian | 2005-06-23 21:28:10 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2005-06-23 21:28:10 +0000 |
| commit | dea41174b205ee592d46c074518b38d97b8b90c2 (patch) | |
| tree | aadab7b3f45563b5ade73e67c1c9a5c4ac30c11f | |
| parent | 2f5c47e882d9cda2395223d01d3d93611b1dfe77 (diff) | |
Update text of terminate:
< * Allow administrators to safely terminate individual sessions
<
< 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
< because backends must first do a query cancel, then exit once they
< have run the query cancel cleanup routine.
<
> * Allow administrators to safely terminate individual sessions either
> via an SQL function or SIGTERM
| -rw-r--r-- | doc/TODO | 12 | ||||
| -rw-r--r-- | doc/src/FAQ/TODO.html | 11 |
2 files changed, 6 insertions, 17 deletions
@@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian ([email protected]) -Last updated: Fri Jun 17 21:45:55 EDT 2005 +Last updated: Thu Jun 23 17:28:04 EDT 2005 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -91,14 +91,8 @@ Administration This would require a new global table that is dumped to flat file for use by the postmaster. We do a similar thing for pg_shadow currently. -* Allow administrators to safely terminate individual sessions - - 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 - because backends must first do a query cancel, then exit once they - have run the query cancel cleanup routine. - +* Allow administrators to safely terminate individual sessions either + via an SQL function or SIGTERM * Un-comment all variables in postgresql.conf By not showing commented-out variables, we discourage people from diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index c1d1bcc8de..9ff701afbb 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:[email protected]">[email protected]</a>)<br/> -Last updated: Fri Jun 17 21:45:55 EDT 2005 +Last updated: Thu Jun 23 17:28:04 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>. @@ -88,13 +88,8 @@ first. <p> This would require a new global table that is dumped to flat file for use by the postmaster. We do a similar thing for pg_shadow currently. </p> - </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 - because backends must first do a query cancel, then exit once they - have run the query cancel cleanup routine. -</p> + </li><li>Allow administrators to safely terminate individual sessions either + via an SQL function or SIGTERM </li><li>Un-comment all variables in postgresql.conf <p> By not showing commented-out variables, we discourage people from thinking that re-commenting a variable returns it to its default. |