Have walsenders participate in procsignal infrastructure.
authorAndres Freund
Tue, 6 Jun 2017 01:53:42 +0000 (18:53 -0700)
committerAndres Freund
Tue, 6 Jun 2017 02:18:16 +0000 (19:18 -0700)
commite1319f64ec07b2a6109ec670c056525ac58ef5a8
tree89682d7f3a779ab65069716ce7c9e88788fc4048
parentb2482ab83242d895e0e0eaa362b5a918d15ce408
Have walsenders participate in procsignal infrastructure.

The non-participation in procsignal was a problem for both changes in
master, e.g. parallelism not working for normal statements run in
walsender backends, and older branches, e.g. recovery conflicts and
catchup interrupts not working for logical decoding walsenders.

This commit thus replaces the previous WalSndXLogSendHandler with
procsignal_sigusr1_handler.  In branches since db0f6cad48 that can
lead to additional SetLatch calls, but that only rarely seems to make
a difference.

Author: Andres Freund
Reviewed-By: Michael Paquier
Discussion: https://postgr.es/m/20170421014030[email protected]
Backpatch: 9.4, earlier commits don't seem to benefit sufficiently
src/backend/replication/walsender.c