Re: Proof of concept: standalone backend with full FE/BE protocol - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Proof of concept: standalone backend with full FE/BE protocol
Date
Msg-id CABUevEyLCzjVnn6NXUUQBQ8A9J=0KY1sV1n-OQom9jCFbkZAaw@mail.gmail.com
Whole thread Raw
In response to Re: Proof of concept: standalone backend with full FE/BE protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proof of concept: standalone backend with full FE/BE protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Sep 3, 2012 at 7:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Kapila <amit.kapila@huawei.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 HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Next
From: Fujii Masao
Date:
Subject: Re: Cascading replication and recovery_target_timeline='latest'