Re: Postmaster self-deadlock due to PLT linkage resolution - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Postmaster self-deadlock due to PLT linkage resolution
Date
Msg-id CA+TgmoZRGNyeWd0g+ro+ucNKtsCVuQpRzforP5SSK5dSmB6P8w@mail.gmail.com
Whole thread Raw
In response to Re: Postmaster self-deadlock due to PLT linkage resolution  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Postmaster self-deadlock due to PLT linkage resolution
List pgsql-hackers
On Tue, Aug 30, 2022 at 8:17 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> FWIW I suspect FreeBSD can't break like this in a program linked with
> libthr, because it has a scheme for deferring signals while the
> runtime linker holds locks.  _rtld_bind calls _thr_rtld_rlock_acquire,
> which uses the THR_CRITICAL_ENTER mechanism to cause thr_sighandler to
> defer until release.  For a non-thread program, I'm not entirely sure,
> but I don't think the fork() problem exists there.  (Could be wrong,
> based on a quick look.)

Well that seems a bit ironic, considering that Tom has worried in the
past that linking with threading libraries would break stuff.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option
Next
From: Robert Haas
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option