On Mon, Nov 6, 2017 at 12:35 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
David Pacheco <dap@xxxxxxxxxx> writes:
> I ran into what appears to be a deadlock in the logging subsystem. It
> looks like what happened was that the syslogger process exited because it
> ran out of memory. But before the postmaster got a chance to handle the
> SIGCLD to restart it, it handled a SIGUSR1 to start an autovacuum worker.
> That also failed, and the postmaster went to log a message about it, but
> it's blocked on the pipe that's normally connected to the syslogger,
> presumably because the pipe is full because the syslogger is gone and
> hasn't read from it.
Ugh.
Should I file a bug on this issue?
Thanks,
Dave
