Psycopg2 connection timeout. Jul 23, 2025 · The connection timeout specifies how long the client will wait for a connection to be established with the PostgreSQL server before giving up. Jul 5, 2021 · How to configure statement timeout in psycopg2 If you are concerned that in certain scenarios, your PostgreSQL query may take exceptionally long to execute and overwhelm your DB and/or make your application or API incredibly slow, you may want to add a time limit to your query execution. . The problem is solved in psycopg 3, but not backported. Oct 19, 2023 · However, your application loses its connection to the server for a short period of time of typically less than 60 seconds at most. There is also a corresponding parameter keepalives_idle on the client side that you could set when you connect with psycopg2. Feb 9, 2010 · The connection will be unusable from this point forward; an InterfaceError will be raised if any operation is attempted with the connection. Some events can occasionally take longer to mitigate, such as when a large transaction causes a long-running recovery. Both should do the trick. See the libpq docs for a list of all the parameters supported. In this example, the connect_timeout parameter is set to 10 seconds. Sep 12, 2020 · To defend against that, set the parameter tcp_keepalives_idle on the server to something less than the default 2 hours. Aug 26, 2022 · You can pass the connect_timeout as a keyword argument or DSN string option. The same applies to all cursor objects trying to use the connection. When using the keyword arguments syntax to the connect function it is possible to use any of the libpg supported connection parameters. Note that it doesn't work for async connections (including greenlet connections). Among those there is connect_timeout in seconds: host=dhost, database=ddatabase, user=duser, password=dpassword, connect_timeout=3. qtjqr cftsec avacxj isg virgd ddeze tel isr gqyqelr slehl