On 06/02/2017 09:13 PM, Petr Jelinek wrote:
> On 03/06/17 02:59, Tom Lane wrote:
>> I wrote:
>>> Peter Eisentraut 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-s
On 03/06/17 02:59, Tom Lane wrote:
> I wrote:
>> Peter Eisentraut 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
I wrote:
> Peter Eisentraut 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
Fre
Peter Eisentraut 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.
regards, tom lane
--
Sent via pgsql-committers mailing list
Fix signal handling in logical replication workers
The logical replication worker processes now use the normal die()
handler for SIGTERM and CHECK_FOR_INTERRUPTS() instead of custom code.
One problem before was that the apply worker would not exit promptly
when a subscription was dropped, which co
