Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2019-05-16T02:59:38Z
Lists: pgsql-bugs
Hi, On 2019-05-16 11:19:03 +0900, Michael Paquier wrote: > So it seems that reverting 57431a91 is an option on the table? > Opinions? Seems a bit early to go that way. Given that this bug was reported yesterday, and that there's reasonable sketches how to fix this, I'm not clear why reverting would already be on the table? Greetings, Andres Freund
Commits
-
Rearrange postmaster's startup sequence for better syslogger results.
- 9a86f03b4e8c 13.0 landed
-
Improve logrotate test so that it meaningfully exercises syslogger.
- 9d5c22d28f8c 12.0 landed
-
Revert "postmaster: Start syslogger earlier".
- 833451552925 12.0 landed
-
postmaster: Start syslogger earlier
- 57431a911d3a 12.0 cited