Thread: [ODBC] BUG: odbc statement_timeout gets set to 30000
Hi All I've found a problem with at least the 906 and 1000 odbc driver, in that, no matter what statement_timeout is set to, after initially connecting and setting the value to that specified in the connection settings, it is then subsequently set to 30000. This means that queries running longer than 30seconds are failing, which is a major problem. Earlier drivers do not behave in this manner. I'm not a windows person, however, I have found that SET statement_timeout = %d Is present in psqlodbc30a.dll psqlodbc35w.dll, I've used a hex editor to change the above to read SET statement_timeout = 0 This works for us, but it would be good for a fixed driver to be published, I can't see the need for it to be specified in the driver itself, when it can be passed as a connection setting. I suspect that %d variable is being overwritten, so, it would be good if this could be fixed for the next release, either by making sure the statement_timeout doesn't get overwritten when set in the connection settings in the driver gui, or windows registry, or, simply remove it from the driver. I hope that all makes sense Thanks Tony -- Sent from: http://www.postgresql-archive.org/PostgreSQL-odbc-f2186591.html -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
Le 17/11/2017 à 08:34, linuxyeti a écrit : > I've found a problem with at least the 906 and 1000 odbc driver, in that, no > matter what statement_timeout is set to, after initially connecting and > setting the value to that specified in the connection settings, it is then > subsequently set to 30000. I've witnessed it too, and fixed it by setting my ado connection's commandtimeout to 0 in my scripts. (oADODBConn.CommandTimeout = 0) But just like you I was surprised by this change, so it might be a bug. Regards -- Arnaud -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
Hi, On 2017/11/17 16:39, Arnaud L. wrote: > Le 17/11/2017 à 08:34, linuxyeti a écrit : >> I've found a problem with at least the 906 and 1000 odbc driver, in >> that, no >> matter what statement_timeout is set to, after initially connecting and >> setting the value to that specified in the connection settings, it is >> then >> subsequently set to 30000. > > I've witnessed it too, and fixed it by setting my ado connection's > commandtimeout to 0 in my scripts. (oADODBConn.CommandTimeout = 0) The default value of CommandTimeout property is 30. > > But just like you I was surprised by this change, so it might be a bug. It's because of an enhancement (SQL_QUERY_TIMEOUT option support since 9.5.0400) not a bug. regards, Hiroshi Inoue > > > Regards > > -- > Arnaud > > -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
Hi ! Le 17/11/2017 à 09:26, Inoue, Hiroshi a écrit : > It's because of an enhancement (SQL_QUERY_TIMEOUT option support since > 9.5.0400) not a bug. OK, nice to have this feature, but why is the default set at 30s and not 0 ? The new default value breaks scripts that where previsously running without problem. Regards, -- Arnaud -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
Hi Arnaud, On 2017/11/17 20:15, Arnaud L. wrote: > Hi ! > > Le 17/11/2017 à 09:26, Inoue, Hiroshi a écrit : >> It's because of an enhancement (SQL_QUERY_TIMEOUT option support since >> 9.5.0400) not a bug. > > OK, nice to have this feature, but why is the default set at 30s and > not 0 ? The 30s comes from apps or middlewares not from drivers. regards, Hiroshi Inoue > > The new default value breaks scripts that where previsously running > without problem. > > Regards, > > -- > Arnaud > > --- > このメールは、AVG によってウイルス チェックされています。 > http://www.avg.com > > -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
Le 17/11/2017 à 12:32, Inoue, Hiroshi a écrit : >> Le 17/11/2017 à 09:26, Inoue, Hiroshi a écrit : >>> It's because of an enhancement (SQL_QUERY_TIMEOUT option support since >>> 9.5.0400) not a bug. >> >> OK, nice to have this feature, but why is the default set at 30s and >> not 0 ? > > The 30s comes from apps or middlewares not from drivers. Ah OK, so it's probably the default value in ADO ? Anyway, it works with commandtimeout=0, and I suppose I should have defined that from the beginning. Regards -- Arnaud -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc