| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Durumdara <durumdara(at)gmail(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Question about aborting |
| Date: | 2011-07-06 20:08:34 |
| Message-ID: | 1309982914.2096.1.camel@laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Wed, 2011-07-06 at 16:09 +0200, Durumdara wrote:
> Dear Author!
>
> I need to know that which ways I have to abort a runaway query/stored procedure.
>
> As I saw, pgAdmin CAN abourt my own queries.
> It is ok.
>
> But what's happens when:
> - somebody (not me) started a query that have too less filter, and
> becomes unlimited
> - I started a query or stored proc what is buggy, and gets into
> infinitive state because of wrong loops, but the TCP socket
> disconnected by a failure, or wifi problem, so my session killed by
> the server
>
> As I saw, pgAdmin have a monitoring tool which show me these queries.
>
> But have some tool in the pgAdmin with I can abort these runaway statements?
>
The server status tool can help you stop runaway queries. There's a
button for that in the toolbar.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durumdara | 2011-07-07 07:22:14 | Re: Question about aborting |
| Previous Message | Durumdara | 2011-07-06 14:09:53 | Question about aborting |