----- Original message -----
> So the specific case is:
> - connect to the postgres database using psycopg2 while network is up
> - run some queries, get the results fine etc
> - send a query
> - the network goes down before the result to this last query has been
> received - neither a result nor an error callback gets called - as far
> as I can see (using txpostgres.ConnectionPool)
>
> What's the proper way to deal with that?
I'll try to reproduce this problem, AIUI you should have the Deferred errback if the connection is lost, but perhaps it
takessome time for Twisted to detect it (actually it takes time for the kernel to detect it). You might try playing
withyour TCP keepalive settings.
Another option is implementing a timeout with a callLater. The problem there is that it requires additional code and
txpostgresdoes not support query cancellation (yet, it's on the roadmap).
Cheers,
Jan