Re: pgsql: Fix signal handling in logical replication workers

From: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: pgsql: Fix signal handling in logical replication workers
Date: 2017-06-03 01:13:52
Message-ID: a1c7687e-0448-1cdd-596f-8dc30312e971@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 03/06/17 02:59, Tom Lane wrote:
> I wrote:
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>> Fix signal handling in logical replication workers
>
>> It looks like this broke buildfarm member nightjar.
>> Not clear why - I don't see anything especially platform-specific
>> in the patch.
>
> To muddy the waters further, I tried to duplicate the failure on
> FreeBSD 11.0/x86_64, and it seems to pass just fine. Maybe Andrew
> can look into why nightjar is failing.
>

There is still one locking patch pending (well pending to be written), I
would not be surprised if there is race condition in shutdown somewhere
before that's done.

--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-06-03 02:23:15 pgsql: Allow parallelism in COPY (query) TO ...;
Previous Message Tom Lane 2017-06-03 00:59:36 Re: pgsql: Fix signal handling in logical replication workers