RE: statement timeout with psqlODBC 09.05.300+

From: Richard Hetherington <hetheringtonrichard(at)hotmail(dot)com>
To: Michael Michaud <Michael(dot)Michaud(at)ign(dot)fr>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: RE: statement timeout with psqlODBC 09.05.300+
Date: 2018-01-26 14:13:23
Message-ID: DB6P18901MB016504243C86C8D50B1020BDBBE00@DB6P18901MB0165.EURP189.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Michael, the statement_timeout value is in milliseconds, however if setting directly against the Connection then it is in seconds. I guess behind the scenes the value is converted to milliseconds before issuing the SET statement_timeout command to Postgres.

Regards,

Richard

-----Original Message-----
From: Michael Michaud [mailto:Michael(dot)Michaud(at)ign(dot)fr]
Sent: 25 January 2018 19:11
To: pgsql-odbc(at)postgresql(dot)org
Subject: RE : statement timeout with psqlODBC 09.05.300+

Thanks for the quick answer.

Our codebase is rather large and old, and prepending a SQL commands to all existing queries would really be annoying. But anyway, thank you for the tip. I learn two things from it
- setting the statement_timeout just before the query overwrites the default setting of the driver
- the timeout setting is in milliseconds, not in seconds.

Michaël
________________________________________
De : Richard Hetherington [hetheringtonrichard(at)hotmail(dot)com] Date d'envoi : jeudi 25 janvier 2018 18:15 À : Michael Michaud; pgsql-odbc(at)postgresql(dot)org Objet : RE: statement timeout with psqlODBC 09.05.300+

I reported this issue a couple of years ago when I figured out the ODBC Command Timeout value configured on a connection was being ignored. I found a work around to prepend this to all queries needing a custom configured COMMAND timeout.

SET statement_timeout = ( YourCommandTimeoutInSeconds * 1000 ); SELECT * FROM bla;

Hope this helps.

Regards,

Richard Hetherington
Senior Web Developer

Aspire HE Technologies Ltd
(Formally Aztec Retail Solutions Limited) c/o John Smith & Son Group Ltd Ash House Headlands Business Park Ringwood, Hampshire
BH24 3PB
Tel: +44 (0)1425 485957 ext. 315

-----Original Message-----
From: michael [mailto:michael(dot)michaud(at)ign(dot)fr]
Sent: 25 January 2018 15:51
To: pgsql-odbc(at)postgresql(dot)org
Subject: statement timeout with psqlODBC 09.05.300+

Hi,

This ticket is related to
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.postgresql-archive.org%2FBUG-odbc-statement-timeout-gets-set-to-30000-td5992591.html&data=02%7C01%7C%7C81c51c8f9a2946fd464e08d5640c496a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636524926286264264&sdata=LRP3sJ4c0lqj07OBvbaILmtG5EHXVPhWkBsxadcLOpk%3D&reserved=0

The client using the ODBC Driver is on Windows 7, must be x86 compatible, and connect to a 9.6 postgresql database.
from 09.05.300+ version of the ODBC driver x86 (tested up to 10.01), queries which used to work fine with drivers 08.x now throw "ERROR: canceling statement due to statement timeout;"

It seems that there is now a default setting for statement timeout coming with 9.5+ versions of the driver (less than 1 mn), and I did not find any way to change this setting.
I tried to find a key in the Windows Registry Database or to set the timeout in the connection string but did not find good documentation and did not succeeded.
Any help woul be appreciated

--
Sent from: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.postgresql-archive.org%2FPostgreSQL-odbc-f2186591.html&data=02%7C01%7C%7C81c51c8f9a2946fd464e08d5640c496a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636524926286264264&sdata=2MW%2FYoQngU0%2FSs0DlNxqnXY6Ewv8xgDLoZbylNjAss8%3D&reserved=0

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Wolfgang Apolinarski 2018-02-01 16:45:30 ODBC - Retrieving info messages - RAISE NOTICE
Previous Message Michael Michaud 2018-01-25 19:10:41 RE : statement timeout with psqlODBC 09.05.300+