From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <greg(dot)maples(at)linkify(dot)com> |
Cc: | <jeff_eckermann(at)yahoo(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: ODBC driver crashing both Enterprise manager and pgAdminII? |
Date: | 2003-05-17 16:00:02 |
Message-ID: | 50109.80.177.99.193.1053187202.squirrel@ssl.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
It's rumoured that Greg Maples once said:
> My best guess is that the odbc driver code expects some level of
> Reliability in the connection and the port is either jabbering or
> Colliding. Not much else would make sense.
There is a known bug in the driver that causes exactly the symptoms you
describe in pgAdmin and would probably affect DTS as well. In a nutshell,
recent versions of Redhat Linux have an extemely long compiler version
string that consequently make the PostgreSQL version string very long. In
ealier versions of psqlODBC, this would cause a crash at logon when the
database version was requested using the SQLInfo function because a
temporary buffer created to store the data would overflow.
Did you try the updated driver yet that was suggested?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-05-18 21:23:41 | psqlODBC 07.03.0100 Released |
Previous Message | Dave Page | 2003-05-16 23:02:07 | Re: ODBC driver crashing both Enterprise manager and pgAdminII? |