From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Noah Misch <noah@leadboat.com>, Michael Paquier <michael@paquier.xyz>,
        Jacob Champion <pchampion@vmware.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
        Daniel Gustafsson <daniel@yesql.se>, info@cspug.cz
Subject: Re: Preventing abort() and exit() calls in libpq
In-reply-to: <202107021459.7c2dkzyg5lua@alvherre.pgsql>
References: <202107021459.7c2dkzyg5lua@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Fri, 02 Jul 2021 10:59:33 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <819501.1625239217.1@sss.pgh.pa.us>
Date: Fri, 02 Jul 2021 11:20:17 -0400
Message-ID: <819502.1625239217@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/819502.1625239217%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Now it's hoverfly:
> ! nm -A -u libpq.so.5 2>/dev/null | grep -v __cxa_atexit | grep exit
> libpq.so.5: atexit               U           -
> libpq.so.5: pthread_exit         U           -

Ugh.  What in the world is producing those references?

(As I mentioned upthread, I'm quite suspicious of libpq trying to
perform any actions in an atexit callback, because of the uncertainty
about whether some later atexit callback could try to use libpq
functions.  So this seems like it might be an actual bug.)

			regards, tom lane