Request a Demo
Home   >   mailing lists

Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times
Date
Msg-id 1329124.1776896008@sss.pgh.pa.us
Whole thread
In response to Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
Tree view 
Jacob Champion <jacob.champion@enterprisedb.com> writes:
> On Wed, Apr 22, 2026 at 12:23 PM Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times
Next
From: SATYANARAYANA NARLAPURAM
Date:
Subject: Add null check on get_tablespace_name() return in pg_get_database_ddl_internal