Thomas Munro <[email protected]> writes:
> On Fri, Apr 19, 2019 at 10:22 AM Tom Lane <[email protected]> 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
