delta/python-packages/psycopg2.git/sandbox/test_green_error.py, branch separate-binary github.com: psycopg/psycopg2.git Close the connection on error in callback 2012-10-09T01:01:29+00:00 Daniele Varrazzo daniele.varrazzo@gmail.com 2012-10-06T10:58:52+00:00 58d048198f88b882ce7530b5eb2dec672c36c8a0 Unfortunately PQcancel blocks, so it's not better than PQgetResult. It has been suggested to use PQreset in non-blocking way but this would give the Python program the burden of handling a connection done but not configured in an unexpected place. 
Unfortunately PQcancel blocks, so it's not better than PQgetResult.
It has been suggested to use PQreset in non-blocking way but this would give
the Python program the burden of handling a connection done but not configured
in an unexpected place.
Get the result from the connection after the green panic 2012-10-09T01:01:29+00:00 Daniele Varrazzo daniele.varrazzo@gmail.com 2012-10-06T00:45:24+00:00 7632e1ae46d0f65b6302f02d0b6a5c236b84c0fe Otherwise the connection won't be usable in case we manage to put it back on track (libpq reports "another command is already in progress") 
Otherwise the connection won't be usable in case we manage
to put it back on track (libpq reports "another command is
already in progress")
Attempt to fix issue #113. 2012-10-09T01:01:29+00:00 Daniele Varrazzo daniele.varrazzo@gmail.com 2012-10-06T00:10:41+00:00 fa032f09fb5bdbbb0f804b346978525939261c97 If the network is down, trying to read blocking will hang the process hard (ctrl-c not working). Send a cancel signal instead (as suggested in http://archives.postgresql.org/pgsql-hackers/2012-07/msg00903.php) and go back into a green polling: this should allow a further error (e.g. another ctrl-c) to break the loop. In this case we cannot assume anything about the state of the connection, so we close it. 
If the network is down, trying to read blocking will hang the process hard
(ctrl-c not working). Send a cancel signal instead (as suggested in
http://archives.postgresql.org/pgsql-hackers/2012-07/msg00903.php) and go
back into a green polling: this should allow a further error (e.g. another
ctrl-c) to break the loop. In this case we cannot assume anything about
the state of the connection, so we close it.