Horton

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

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-05-23T14:17:50Z
Lists: pgsql-bugs 
On 2019-05-19 04:10, Andres Freund wrote:
>> (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 was traveling, and the subject line didn't yell "problem with beta1".

>> 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 ...

After rereading the entire discussion, I don't have much enthusiasm for
trying to fix this for PG12.  It's worth trying again in the future.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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