Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Schreiber <daniel(dot)schreiber(at)hrz(dot)tu-chemnitz(dot)de>
Subject: Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times
Date: 2026-04-22 22:13:28
Message-ID: 1329124.1776896008@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> On Wed, Apr 22, 2026 at 12:23 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Should we write the arguments as BIO_TYPE_NONE | BIO_TYPE_SOURCE_SINK
>> rather than just BIO_TYPE_SOURCE_SINK?

> Good question... Popularity-wise, the shorter spelling shows up across
> quite a few projects on GitHub, but the only spelling of
> `BIO_meth_new(BIO_TYPE_NONE | ...)` that I can find is a single place
> inside OpenSSL's own test suite -- which also uses the shorter
> alternative, in two places. So my vote is BIO_TYPE_SOURCE_SINK; we'll
> be in good company.

Fair enough.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2026-04-23 00:55:10 Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
Previous Message Jacob Champion 2026-04-22 22:10:31 Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times

Browse pgsql-hackers by date

  From Date Subject
Next Message SATYANARAYANA NARLAPURAM 2026-04-22 22:20:36 Add null check on get_tablespace_name() return in pg_get_database_ddl_internal
Previous Message Jacob Champion 2026-04-22 22:10:31 Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times