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: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
Andres Freund <andres@anarazel.de>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>,
pgsql-bugs@lists.postgresql.org
Date: 2019-09-11T15:47:07Z
Lists: pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes: > On Tue, Sep 10, 2019 at 10:58:52AM -0400, Tom Lane wrote: >> Here's a version that does it like that. After studying things a bit, >> it seemed like a good idea to also move RemovePgTempFiles() down, >> so that that possibly-slow step still occurs after making the external >> PID file. Everything else that we've moved to before that step >> should be reasonably quick. > Good point. Nothing more to add with this version. Thanks for > caring. I did one final round of testing and noted that in a Linux EXEC_BACKEND build, this last change causes the race condition that was noted upthread: RemovePgTempFiles could remove the parameter file that the syslogger process is supposed to consume. So I split off the clearing of that subdirectory as we'd discussed, and pushed it. Thanks for reviewing! regards, tom lane
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