I would also throw a few debug lines into psycopg2 and ensure that library is creating a connection with the params you intend.
On Wednesday, February 26, 2020 at 11:19:28 AM UTC-5, Karim Gillani wrote: > > Thanks. I don't believe this is a Red Hat issue as much as a > configuration issue. This is because I can replicate the issue using PSQL > and using the connect_timeout argument in PSQL, I can fix it. With the > complexity of using flask-sqlalchemy which uses sqlalchemy to pass > arguments to psycopg2 to libpq, it is difficult to see where the issue > actually is. Based on the links you provided, I am passing the > connect_timeout parameter correctly. I am not sure what to do now. I am > guessing I will need to somehow figure out if the parameter is being > passed. I think I will play with getting connection.get_dsn_parameters() > function to display the parameters. > > Karim > -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- 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 sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/b6afe29e-6a42-41da-a67b-fa8176a49b28%40googlegroups.com.
