Re: PQinitSSL broken in some use casesf
От | Tom Lane |
---|---|
Тема | Re: PQinitSSL broken in some use casesf |
Дата | |
Msg-id | 7782.1234282482@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 Re: PQinitSSL broken in some use casesf |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: >>> 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. > It would let you assert that you were running against a version of > libpq that has the functionality that you are attempting to use, thus > eliminating the risk of silent failure. If that's all you want, then PQinitSSLExtended is a perfectly good answer. Your app will fail to link if you try to use a library version that hasn't got it. I think documenting the workaround is a sufficient answer though. regards, tom lane
В списке pgsql-hackers по дате отправления: