Bugs item #1000714, was opened at 2006-08-24 15:40
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000714&group_id=1000125
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Farid Zidan (faridz)
Assigned to: Nobody (None)
Summary: Driver gets progressively slower Multi-threading retrieval
Initial Comment:
4 or more threads active on the same connection doing sequential data retrieval over data of 300 tables. Some tables
have200k rows. Driver gets progressively slower retrieving large table data until and it appears to go into an infinite
loopusing 100% cpu and not doing any useful work.
Not able to isolate this issue. But you can reproduce it using CompareData application www.zidsoft.com
Required: one or two databases with over 300 tables with at least 6-8 tables with 200k or more rows.
Add a DBMS comparison for the two datasources in CompareData. Open a Compare Data tab to compare all the data of the
twodatasources tables and set the max thread count to 6 or 8 threads and then start the comparison. The first few
tablesdata are compared quickly but as the application progesses through the tables and encounters tables with large
numberof rows, the driver slows down more and more.
If you set the max thread count to 1, then the driver appears to works fine.
This issue does not happen with other DBMS drivers and appear specific to the PostgreSQL ODBC driver. I am using the
latestversion of the driver psqlodbc35w.dll dated 8/24/06 2:33pm ( an 8.02 bug fix by Hiroshi Inoue ).
Please let me know if you need any help reproducing this issue.
----------------------------------------------------------------------
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000714&group_id=1000125
From: Date: Subject:
[ psqlodbc-Bugs-1000417 ] odbc_lib_connect() returns "Specified driver could not be loaded due to system error 182 (PostgreSQL ANSI)"
