Re: Checkpointer sync queue fills up / loops around pg_usleep() are bad - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Checkpointer sync queue fills up / loops around pg_usleep() are bad
Date
Msg-id YhtAFcgIxe/OL3qF@paquier.xyz
Whole thread Raw
In response to Checkpointer sync queue fills up / loops around pg_usleep() are bad  (Andres Freund <andres@anarazel.de>)
Responses Re: Checkpointer sync queue fills up / loops around pg_usleep() are bad  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On Sat, Feb 26, 2022 at 01:39:42PM -0800, Andres Freund wrote:
> I suspect the easiest is to just convert that usleep to a WaitLatch(). That'd
> require adding a new enum value to WaitEventTimeout in 14. Which probably is
> fine?

We've added wait events in back-branches in the past, so this does not
strike me as a problem as long as you add the new entry at the end of
the enum, while keeping things ordered on HEAD.  In recent memory, I
think that only some of the extensions published by PostgresPro rely
on the enums in this area.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Commitfest manager for 2022-03
Next
From: Julien Rouhaud
Date:
Subject: Re: Checkpointer sync queue fills up / loops around pg_usleep() are bad