Markus Donath wrote:
> i have also tested several PGSQL ODBC driver versions with Windows 2000, IIS
> (the Windows webserver) and ASP.
> Version 188.8.131.52 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 !
I have to admit that I have not had any problems with 184.108.40.206 and I have
hit it pretty hard. In real-load tests with around 100 concurrent
connections from an ASP.NET server ticking over at around 12 connections
per second on average, ODBC pooling on, with a good mix of
selects/update/inserts it has not hung at all.
How do you know that it is the ODBC driver itself that is hanging the
In response to
pgsql-odbc by date
|Next:||From: Jeff Eckermann||Date: 2004-11-10 19:15:58|
|Subject: Re: Can't use current_timestamp or currval functions|
|Previous:||From: Peter Eisentraut||Date: 2004-11-10 18:17:59|
|Subject: Re: @@IDENTITY|