Re: Race conditions with checkpointer and shutdown
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-19T03:48:07Z
Lists: pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes: > On Fri, Apr 19, 2019 at 10:22 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Maybe what we should be looking for is "why doesn't the walreceiver >> shut down"? But the dragonet log you quote above shows the walreceiver >> exiting, or at least starting to exit. Tis a puzzlement. > ... Is there some way that the exit code could hang > *after* that due to corruption of libc resources (FILE streams, > malloc, ...)? It doesn't seem likely to me (we'd hopefully see some > more clues) but I thought I'd mention the idea. I agree it's not likely ... but that's part of the reason I was thinking about adding some postmaster logging. Whatever we're chasing here is "not likely", per the observed buildfarm failure rate. regards, tom lane
Commits
-
In walreceiver, don't try to do ereport() in a signal handler.
- ac8f2e1ef34f 10.9 landed
- 9346d396fd4a 11.4 landed
- a1a789eb5ac8 12.0 landed