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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Sherrylyn Branchaw <sbranchaw(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: What to do when dynamic shared memory control segment is corrupt
Date: 2018-06-18 21:17:10
Message-ID: CAH2-WzmOEWJh-v_X8a=_YDyF9Jam51fb2jfxNRmM9QuOhJ1w-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 18, 2018 at 1:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Juan Manuel Cuello 2018-06-18 21:43:06 High WriteLatency RDS Postgres 9.3.20
Previous Message Tom Lane 2018-06-18 20:03:45 Re: What to do when dynamic shared memory control segment is corrupt