Re: [GENERAL] postmaster deadlock while logging after syslogger exited

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Дата
Msg-id 24571.1510889371@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [GENERAL] postmaster deadlock while logging after syslogger exited  (Andres Freund <andres@anarazel.de>)
Ответы Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Список 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 по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Следующее
От: marcelo
Дата:
Сообщение: [GENERAL] mild modification to pg_dump