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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Sherrylyn Branchaw <sbranchaw(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: What to do when dynamic shared memory control segment is corrupt
Date: 2018-06-18 20:03:45
Message-ID: 24033.1529352225@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:
> On 2018-06-18 12:30:13 -0400, Tom Lane wrote:
>> Sherrylyn Branchaw <sbranchaw(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2018-06-18 21:17:10 Re: What to do when dynamic shared memory control segment is corrupt
Previous Message Robert Creager 2018-06-18 18:20:42 Re: Query hitting empty tables taking 48 minutes