Re: pgsql: Use standard interrupt handling in logical replication launcher.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Use standard interrupt handling in logical replication launcher.
Date: 2017-06-09 21:55:23
Message-ID: 21967.1497045323@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-06-09 17:47:23 -0400, Tom Lane wrote:
>> 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.

Yeah, I'm also suspecting that it's somehow timing related, because of
the similar-looking CLOBBER_CACHE_ALWAYS failures. I'm currently trying
to see if I can duplicate it that way.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-06-09 23:50:45 pgsql: doc: Improve types in example
Previous Message Andres Freund 2017-06-09 21:52:15 Re: pgsql: Use standard interrupt handling in logical replication launcher.