Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitdea4117

Browse files
committed
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
1 parent2f5c47e commitdea4117

File tree

2 files changed

+6
-17
lines changed

2 files changed

+6
-17
lines changed

‎doc/TODO

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Fri Jun17 21:45:55 EDT 2005
5+
Last updated:Thu Jun23 17:28:04 EDT 2005
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -91,14 +91,8 @@ Administration
9191
This would require a new global table that is dumped to flat file for
9292
use by the postmaster. We do a similar thing for pg_shadow currently.
9393

94-
* Allow administrators to safely terminate individual sessions
95-
96-
Right now, SIGTERM will terminate a session, but it is treated as
97-
though the postmaster has paniced and shared memory might not be
98-
cleaned up properly. A new signal is needed for safe termination
99-
because backends must first do a query cancel, then exit once they
100-
have run the query cancel cleanup routine.
101-
94+
* Allow administrators to safely terminate individual sessions either
95+
via an SQL function or SIGTERM
10296
* Un-comment all variables in postgresql.conf
10397

10498
By not showing commented-out variables, we discourage people from

‎doc/src/FAQ/TODO.html

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated:Fri Jun17 21:45:55 EDT 2005
11+
Last updated:Thu Jun23 17:28:04 EDT 2005
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -88,13 +88,8 @@ <h1><a name="section_2">Administration</a></h1>
8888
<p> This would require a new global table that is dumped to flat file for
8989
use by the postmaster. We do a similar thing for pg_shadow currently.
9090
</p>
91-
</li><li>Allow administrators to safely terminate individual sessions
92-
<p> Right now, SIGTERM will terminate a session, but it is treated as
93-
though the postmaster has paniced and shared memory might not be
94-
cleaned up properly. A new signal is needed for safe termination
95-
because backends must first do a query cancel, then exit once they
96-
have run the query cancel cleanup routine.
97-
</p>
91+
</li><li>Allow administrators to safely terminate individual sessions either
92+
via an SQL function or SIGTERM
9893
</li><li>Un-comment all variables in postgresql.conf
9994
<p> By not showing commented-out variables, we discourage people from
10095
thinking that re-commenting a variable returns it to its default.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp