From: | Hansjörg Herrbold <hjh(at)uumail(dot)de> |
---|---|
To: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | ODBC / startup and existing pidfile |
Date: | 2005-01-06 08:23:24 |
Message-ID: | !~!AAAAAILqQKrupgFMmjjkKbfCwfHEVSAA@uumail.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello,
we a working with libodbc++ (http://libodbcxx.sourceforge.net/)
We have tested our software on Windows XP together witch Postgres 8.0 RC1
(installed with pginstaller)
Unfortunately an every SELECT only invalid data is retreived from the
database (e.g. a VARCHAR row) with libodbc++ and the 8.0 ODBC driver
After we have replaced the psqlODBC with version psqlodbc-07_03_0200
everything works perfectly.
If we query the database using MS Access together with the 8.0 ODBC driver
we get the correct results.
What has changed in the ODBC driver resulting in this incompatibility with
libodbc++?
I have not verified in newer versions the following problem:
After simulating a power failure on the PostgreSQL Server on Windows XP the
database is not started on next restart
because of the pidfile now already existing. This happens in the case that
another process (not a postgres database server)
exists with the pid stored in the pidfile. Is it possible to check if the
pidfile id owned by a database process or any other
system process and in this case to remove the stale pidfile?
Best regards
And many thanks for this great database system
Hansjörg Herrbold
Attachment | Content-Type | Size |
---|---|---|
winmail.dat | application/ms-tnef | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2005-01-06 09:44:02 | Re: File Groups with postgresql |
Previous Message | Oliver Jowett | 2005-01-05 23:02:58 | Re: [pgsql-hackers-win32] More SSL questions.. |