From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | josh(at)agliodbs(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Function to kill backend |
Date: | 2004-04-04 02:56:39 |
Message-ID: | 406F7967.1090409@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> This is a commonly requested feature by DBA's migrating from SQL Server and
> Oracle. In those databases, there is a GUI to monitor database requests,
> and potentially kill them to resolve deadlocks or runaway queries (though, in
> the case of SQL server, it does not work). Right now, it is very difficult
> for any of our GUI projects to construct such an interface due to the
> necessity of root shell access.
Yes, MySQL can do it too.
http://www.mysql.com/doc/en/KILL.html
I would love to have a KILL <pid> command in postgres. I don't know how
you would restrict it to only being able to kill postgres backends though.
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2004-04-04 03:22:06 | Re: Function to kill backend |
Previous Message | Josh Berkus | 2004-04-04 01:09:35 | Re: Function to kill backend |