3 Commits

Author	SHA1	Message	Date
Daniele Varrazzo	b61a2a34c4	Close the connection on error in callback ... 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.	2012-10-06 11:58:52 +01:00
Daniele Varrazzo	2611d62283	Get the result from the connection after the green panic ... 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")	2012-10-06 01:45:24 +01:00
Daniele Varrazzo	53b1c70f3a	Attempt to fix issue #113. ... 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.	2012-10-06 01:10:41 +01:00