Feedback
Did this article resolve your question/issue?

   

Article

ODBC driver hang after Postgres DB timeout

Information

 
TitleODBC driver hang after Postgres DB timeout
URL NameODBC-driver-hang-after-Postgres-DB-timeout
Article Number000185471
EnvironmentProduct: Connect(64) for ODBC PostgreSQL Wire Protocol driver
Version: 07.16.0238
OS: Linux 32-bit
Database: PostgreSQL
Application: Test application
Question/Problem Description
After setting a PostgreSQL database timeout to cancel a long query, then running the long query so the timeout occurs, preparing a second statement hangs.  A large file remains in /tmp.
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC PostgreSQL Wire Protocol driver][PostgreSQL]ERROR: current transaction is aborted, commands ignored until end of transaction block(File postgres.c; Line 1231; Routine exec_parse_message; )
Defect NumberDefect 41686
Enhancement Number
Cause
The driver was not processing the error scenario properly.
Resolution
Fixed in hot fix 07.16.0250.
Refer to article Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/20/2020 7:22 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.