.. changelog::
:version: 0.9.8
+ .. change::
+ :tags: bug, postgresql
+ :versions: 1.0.0
+ :tickets: 3021
+
+ A revisit to this issue first patched in 0.9.5, apparently
+ psycopg2's ``.closed`` accessor is not as reliable as we assumed,
+ so we have added an explicit check for the exception messages
+ "SSL SYSCALL error: Bad file descriptor" and
+ "SSL SYSCALL error: EOF detected" when detecting an
+ is-disconnect scenario. We will continue to consult psycopg2's
+ connection.closed as a first check.
+
.. change::
:tags: bug, orm, engine
:versions: 1.0.0
def is_disconnect(self, e, connection, cursor):
if isinstance(e, self.dbapi.Error):
# check the "closed" flag. this might not be
- # present on old psycopg2 versions
+ # present on old psycopg2 versions. Also,
+ # this flag doesn't actually help in a lot of disconnect
+ # situations, so don't rely on it.
if getattr(connection, 'closed', False):
return True
- # legacy checks based on strings. the "closed" check
- # above most likely obviates the need for any of these.
+ # checks based on strings. in the case that .closed
+ # didn't cut it, fall back onto these.
str_e = str(e).partition("\n")[0]
for msg in [
# these error messages from libpq: interfaces/libpq/fe-misc.c
# not sure where this path is originally from, it may
# be obsolete. It really says "losed", not "closed".
'losed the connection unexpectedly',
- # this can occur in newer SSL
- 'connection has been closed unexpectedly'
+ # these can occur in newer SSL
+ 'connection has been closed unexpectedly',
+ 'SSL SYSCALL error: Bad file descriptor',
+ 'SSL SYSCALL error: EOF detected',
]:
idx = str_e.find(msg)
if idx >= 0 and '"' not in str_e[:idx]: