Re: GUC option log_pid is not checked [Fwd: Bug#149675: Fix] - Mailing list pgsql-patches

From Tom Lane
Subject Re: GUC option log_pid is not checked [Fwd: Bug#149675: Fix]
Date
Msg-id 9350.1023891151@sss.pgh.pa.us
Whole thread Raw
In response to GUC option log_pid is not checked [Fwd: Bug#149675: Fix]  (Oliver Elphick <olly@lfix.co.uk>)
Responses Re: GUC option log_pid is not checked [Fwd: Bug#149675:
List pgsql-patches
Oliver Elphick <olly@lfix.co.uk> writes:
> The GUC option log_pid is not checked; LOG_PID is used by default,
> contrary to the documentation.  This patch fixes it.

No it doesn't (at least not unless you are also going to propose closing
and reopening syslog at SIGHUP to deal with changes in log_pid setting).

I'm not convinced that there's anything wrong with the code anyway.
Do you expect log_timestamp to control whether timestamps are added to
syslog entries?  If so you are out of luck.  Perhaps we should just
tweak the documentation to make it clearer that log_pid and
log_timestamp only control the format of non-syslog logging.

            regards, tom lane

pgsql-patches by date:

Previous
From: Manfred Koizar
Date:
Subject: WriteBuffer return value
Next
From: Tom Lane
Date:
Subject: Re: WriteBuffer return value