Postgres Pro
Downloads
Home   >   mailing lists

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+TgmoaVPzXB-azTM1_g+e=QDN0Uu0vSGUQsXxRfL7ZwnQX=wA@mail.gmail.com
Whole thread Raw
In response to Re: the s_lock_stuck on perform_spin_delay  (Andy Fan <zhihuifan1213@163.com>)
Responses Re: the s_lock_stuck on perform_spin_delay
List pgsql-hackers
Tree view 
On Mon, Jan 22, 2024 at 11:58 AM Andy Fan <zhihuifan1213@163.com> wrote:
> I get your point! Acquiring an already held spinlock in quickdie is
> unlikely to happen, but since our existing infrastructure can handle it,
> then there is no reason to bypass it.

No, the existing infrastructure cannot handle that at all.

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

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: XLog size reductions: smaller XLRec block header for PG17
Next
From: Tom Lane
Date:
Subject: Re: Improving EXPLAIN's display of SubPlan nodes