orphaned runaway queries after killing pgadmin - Mailing list pgadmin-support

From Dan Halbert
Subject orphaned runaway queries after killing pgadmin
Date
Msg-id 1289851856.131324391@beta.apps.rackspace.com
Whole thread Raw
Responses Re: orphaned runaway queries after killing pgadmin
List pgadmin-support
<font face="arial" size="2"><p>Today I end up killing pgadmin a few times while inadvertantly running some huge queries
andsome ALTER requests that were blocked due to the queries. I should have canceled the queries from pgadmin, but I
didn't.When I saw that the postgres processes were using up 100% of the CPU, I looked up the process id's of the ALTERs
andrunaway queries in pg_stat_activity and did the equivalent of "pg_ctl kill".<p> <p>I don't think this is really
pgadmin'sfault, but why doesn't PostgreSQL notice that the query requestor has vanished and quit working on the query?
Apologiesif you think I should ask this on a general PG list.<p> <p>Thanks,<p>Dan</font> 

pgadmin-support by date:

Previous
From: Dave Page
Date:
Subject: Re: PGAdmin - still no jobs node.
Next
From: Guillaume Lelarge
Date:
Subject: Re: orphaned runaway queries after killing pgadmin