| From: | "Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)de> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | "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-08 13:34:24 |
| Message-ID: | trinity-288aaeed-cf4e-4956-a682-b98230657583-1467984864580@3capp-gmx-bs29 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hello Tsunakawa-san,
thank you very much for your reply!
> No, SQL_QUERY_TIMEOUT is off by default.
How would you set it then - via connect settings?
> 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.
You are right. It seems that there was a network problem when I tried the update before. It completed using v9.5.300 without problems.
> Could you show the mylog output?
I have the mylog output. However, there was another problem. When using 9.5.300 all the the check boxes for the logs were disabled (greyed out) - even when creating a new ODBC DSN. When using 9.3.400 everything is okay.
Best regards,
Peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | NILTON OLIV | 2016-07-09 12:54:15 | Help me please - psqlODBC _09_05_0300-x64 |
| Previous Message | Michael Paquier | 2016-07-07 06:58:59 | Re: Build broken with nmake since ea74e47 |