From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <mha(at)sollentuna(dot)net>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Function to kill backend |
Date: | 2004-04-06 15:15:16 |
Message-ID: | 200404061515.i36FFGV14684@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> >> If we are going to allow session kill then of course we need
> >> PID for that.
>
> > I still say we need this.
>
> Well, that seems to be the consensus, so I won't stand in the way.
>
> If you like the cancel-by-XID idea then I'd suggest providing two
> functions: pg_cancel_query(XID) to send SIGINT and pg_kill_session(PID)
> to send SIGTERM. I'm not sure if the other two combinations (SIGINT by
> PID and SIGTERM by XID) are worth providing.
Agreed. Two functions, cancel by xid (skips cancel if xid changes
during command), and kill by pid for remote admin apps, is great.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-04-06 15:21:54 | Re: [HACKERS] logging statement levels |
Previous Message | Rod Taylor | 2004-04-06 15:12:19 | Re: zero knowledge users |