Re: postmaster deadlock while logging after syslogger exited

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: David Pacheco <dap(at)joyent(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: postmaster deadlock while logging after syslogger exited
Date: 2017-11-17 03:29:31
Message-ID: 24571.1510889371@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andres Freund <andres(at)anarazel(dot)de> writes:
> It doesn't seem impossible to get into a situation where syslogger is
> the source of the OOM. Just enabling a lot of logging in a workload with
> many large query strings might do it. So making it less likely to be
> killed might make the problem worse...

Hm, so that's another angle David didn't report on: is it possible that
his workload could have resulted in a very large volume of incomplete
in-progress log messages?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message marcelo 2017-11-17 12:51:35 mild modification to pg_dump
Previous Message Andres Freund 2017-11-17 03:20:56 Re: postmaster deadlock while logging after syslogger exited