On Fri, Jun 2, 2017 at 7:05 AM, Andres Freund <and...@anarazel.de> wrote: > I'm a unhappy how this is reusing SIGINT for WalSndLastCycleHandler. > Normally INT is used cancel interrupts, and since walsender is now also > working as a normal backend, this overlap is bad. Even for plain > walsender backend this seems bad, because now non-superusers replication > users will terminate replication connections when they do > pg_cancel_backend(). For replication=dbname users it's especially bad > because there can be completely legitimate uses of pg_cancel_backend().
Signals for WAL senders are set in WalSndSignals() which uses SIG_IGN for SIGINT now in ~9.6, and StatementCancelHandler does not get set up for a non-am_walsender backend. Am I missing something? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
