Re: Autogenerate some wait events code and documentation

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2023-07-14T04:49:22Z
Lists: pgsql-hackers

Attachments

On Thu, Jul 13, 2023 at 10:26:54AM +0900, Michael Paquier wrote:
> I would like to apply 0001 and 0002 to improve the format if there are
> no objections.  0003 and 0004 are still here for discussion, as it
> does not seem like a consensus has been reached for that yet.  Getting
> more opinions would be a good next step for the last two patches, I
> assume.

I have looked again at 0001 and 0002 and applied them to get them out
of the way.  0003 and 0004 are rebased and attached.  I'll add them to
the CF for later consideration.  More opinions are welcome.
--
Michael

Commits

  1. Add "ABI_compatibility" regions to wait_event_names.txt

  2. Remove column for wait event names in wait_event_names.txt

  3. Use more consistent names for wait event objects and types

  4. Add information about line contents on parsing failure of wait_event_names.txt

  5. Remove double quotes from the second column of wait_event_names.txt

  6. Generate automatically code and documentation related to wait events

  7. Refactor some code related to wait events "BufferPin" and "Extension"

  8. doc: Fix ordering of entries in wait event table for I/O type