| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: psqlODBC 09.05.0300 (x86) - problem with SQL_QUERY_TIMEOUT |
| Date: | 2016-07-07 01:51:36 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F5B2E59@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Jan-Peter Seifert
> it looks like SQL_QUERY_TIMEOUT is on by default - causing dead connections
> with long running statements:
>
> "SQLSTATE = 00000 Native Error = 26 Could not send Query(connection dead)"
No, SQL_QUERY_TIMEOUT is off by default.
I've just confirmed that "SET statement_timeout" is not issued when I executed "SELECT pg_sleep(60);" with isql command of the unixODBC. In addition, SQL_QUERY_TIMEOUT just terminates the query, retaining the database connection. Your message seems to show that the connection was terminated.
Could you show the mylog output?
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-07 06:58:59 | Re: Build broken with nmake since ea74e47 |
| Previous Message | Johnny Yan | 2016-07-06 21:20:06 | Re: Statically linking against libpq |