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 <guilla...@lelarge.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 > > -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
