Bugs item #1000457, was opened at 2005-11-30 15:36
You can respond by visiting:
http://pgfoundry.org/tracker/?func=d...oup_id=1000125

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Nobody (None)
Assigned to: Ludek Finstrle (luf)
Summary: Autocommit and Cancel

Initial Comment:
Our application in one thread issued long time SELECT, another thread cancelled this statement. After that first thread tried to issue next SELECT and got error message because current transaction is aborted with error. As I saw in postgresql server logs there was no ROLLBACK statement issued by driver after cancellation.

We're using autocommit mode. Mylog file is attached.
Server version is 7.4.6, psqlodbc version is 08.01.0101.
Also, we use unixODBC 2.2.8 with option "Threading=0" in odbcinst.ini.

Thank you.

----------------------------------------------------------------------

>Comment By: Ludek Finstrle (luf)
Date: 2005-12-07 12:14

Message:
I try to fix this problem. Please try one of attached drivers. Send me feedback throught pgsql-odbc mailing list with attached mylog and with yours odbc.ini settings for used datasource (I think you have to use usedeclarefetch option).

I see no mylog attached (as you wrote you attach one).

----------------------------------------------------------------------

Comment By: Ludek Finstrle (luf)
Date: 2005-12-06 11:14

Message:
There is problem that exec is blocking and cancel is for non-blocking operations.
I'll fix it as soon as possible.

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=d...oup_id=1000125

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings