Horton

Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-05-19T02:10:43Z
Lists: pgsql-bugs 
Hi,

On 2019-05-18 12:18:28 -0400, Tom Lane wrote:
> At this point I agree with Michael that reverting 57431a911 is the most
> prudent thing to do for beta1.

Seems reasonable at this point in time :(.  A bit annoyed that
longer-existing crappyness around the windows port affects a relatively
platform independent patch this much.


> (I'm also getting annoyed that Peter, as the original author of this
> commit, isn't doing anything about the issue.)

Yea, I'm confused / annoyed about that too.


> I wouldn't be totally opposed to un-reverting after beta1, if a
> better-tested patch emerges.  But we don't have such a patch today
> and I don't see how we'll get there this weekend.

Right. I think if somebody puts some elbow grease into that that'd be a
reasonable course. But so far Peter's not showing up, so ...


Greetings,

Andres Freund

Commits

  1. Rearrange postmaster's startup sequence for better syslogger results.

  2. Improve logrotate test so that it meaningfully exercises syslogger.

  3. Revert "postmaster: Start syslogger earlier".

  4. postmaster: Start syslogger earlier