Re: the s_lock_stuck on perform_spin_delay - Mailing list pgsql-hackers

From Robert Haas
Subject Re: the s_lock_stuck on perform_spin_delay
Date
Msg-id CA+Tgmoa6TfnnL-RiOeKfNYJZEtyUXj_=bZRrXe59iG8TDNccPA@mail.gmail.com
Whole thread Raw
In response to Re: the s_lock_stuck on perform_spin_delay  (Andres Freund <andres@anarazel.de>)
Responses Re: the s_lock_stuck on perform_spin_delay
List pgsql-hackers
On Fri, Jan 5, 2024 at 2:11 PM Andres Freund <andres@anarazel.de> wrote:
> I see it fairly regularly. Including finding several related bugs that lead to
> stuck systems last year (signal handlers are a menace).

In that case, I think this proposal is dead. I can't personally
testify to this code being a force for good, but it sounds like you
can. So be it!

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Fix bogus Asserts in calc_non_nestloop_required_outer
Next
From: Andres Freund
Date:
Subject: Re: the s_lock_stuck on perform_spin_delay