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

From Tom Lane
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 7476.1234281293@sss.pgh.pa.us
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: PQinitSSL broken in some use casesf
Re: PQinitSSL broken in some use casesf
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
>> We could do that, I guess. However, if an application passes this in to
>> an old version of libpq, there is no way to know that it didn't know
>> about it.

> Well, you could create PQinitSSLExtended, but, as you say, the use
> case is pretty narrow...

> It would help if there were a PQgetLibraryVersion() function.

Help how?  There is nothing an app can do to work around the problem
AFAICS.  Or if there were, we should just document it and not change
the code --- the use case for this is evidently too narrow to justify
complicating libpq's API even more.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PQinitSSL broken in some use casesf
Next
From: Magnus Hagander
Date:
Subject: Re: PQinitSSL broken in some use casesf