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

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

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

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

Cc: Andres Freund <andres@anarazel.de>, Michael Paquier <michael@paquier.xyz>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org

Date: 2019-05-23T15:27:33Z

Lists: pgsql-bugs

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> 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.

Fair enough.  I stuck my patch into the CF app[1] so we don't forget.

			regards, tom lane

[1] https://commitfest.postgresql.org/23/2126/

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