Robert Haas <robertmh...@gmail.com> writes:
> On Wed, Mar 9, 2016 at 12:32 PM, Gilles Darold <gilles.dar...@dalibo.com>
> wrote:
>> I choose to allow the log collector to write his current log file name
>> into the lock file 'postmaster.pid'.
> Gosh, why? Piggybacking this on a file written for a specific purpose
> by a different process seems like making life very hard for yourself,
> and almost certainly a recipe for bugs.
That's a *complete* nonstarter. postmaster.pid has to be written by the
postmaster process and nobody else.
It's a particularly bad choice for the syslogger, which will exist
fractionally longer than the postmaster, and thus might be trying to write
into the file after the postmaster has removed it.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
