From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Use standard interrupt handling in logical replication launcher. |
Date: | 2017-06-09 21:52:15 |
Message-ID: | 20170609215215.xrwp6suwitextrde@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 2017-06-09 17:47:23 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-06-09 21:55:23 | Re: pgsql: Use standard interrupt handling in logical replication launcher. |
Previous Message | Tom Lane | 2017-06-09 21:47:23 | Re: pgsql: Use standard interrupt handling in logical replication launcher. |