Re: Killing the backend to cancel a long waiting query

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <chriskl(at)familyhealth(dot)com(dot)au>
Cc: <kevin(at)sysexperts(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Killing the backend to cancel a long waiting query
Date: 2003-09-21 10:26:58
Message-ID: 50096.80.177.99.193.1064140018.squirrel@ssl.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces pgsql-odbc

It's rumoured that Christopher Kings-Lynne once said:
>> Wouldn't it be useful, though, to implement a "KILL" or "CANCEL" SQL
>> command that takes a backend ID as its argument (and, of course, does
>> the appropriate checks of whether you're a superuser or the owner of
>> the backend) and sends the appropriate signal to the target backend?
>>
>> That would make it possible for users to kill their own runaway
>> queries without having to run as whatever user PG is running as.
>
>
> It would be awesome for phpPGAdmin as well. eg. Superusers would be
> able to cancel sql queries that gumby users are running, etc.

I'll second that for pgAdmin. I have times in the past where it would have
been useful on my own systems as well.
Regards, Dave.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Spraul 2003-09-21 10:49:45 Re: Align large shared memory allocations
Previous Message Heikki Tuuri 2003-09-21 09:51:10 Re: PostgreSQL not ACID compliant?

Browse pgsql-interfaces by date

  From Date Subject
Next Message Mayank Goyal 2003-09-22 04:22:55 Need information for C++ interface
Previous Message Jürgen Cappel 2003-09-21 06:46:02 ECPG and structure declaration

Browse pgsql-odbc by date

  From Date Subject
Next Message Albert Graef 2003-09-21 11:14:26 Re: problem with multiple result sets
Previous Message Hiroshi Inoue 2003-09-21 09:09:00 Re: LF <-> CR/LF conversion