From: | Durumdara <durumdara(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Question about aborting |
Date: | 2011-07-07 07:22:14 |
Message-ID: | CAEcMXhnJsRBYABAoWLmszP6vhtcX_BHqFx+Z0zBOXF89QMeXag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi!
I'm very-very thanks for it!
I was so tired yesterday, and I don't clicked on any connections, so
the buttons were greyed, and I could not see that there are buttons.
:-)
Client "start" column is too short. May you can save the columns width
to preserve the good size.
Thanks and regards:
dd
2011/7/6 Guillaume Lelarge <guillaume(at)lelarge(dot)info>:
> 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 | Defiant Challenged | 2011-07-07 09:24:30 | Using pgAgent w/o pgAdmin3 on linux |
Previous Message | Guillaume Lelarge | 2011-07-06 20:08:34 | Re: Question about aborting |