sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-01 00:01:20 -04:00
Code Issues Projects Releases Wiki Activity

Add description for backend termination:

Browse Source 
<   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:
Bruce Momjian 2005-06-05 03:39:54 +00:00
parent bebe7c5600
commit 22dbd54047
2 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TODO
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: 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 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.
@ -96,7 +96,9 @@ Administration
Right now, SIGTERM will terminate a session, but it is treated as Right now, SIGTERM will terminate a session, but it is treated as
though the postmaster has paniced and shared memory might not be 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 * Un-comment all variables in postgresql.conf

6
doc/src/FAQ/TODO.html
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: Sat Jun 4 20:45:17 EDT 2005 Last updated: Sat Jun 4 23:39:40 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>.
@ -92,7 +92,9 @@ first.
</li><li>Allow administrators to safely terminate individual sessions </li><li>Allow administrators to safely terminate individual sessions
<p> Right now, SIGTERM will terminate a session, but it is treated as <p> Right now, SIGTERM will terminate a session, but it is treated as
though the postmaster has paniced and shared memory might not be 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> </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