Re: [COMMITTERS] pgsql: Use standard interrupt handling in logicalreplication launcher. - Mailing list pgsql-committers

From Andres Freund
Subject Re: [COMMITTERS] pgsql: Use standard interrupt handling in logicalreplication launcher.
Date
Msg-id 20170609215215.xrwp6suwitextrde@alap3.anarazel.de
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Use standard interrupt handling in logical replication launcher.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Use standard interrupt handling in logical replication launcher.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 2017-06-09 17:47:23 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > Use standard interrupt handling in logical replication launcher.
>
> This seems to have fixed nightjar's subscription-test failures.
> Were you expecting that?

Well, hoping ;).  Petr had pointed it out as the probable source.


> On the less good side, something seems to have broken the pg_upgrade
> tests recently on skink and some (not all) of the CLOBBER_CACHE_ALWAYS
> animals.

Yea, I saw skinks failure. Unfortunately it seems we're either not
seeing the bleat because it's in some logfile that's hidden, or it's not
a valgrind visible failure and "just" triggered by the long runtime.

I've a couple things that are of higher priority, but if not I'd planned
to locally try running the pg_upgrade tests under valgrind.

Greetings,

Andres Freund


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Use standard interrupt handling in logical replication launcher.
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Use standard interrupt handling in logical replication launcher.