Thanks for the tip, we haven't tried that yet although I think we would have the same behavior as it seems to be the next connection after the database is down that hangs (no matter if it's a SELECT 1 or an actual query).
On Fri, Oct 17, 2014 at 5:38 PM, Jonathan Vanasco <[email protected]> wrote: > Have you tried a Pessimistic Disconnect strategy? > > > http://docs.sqlalchemy.org/en/latest/core/pooling.html#dealing-with-disconnects > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sqlalchemy" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sqlalchemy/NANPH1QWgMM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
