Skip site navigation (1) Skip section navigation (2)

hanging select processes

From: John Rogers <John(at)delosis(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: hanging select processes
Date: 2004-07-19 10:18:59
Message-ID: 40FBA013.3090905@delosis.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi,
I am using the odbc driver to provide MS Acess with a view on our 
postgres db, securing the connection using stunnel.

Everthing works fine, and it seems to be a fantastic solution to give 
our clients a user friendly look at the data.
the only problem we have discovered when testing this out is that if the 
client runs a query in access and then kills the access process on their 
computer. we end up with a postgres SELECT thread running at 99% cpu 
time on our backend. I have found a thread possible hinting at this in 
the archives - regarding 'zombie' processes, but these are not zombie 
processes - we can kill them though a restart of postgres is required to 
get it all working again.

Now we cant stop our clients being idiots - i guess we'd all be a lot 
happier if we could! Is there a way to mitigate or even stop this errant 
behaviour? surely postgres should stop the select if the client 
dissapears in a puff of smoke?
cheers
John

Responses

pgsql-odbc by date

Next:From: Dave PageDate: 2004-07-19 10:53:55
Subject: 07.05.0001 Snapshot available
Previous:From: Dave PageDate: 2004-07-19 10:06:50
Subject: Todo items for developers...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group