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

Commita9c1047

Browse files
committed
Update comment on how sighup signal affects postgresql.conf reload.
Markus Bertheau
1 parent526f773 commita9c1047

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

‎src/include/utils/guc.h

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
* Copyright (c) 2000-2006, PostgreSQL Global Development Group
88
* Written by Peter Eisentraut <peter_e@gmx.net>.
99
*
10-
* $PostgreSQL: pgsql/src/include/utils/guc.h,v 1.64 2006/03/05 15:59:07 momjian Exp $
10+
* $PostgreSQL: pgsql/src/include/utils/guc.h,v 1.65 2006/03/06 18:38:11 momjian Exp $
1111
*--------------------------------------------------------------------
1212
*/
1313
#ifndefGUC_H
@@ -31,10 +31,10 @@
3131
*
3232
* SIGHUP options can only be set at postmaster startup or by changing
3333
* the configuration file and sending the HUP signal to the postmaster
34-
* or a backend process. (Notice that the signal receipt willnotbe
35-
* evaluated immediately. The postmaster andthebackend check it at a
36-
* certain point intheir main loop. It's safer to wait than to read a
37-
* file asynchronously.)
34+
* or a backend process. (Notice that the signal receipt will be
35+
* evaluated immediately only inthepostmaster. The backend checks it
36+
*at acertain point inits main loop. It's safer to wait than to
37+
*read afile asynchronously.)
3838
*
3939
* BACKEND options can only be set at postmaster startup, from the
4040
* configuration file, or by client request in the connection startup

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp