Re: [GENERAL] postmaster deadlock while logging after syslogger exited - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Date
Msg-id 24571.1510889371@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] postmaster deadlock while logging after syslogger exited  (Andres Freund <andres@anarazel.de>)
Responses Re: [GENERAL] postmaster deadlock while logging after syslogger exited  (David Pacheco <dap@joyent.com>)
List pgsql-general
Andres Freund <andres@anarazel.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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Next
From: marcelo
Date:
Subject: [GENERAL] mild modification to pg_dump