From abd3f43b4c6fb298fa1eb12fe8d78c6c3e6e0532 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 14 Oct 2005 20:53:56 +0000 Subject: Fix syslog bug: if any messages are emitted to write_syslog before the facility has been set, the facility gets set to LOCAL0 and cannot be changed later. This seems reasonably plausible to happen, particularly at higher debug log levels, though I am not certain it explains Han Holl's recent report. Easiest fix is to teach the code how to change the value on-the-fly, which is nicer anyway. I made the settings PGC_SIGHUP to conform with log_destination. --- doc/src/sgml/config.sgml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 9e695bad576..b02598a7bcd 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,5 +1,5 @@ Run-time Configuration @@ -2254,7 +2254,8 @@ SELECT * FROM parent WHERE key = 2400; the default is LOCAL0. See also the documentation of your system's syslog daemon. - This option can only be set at server start. + This option can only be set at server start or in the + postgresql.conf configuration file. @@ -2271,7 +2272,8 @@ SELECT * FROM parent WHERE key = 2400; PostgreSQL messages in syslog logs. The default is postgres. - This option can only be set at server start. + This option can only be set at server start or in the + postgresql.conf configuration file. @@ -2581,8 +2583,8 @@ SELECT * FROM parent WHERE key = 2400; log_statement to be logged. When using this option, if you are not using syslog, it is recommended that you log the PID or session ID using log_line_prefix - so that you can link the statement to the - duration using the process ID or session ID. The default is + so that you can link the statement message to the later + duration message using the process ID or session ID. The default is off. Only superusers can change this setting. -- cgit v1.2.3