On Mon, Nov 6, 2017 at 12:35 PM, Tom Lane wrote:
> David Pacheco 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 postm
On Mon, Nov 6, 2017 at 12:35 PM, Tom Lane wrote:
> David Pacheco writes:
> > ... that process appears to have exited due to a fatal error
> > (out of memory). (I know it exited because the process still exists in
> the
> > kernel -- it hasn't been reaped yet -- and
Hello,
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.
