| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, 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: | 2023-04-12 10:59:46 |
| Message-ID: | A09060B3-D85E-45BC-A91B-AC49924773CA@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 12 Sep 2022, at 15:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Personally I'd put this up front, more like
>
> have been initialized by your application, so that
> <application>libpq</application> will not also initialize those libraries.
> + However, this is unnecessary when using OpenSSL 1.1.0 or later,
> + as duplicate initializations are no longer problematic.
> </para>
>
> If you do use wording that specifically mentions PQinitOpenSSL,
> it should also mention PQinitSSL, just for clarity.
Reviving an old thread that got buried, I propose to apply the attached and
backpatch it as OpenSSL of such vintage is equally likely to be used in old
versions of postgres as current.
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| pqinitopenssl_v2.diff | application/octet-stream | 663 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-04-12 11:23:35 | Re: Support logical replication of DDLs |
| Previous Message | John Howroyd | 2023-04-12 10:50:21 | Re: Guidance on INSERT RETURNING order |