Storm already catches all DatabaseError subclasses (including OperationalError) that set the psycopg2 connection object's closed attribute. So for the bug's situation to happen, I think it means psycopg2 is not flagging the connection as closed if this TCP failure happens.
Storm already catches all DatabaseError subclasses (including OperationalError) that set the psycopg2 connection object's closed attribute. So for the bug's situation to happen, I think it means psycopg2 is not flagging the connection as closed if this TCP failure happens.