Re: What to do when dynamic shared memory control segment is corrupt - Mailing list pgsql-general

From Peter Geoghegan
Subject Re: What to do when dynamic shared memory control segment is corrupt
Date
Msg-id CAH2-WzmOEWJh-v_X8a=_YDyF9Jam51fb2jfxNRmM9QuOhJ1w-w@mail.gmail.com
Whole thread Raw
In response to Re: What to do when dynamic shared memory control segment is corrupt  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: What to do when dynamic shared memory control segment is corrupt  (Sherrylyn Branchaw <sbranchaw@gmail.com>)
List pgsql-general
On Mon, Jun 18, 2018 at 1:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

Unhandled C++ exceptions end up calling std::abort(). I've seen bugs
in modules like PL/V8 that were caused by this. The symptom was a
mysterious message in the logs about SIGABRT. Perhaps that's what
happened here?

What extensions are installed, if any?

-- 
Peter Geoghegan


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: What to do when dynamic shared memory control segment is corrupt
Next
From: Juan Manuel Cuello
Date:
Subject: High WriteLatency RDS Postgres 9.3.20