From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Removing support for v1 and v2 protocols? |
Date: | 2014-06-19 09:14:23 |
Message-ID: | 53A2A9EF.6010209@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 06/19/2014 05:52 AM, Craig Ringer wrote:
> Hi
>
> I've just found a bug (followup mail to come) that seems to be tied up
> in support for the old v1/v2 protocols.
>
> Is there any reason to keep all that cruft? v3 was introduced in 7.4, in
> 2003-11-17 .
No reason. Michael Paquier has been working on removing it, see thread
"Removing support for < 7.4 servers":
> Also, I'm wondering why psqlODBC does so much of its own protocol
> handling. It links to libpq, why doesn't it use it? There's a lot of
> complicated code in there - see, e.g. CC_send_query_append, that seems
> to duplicate much of what libpq its self does, and mix protocol handling
> up with client driver logic.
Yeah. Historical reasons, I'd say. I'd like to refactor the driver to
stop doing that, and use libpq. It's not an easy task, exactly because
the current code is quite complicated.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-06-19 10:32:45 | Re: Protocol de-synchronisation bug, bogus query sent |
Previous Message | Heikki Linnakangas | 2014-06-19 09:06:18 | Re: Building psqlODBC installers |