Re: PQinitSSL broken in some use casesf
| От | Tom Lane |
|---|---|
| Тема | Re: PQinitSSL broken in some use casesf |
| Дата | |
| Msg-id | 7476.1234281293@sss.pgh.pa.us обсуждение |
| Ответ на | Re: PQinitSSL broken in some use casesf (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: PQinitSSL broken in some use casesf
Re: PQinitSSL broken in some use casesf |
| Список | 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 по дате отправления: