My personal opinion is that atm the libpq driver is already as good as or better than the pre-libpq driver. There may be a few as of yet undiscovered reliability issues or busted features, so there is some risk with the switchover. Since Dave fixed the excel bug, today I’m going to switch over my application stack to the new driver and give a more qualitative analysis.
Since the new driver is a much better design, (and supports the level 3 protocol!) it will only get better. I think that you can also give some really good feedback about utf-8 capabilities of the driver (expect some problems here). I hate to suggest new technology to bail you out of a nasty situation but ISTM this is the only situation with a high chance of long term success. The only other option I see is to build a stronger test suite and hang back for a bit and closely monitor progress.
How heavily have you load tested the new driver?
Merlin
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Joel Fradkin
Sent: Monday, July 25, 2005 4:01 PM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] WHat do people think about using in production?
We still are experiencing issues with SQLASCII and 7.4 ODBC, any feedback on the readiness of the libpq stuff?
I have not grabbed a current copy and built it since last Thursday, so not sure if any other changes are planned I should wait for, or even if you feel its ready or not for prime time yet.
I appreciate any feedback as I want to try the conversion again (the conversion went ok, but once in Unicode my app was having issues on the 8.0 pre libpq driver, and at that moment the libpq driver had memory leaks which I have verified seem to be fixed.)
Joel Fradkin
