| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: lippq client library and openssl initialization: PQinitOpenSSL() |
| Date: | 2022-09-11 20:57:50 |
| Message-ID: | 9A09E47E-68EB-45DF-A934-FB76F2086D20@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 11 Sep 2022, at 17:08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> writes:
>> The PostgreSQL doc says that if the application code is initializing OpenSSL, it should tell PostgreSQL libpq client library that OpenSSL initialization is already done:
>> https://www.postgresql.org/docs/14/libpq-ssl.html#LIBPQ-SSL-INITIALIZE
>> I was wondering if this is still true with OpenSSL 1.1.0+
>
> Don't believe so. The HAVE_CRYPTO_LOCK stuff is all obsolete and
> not compiled if you built against 1.1.0. The only thing left that
> will happen if you don't call PQinitOpenSSL is an extra call to
> OPENSSL_init_ssl, which should be harmless as far as I can see
> from the OpenSSL docs.
To the best of my knowledge, thats entirely correct.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-11 21:35:04 | Re: lippq client library and openssl initialization: PQinitOpenSSL() |
| Previous Message | David G. Johnston | 2022-09-11 16:03:23 | Re: how to check specific user_name have “SELECT ON ALL TABLES IN SCHEMA <tableschema>” privilege or not ? |