Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
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-20T01:04:27Z
Lists: pgsql-bugs 
On Sun, May 19, 2019 at 11:05:22AM -0400, Tom Lane wrote:
> 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.

Thanks for doing that before I was able to come back, the reverted
version looks fine to me.
--
Michael

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