i have also tested several PGSQL ODBC driver versions with Windows 2000, IIS
(the Windows webserver) and ASP.
Version 18.104.22.168 runs best in a multithreaded environment, but it is still
not 100% stable.
The webserver sometimes hangs (depends on the load) so that the process
needs to be killed.
All in all, the Postgres ODBC driver does not fit our needs for stability,
and as the posts in this newsgroup show, there is no development going on.
To me, it looks like no one here uses the ODBC-driver for server
applications with windows.
Our conclusion is that Postgres is not usable with ODBC on windows, and no
stable driver will be available soon. We are going to switch a different
database. To bad, as the database itself runs fast and stable.
bye bye postgres !
> -----Ursprüngliche Nachricht-----
> Von: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]Im Auftrag von Gary Doades
> Gesendet: Montag, 8. November 2004 23:30
> An: pgsql-odbc(at)postgresql(dot)org
> Betreff: [ODBC] ODBC Driver stability
> Unfortunately I have to come to the conclusion that the latest ODBC
> driver (22.214.171.124) is not as stable as first thought. When I initially
> tested it I was using a single application with a few connections and it
> seemed OK (better than 126.96.36.199 anyway)
> Recently I have been doing heavier load testing within my ASP.NET
> application. Being a Web app on Windows it is inheriently multi-threaded
> and uses the MS .NET connect-execute-fetch-disconnect cycle heavily.
> After obtaining just 10 connections and executing SQL the app starts to
> report random database failure messages "No error" and null reference
> exceptions withing Syetem.Data are common.
> Various restarts, checking there are no other psqlodbc dlls and various
> test loads end up with the same situation fairly quickly.
> Switching back to the 188.8.131.52 ODBC driver and the app will run stable
> for hours (or for as long as the test runs) with no driver errors.
> I can now reproduce this problem in a single Windows GUI app by getting
> lots of connections and radpidly executing SQL immediately after opening
> each of the connections.
> Sadly being in the .NET environment I can't see how to debug the driver
> in these situations or how to get more information about the faults. It
> still looks like buffer overruns causing the main problems.
> I'm a bit concerned that Postgres is going to end up with a fantastic
> server (even on Windows!), but badly let down by the ODBC driver, which
> I suspect that a lot of the Windows newcomers will want to use. I know
> that 184.108.40.206 is stable at the moment, but what is the way forward?
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.789 / Virus Database: 534 - Release Date: 07.11.2004
In response to
pgsql-odbc by date
|Next:||From: Scot Loach||Date: 2004-11-10 16:57:03|
|Subject: Re: 08.00.0002 useless :-)|
|Previous:||From: David Bear||Date: 2004-11-10 06:21:17|
|Subject: import limited to 1000 tuples|