From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Have walsenders participate in procsignal infrastructure. |
Date: | 2017-06-06 02:25:22 |
Message-ID: | E1dI4BO-0004tR-BM@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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.fdzvvvbrz4nckrow@alap3.anarazel.de
Backpatch: 9.4, earlier commits don't seem to benefit sufficiently
Branch
------
REL9_5_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e1319f64ec07b2a6109ec670c056525ac58ef5a8
Modified Files
--------------
src/backend/replication/walsender.c | 14 +-------------
1 file changed, 1 insertion(+), 13 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-06-06 02:25:25 | pgsql: Have walsenders participate in procsignal infrastructure. |
Previous Message | Andres Freund | 2017-06-06 02:25:18 | pgsql: Prevent possibility of panics during shutdown checkpoint. |