MIME-Version: 1.0
References: <f7fe39b3-7e99-4939-8852-07350549161d@hrz.tu-chemnitz.de>
 <CAOYmi+=e9bQQa1jgLqZ18m5w-7KA44VeL9FON6i2gd8bi=d5Jw@mail.gmail.com>
 <CAOYmi+kac3wEE3iqxHfHCNd_n2i-Or=n+Qk8_G24UZn2uz3DyQ@mail.gmail.com> <aekf4cx42tNs6C0j@ubby>
In-Reply-To: <aekf4cx42tNs6C0j@ubby>
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Wed, 22 Apr 2026 15:10:07 -0700
Message-ID: <CAOYmi+nJ19kj4bnyyX66VpvTPhjaGVWGvPsyVQdnV=R6aLGo0A@mail.gmail.com>
Subject: Re: PostgreSQL 17: Bug in libpq when libpq is dlopened/closed
 multiple times
To: Nico Williams <nico@cryptonector.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, 
	Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAOYmi%2BnJ19kj4bnyyX66VpvTPhjaGVWGvPsyVQdnV%3DR6aLGo0A%40mail.gmail.com>
Precedence: bulk

On Wed, Apr 22, 2026 at 12:22=E2=80=AFPM Nico Williams <nico@cryptonector.c=
om> wrote:
> Leaking a dl handle is a way to prevent unloading.  Not saying that's a
> great answer, just that it's a workaround.

Hmm, I did that for our handle to libpq-oauth, but I imagine that
leaking a handle to _ourselves_ may make someone very unhappy with us
at some point? Plus, it might kick off the tiniest, most pointless
arms race:

    // why does libpq do this
    dlclose(libpq_handle);
    dlclose(libpq_handle);

I guess we could play around with RTLD_NODELETE... Something to keep
in the back pocket, maybe?

--Jacob