Re: Postmaster self-deadlock due to PLT linkage resolution

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Postmaster self-deadlock due to PLT linkage resolution
Date: 2022-08-30 12:26:27
Message-ID: CA+TgmoZRGNyeWd0g+ro+ucNKtsCVuQpRzforP5SSK5dSmB6P8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 30, 2022 at 8:17 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-08-30 12:33:46 Re: replacing role-level NOINHERIT with a grant-level option
Previous Message Robert Haas 2022-08-30 12:24:41 Re: replacing role-level NOINHERIT with a grant-level option