ODBC / startup and existing pidfile
| От | Hansjörg Herrbold |
|---|---|
| Тема | ODBC / startup and existing pidfile |
| Дата | |
| Msg-id | !~!AAAAAILqQKrupgFMmjjkKbfCwfHEVSAA@uumail.de обсуждение исходный текст |
| Список | 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
Вложения
В списке pgsql-bugs по дате отправления: