| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Kevin Brown <kevin(at)sysexperts(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Killing the backend to cancel a long waiting query |
| Date: | 2003-09-21 06:25:16 |
| Message-ID: | 20030921142434.S61926-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces pgsql-odbc |
> 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.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-09-21 06:25:43 | Re: Can't build latest CVS: |
| Previous Message | Christopher Kings-Lynne | 2003-09-21 06:06:51 | Can't build latest CVS: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jürgen Cappel | 2003-09-21 06:46:02 | ECPG and structure declaration |
| Previous Message | Kevin Brown | 2003-09-21 05:42:24 | Re: Killing the backend to cancel a long waiting query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mainlander | 2003-09-21 06:53:28 | Re: Suppressing public. in tables names |
| Previous Message | Kevin Brown | 2003-09-21 05:42:24 | Re: Killing the backend to cancel a long waiting query |