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 1309665.1776885833@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>)
Responses Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times
List pgsql-hackers
Jacob Champion <jacob.champion@enterprisedb.com> writes:
> If anyone has thoughts on that, I'd love to hear them. I don't mind
> removing this unnecessary code in HEAD, or even backpatching as a
> courtesy -- but if it were up to me, I would not guarantee zero global
> resource leaks across libpq and its entire dependency graph.

I agree that we have no real ability to guarantee that.
Still, as far as the presented patch goes, it seems like a clear
win so I'd vote for fix-and-backpatch.

Should we write the arguments as BIO_TYPE_NONE | BIO_TYPE_SOURCE_SINK
rather than just BIO_TYPE_SOURCE_SINK?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nico Williams
Date:
Subject: Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed multiple times
Next
From: Bharath Rupireddy
Date:
Subject: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE