Re: Autogenerate some wait events code and documentation

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Autogenerate some wait events code and documentation
Date: 2024-03-18 23:39:11
Message-ID: ZfjQn5w5IMtw88n_@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 18, 2024 at 08:49:34AM -0700, Noah Misch wrote:
> On Mon, Mar 18, 2024 at 09:04:44AM +0000, Bertrand Drouvot wrote:
>> +# Ensure that the wait events under the "Backpatch" delimiter are placed in the
>> +# same order as in the pre 17 wait_event_types.h (see VERSION_FILE_SYNC as an
>> +# example).
>
> I expect the normal practice will be to put the entry in its natural position
> in git master, then put it in the backpatch section for any other branch. In
> other words, the backpatch regions are always empty in git master, and the
> non-backpatch regions change in master only.

Yes, I'd expect the same experience. And it is very important to
document that properly in the txt file. I don't see a need to specify
any version numbers as well, that's less burden when bumping the major
version number on the master branch every year.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2024-03-18 23:58:11 Re: Improving EXPLAIN's display of SubPlan nodes
Previous Message Greg Sabino Mullane 2024-03-18 23:38:07 Re: Possibility to disable `ALTER SYSTEM`