Re: [HACKERS] Function to kill backend

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Function to kill backend
Date: 2004-07-24 22:51:01
Message-ID: 7921.1090709461@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, I see your point. Can anyone remember why this was needed? I
> remember Magnus wanted query cancel, but what was the logic for session
> termination?

I think the argument for it went along the lines of "what if you've got
a misbehaving client that continually issues expensive queries, so
canceling any one query doesn't help?" I found this unconvincing, as
a client that obstreperous might simply reconnect and start issuing the
same queries again; so having a session-kill tool doesn't really get you
much further. I recall being voted down though ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-07-24 22:55:33 Re: [HACKERS] Function to kill backend
Previous Message Bruce Momjian 2004-07-24 21:44:14 Re: [HACKERS] Function to kill backend

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-07-24 22:55:33 Re: [HACKERS] Function to kill backend
Previous Message Bruce Momjian 2004-07-24 21:44:14 Re: [HACKERS] Function to kill backend