Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event. - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event.
Date
Msg-id CAEepm=3TpxrEO1Hd7s2H9MitJpBX1QNW957yr2nQHyqNVF86Jg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event.  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: pgsql: Add WL_EXIT_ON_PM_DEATH pseudo-event.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Nov 25, 2018 at 12:59 PM Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Sun, Nov 25, 2018 at 3:38 AM Christoph Berg <myon@debian.org> wrote:
> > TRAP: FailedAssertion(»!(!IsUnderPostmaster || (wakeEvents & (1 << 5)) || (wakeEvents & (1 << 4)))«, Datei:
»/build/postgresql-12-JElZNq/postgresql-12-12~~devel~20181124.1158/build/../src/backend/storage/ipc/latch.c«,Zeile:
389)
> > 2018-11-24 15:20:43.193 CET [17834] LOG:  Serverprozess (PID 18425) wurde von Signal 6 beendet: Aborted

Fix pushed.

By way of penance, I have now configured PG_TEST_EXTRA="ssl ldap
kerberos" for my build farm animals elver and eelpout.  elver should
pass at the next build, as I just tested it with --nosend, but eelpout
is so slow I'll just take my chances see if that works.  I'll also
review the firewall config on those VMs, since apparently everyone is
too chicken to run those tests, perhaps for those sorts of reasons.
I've also set those tests up for cfbot, which would have caught this
when draft patches were posted, and also enabled -Werror on cfbot
which would have caught a GCC warning I missed because I usually
develop/test with clang.

--
Thomas Munro
http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Block level parallel vacuum
Next
From: Surafel Temesgen
Date:
Subject: Re: FETCH FIRST clause PERCENT option