From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proof of concept: standalone backend with full FE/BE protocol |
Date: | 2012-09-03 17:08:47 |
Message-ID: | CABUevEyLCzjVnn6NXUUQBQ8A9J=0KY1sV1n-OQom9jCFbkZAaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 3, 2012 at 7:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Kapila <amit(dot)kapila(at)huawei(dot)com> writes:
>>> 8. PQcancel needs some work - it can't do what it does now, but it could
>>> do kill(conn->postgres_pid, SIGINT) instead. At least in Unix. I have no
>>> idea what we'd do in Windows. This doesn't matter for pg_upgrade of course,
>>> but it'd be important for manual use of this mode.
>
>> Can pgkill(int pid, int sig) API of PG be used to achieve the same on
>> Windows.
>
> Hmm, after looking at src/port/kill.c it doesn't seem like there's much
> of a problem with doing that. I had had the idea that our kill
> emulation only worked within the backend environment, but of course
> pg_ctl wouldn't work if that were so. So this is easier than I thought.
Yeah, kill works fine from non-backend as long as the *receiver* has
our backend environment.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2012-09-03 17:43:00 | Re: Cascading replication and recovery_target_timeline='latest' |
Previous Message | Tom Lane | 2012-09-03 17:07:11 | Re: Proof of concept: standalone backend with full FE/BE protocol |