Skip site navigation (1) Skip section navigation (2)  Re:
psycopg2 (async) socket timeout  From: Danny Milosavljevic
<danny(dot)milo+ml(at)gmail(dot)com> Cc:
psycopg(at)postgresql(dot)org Subject: Re: psycopg2 (async)
socket timeout Date: 2011-02-14 18:59:41 Message-ID: (view raw
or flat) Lists: psycopg  2011/2/9 Jan Urbański
<wulczer(at)wulczer(dot)org>: > I'll try to reproduce this
problem, AIUI you should have the Deferred errback if the
connection is lost, but perhaps it takes some time for Twisted
to detect it (actually it takes time for the kernel to detect
it). You might try playing with your TCP keepalive settings.
I'm trying. No luck so far... says "If you rely on TCP timeouts,
expect as much as two hours (the precise amount is platform
specific) to pass between when the disruption occurs and when
connectionLost is called". Oops.  Hmm, even when I connect, then
just down the network interface and only after that call
runQuery, it is also never calling back anything (well, I didn't
wait more than hal