Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-05-19T15:05:22Z
Lists: pgsql-bugs 
Michael Paquier <michael@paquier.xyz> writes:
> Thanks for confirming.  There is little time for doing the revert, and
> it would have been nice seeing comments from Peter.  Anyway, I should
> be able to do that myself in 24 hours or so after coming back in
> front of my desk so as the buildfarm can have a couple of cycles for
> its work.  If you prefer doing that yourself, that's of course fine by
> me.

I'm going to push this revert in a few minutes (as soon as I get done
with local sanity testing).  At this point, an extra 8 or 10 hours
makes a significant difference in how many of the slower buildfarm
critters will have reported in by Monday.

			regards, tom lane

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