Re: perform_spin_delay() vs wait events

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: perform_spin_delay() vs wait events
Date: 2022-11-22 03:51:25
Message-ID: Y3xHPcgOOC9PnSE0@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 21, 2022 at 07:01:18PM -0800, Andres Freund wrote:
> I plan to push this soon unless somebody has further comments.

> @@ -146,7 +146,8 @@ typedef enum
> WAIT_EVENT_RECOVERY_RETRIEVE_RETRY_INTERVAL,
> WAIT_EVENT_REGISTER_SYNC_REQUEST,
> WAIT_EVENT_VACUUM_DELAY,
> - WAIT_EVENT_VACUUM_TRUNCATE
> + WAIT_EVENT_VACUUM_TRUNCATE,
> + WAIT_EVENT_SPIN_DELAY
> } WaitEventTimeout;

That would be fine for stable branches, but could you keep that in an
alphabetical order on HEAD?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-11-22 04:17:08 Re: perform_spin_delay() vs wait events
Previous Message Bharath Rupireddy 2022-11-22 03:16:22 Re: ps command does not show walsender's connected db