Bugs item #1000475, was opened at 2005-12-08 09:56
You can respond by visiting:
http://pgfoundry.org/tracker/?func=d...oup_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: SEGFAULT during SQLCancel

Initial Comment:
I've got seg.fault when I issued "cancel" from one thread for statement which was performing in another thread.
Primarily, it's because statement thread was started to fetch data when "cancel" was issued.
I'm using unixODBC 2.2.9, psqlodbc 08.01.0102 with "Threading=0, UseDeclareFetch=1" options. Also I'm using ODBC auto_commit mode.
MyLog file is attached.
P.S. What I think - it's because PGAPI_FreeStmt call (from PGAPI_Cancel function) doesn't block any mutex against Fetch functions. When I tried to create special mutex to protect PGAPI_Cancel->PGAPI_FreeStmt call against SQLFetchScroll, seg.fault disappeared.


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

>Comment By: Ludek Finstrle (luf)
Date: 2005-12-09 02:29

Message:
Feel free to attach patch which solve the problem. It could be good start point for us at least. You can post the patch to pgsql-odbc mailing list.

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

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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly