open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update text of terminate:

Browse Source 
< * 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
REL8_1_STABLE
Bruce Momjian 21 years ago
parent 2f5c47e882
commit dea41174b2
2 changed files with 6 additions and 17 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 12
      doc/TODO
  2. 11
      doc/src/FAQ/TODO.html

12
doc/TODO
Unescape View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. 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 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. use by the postmaster. We do a similar thing for pg_shadow currently.
* Allow administrators to safely terminate individual sessions * Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
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.
* Un-comment all variables in postgresql.conf * Un-comment all variables in postgresql.conf
By not showing commented-out variables, we discourage people from By not showing commented-out variables, we discourage people from

11
doc/src/FAQ/TODO.html
Unescape View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Fri Jun 17 21:45:55 EDT 2005 Last updated: Thu Jun 23 17:28:04 EDT 2005
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <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 <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. use by the postmaster. We do a similar thing for pg_shadow currently.
</p> </p>
</li><li>Allow administrators to safely terminate individual sessions </li><li>Allow administrators to safely terminate individual sessions either
<p> Right now, SIGTERM will terminate a session, but it is treated as via an SQL function or SIGTERM
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>Un-comment all variables in postgresql.conf </li><li>Un-comment all variables in postgresql.conf
<p> By not showing commented-out variables, we discourage people from <p> By not showing commented-out variables, we discourage people from
thinking that re-commenting a variable returns it to its default. thinking that re-commenting a variable returns it to its default.

Write Preview
Loading…
Cancel
Save