Re: PQinitSSL broken in some use casesf - Mailing list pgsql-hackers

From Dave Page
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 937d27e10902100903u2ea7fbe6if992cfa54aa24a78@mail.gmail.com
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: PQinitSSL broken in some use casesf  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Tue, Feb 10, 2009 at 4:57 PM, Merlin Moncure <mmoncure@gmail.com> wrote:

> PQinitSSL is *broken*.  It's always been broken.  Since it already
> takes a parameter, I say add a special switch...the backwards
> compatibility danger doesn't seem too bad.

Add a switch to what? I get very nervous for our Windows users when
people start talking about changing the libpq API (for those that
don't know, Windows doesn't have DLL versioning like Unix - so any
non-backwards compatible API change really needs a corresponding
filename change to avoid pain and suffering).


-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: PQinitSSL broken in some use casesf
Next
From: Andrew Chernow
Date:
Subject: Re: PQinitSSL broken in some use casesf