Re: What to do when dynamic shared memory control segment is corrupt

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: What to do when dynamic shared memory control segment is corrupt
Дата
Msg-id 24033.1529352225@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: What to do when dynamic shared memory control segment is corrupt  (Andres Freund <andres@anarazel.de>)
Ответы Re: What to do when dynamic shared memory control segment is corrupt
Список pgsql-general
Andres Freund <andres@anarazel.de> writes:
> On 2018-06-18 12:30:13 -0400, Tom Lane wrote:
>> Sherrylyn Branchaw <sbranchaw@gmail.com> writes:
>>> LOG:  server process (PID 138529) was terminated by signal 6: Aborted

>> Hm ... were these installations built with --enable-cassert?  If not,
>> an abort trap seems pretty odd.

> PANIC does an abort, so that's not too surprising...

Hm, I supposed that Sherrylyn would've noticed any PANIC entries in
the log.  The TRAP message from an assertion failure could've escaped
notice though, even assuming that her logging setup captured it.

            regards, tom lane


В списке pgsql-general по дате отправления:

Предыдущее
От: Robert Creager
Дата:
Сообщение: Re: Query hitting empty tables taking 48 minutes
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: What to do when dynamic shared memory control segment is corrupt