From dea41174b205ee592d46c074518b38d97b8b90c2 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Thu, 23 Jun 2005 21:28:10 +0000
Subject: 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
---
doc/src/FAQ/TODO.html | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index c1d1bcc8de3..9ff701afbb9 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-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.
@@ -88,13 +88,8 @@ first.
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
thinking that re-commenting a variable returns it to its default.
--
cgit v1.2.3