Re: BUG #15804: Assertion failure when using logging_collector withEXEC_BACKEND - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15804: Assertion failure when using logging_collector withEXEC_BACKEND
Date
Msg-id 20190910051115.GB22934@paquier.xyz
Whole thread Raw
In response to Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
List pgsql-bugs
On Mon, Sep 09, 2019 at 03:35:23PM -0400, Tom Lane wrote:
> I think this probably is committable now, though of course it'd
> be good for somebody to review it (and maybe test on Windows
> before it hits the buildfarm?)

I have looked at the patch and tested it a bit on Windows with MSVC
(TAP, bincheck, etc.), and the logic looks fine.  Thanks.

Do we need to worry about the port being opened after the external PID
file is written though?  With some imagination it is possible to
imagine that some folks rely on the external PID file to be present
before attempting to access Postgres when not using pg_ctl.  Still, I
would discard that as postmaster.pid gets written before opening the
port already.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Euler Taveira
Date:
Subject: Re: BUG #15992: Index size larger than the base table size. Sometime3 times large
Next
From: Tom Lane
Date:
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND