Re: Function to kill backend

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: Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Function to kill backend
Date: 2004-04-06 19:37:37
Message-ID: 200404061937.i36Jbbv00848@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > If there is a problem, maybe we can fix it, or perhap have the kill
> > function use SIGINT, then wait for the query to cancel, then SIGTERM.
>
> Well, if someone could prove that the SIGTERM path is equivalent to
> a transaction-aborting error followed by normal client disconnect,
> I'd feel a lot better about its reliability. We know those two code
> paths work well.

As far as I know, most database systems have the ability to kill an
individual session, and I think we need that functionality too, as I
described in my report example.

> Right now I do not think they are equivalent, but maybe they could be
> made so.

Let me look into it.

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2004-04-06 19:38:26 Re: Function to kill backend
Previous Message Bruce Momjian 2004-04-06 19:36:35 Re: Function to kill backend

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-04-06 20:01:52 Re: [HACKERS] logging statement levels
Previous Message Tom Lane 2004-04-06 19:34:57 Re: Function to kill backend