Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: Use procsignal_sigusr1_handler and RecoveryConflictInterrupt() from walsender? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: Use procsignal_sigusr1_handler and RecoveryConflictInterrupt() from walsender?
Date
Msg-id CA+TgmoZh6M5bTmtZZm1vBpFGHmeNgESe4UrJ3-OwKnu56SKB7g@mail.gmail.com
Whole thread Raw
In response to Re: Use procsignal_sigusr1_handler and RecoveryConflictInterrupt() from walsender?  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Re: Use procsignal_sigusr1_handler and RecoveryConflictInterrupt() from walsender?  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Tree view 
On Mon, Nov 21, 2016 at 3:21 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> I'm still interested in hearing comments from experienced folks about
> whether it's sane to do this at all, rather than have similar
> duplicate signal handling for the walsender.

Well, I mean, if it's reasonable to share code in a given situation,
that is generally better than NOT sharing code...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical decoding on standby
Next
From: Robert Haas
Date:
Subject: Re: Danger of automatic connection reset in psql