Re: perform_spin_delay() vs wait events - Mailing list pgsql-hackers

From Robert Haas
Subject Re: perform_spin_delay() vs wait events
Date
Msg-id CA+TgmoYNsNVcifkEEOGh4vyv0sm-6RBkGQ3Vn0ihpdqTNn2=mA@mail.gmail.com
Whole thread Raw
In response to Re: perform_spin_delay() vs wait events  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sun, Nov 20, 2022 at 6:10 PM Andres Freund <andres@anarazel.de> wrote:
> I was wondering about that too - but decided against it because it would only
> show a single wait event. And wouldn't really describe spinlocks as a whole,
> just the "extreme" delays. If we wanted to report the spin waits more
> granular, we'd presumably have to fit the wait events into the lwlock, buffers
> and some new category where we name individual spinlocks.
>
> But I guess a single spinlock wait event type with an ExponentialBackoff wait
> event or such wouldn't be too bad.

Oh, hmm. I guess it is actually bracketing a timed wait, now that I
look closer at what you did. So perhaps your first idea was best after
all.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Next
From: Robert Haas
Date:
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway