Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl
Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2025-05-26T07:49:34Z
Lists: pgsql-hackers
Attachments
Hi hackers, c325a7633fcb forgot to add AioUringCompletion in wait_event_names.txt: please find attached v1-0001 fixing it (please double check the wait event description as I'm not that familiar with io_uring). 042a66291 also missed it for LWTRANCHE_MEMORY_CONTEXT_REPORTING_PROC and LWTRANCHE_MEMORY_CONTEXT_REPORTING_STATE. 042a66291 has been reverted in fb844b9f065 though so there is no need to fix those. That makes me think that it is easy to miss adding a new LWLock in wait_event_names.txt and generate-wait_event_types.pl does not detect that. So, adding validate_lwlock_count() in generate-wait_event_types.pl (in v1-0002) to ensure that the number of LWLocks description generated in the documentation match the ones defined in lwlock.h and lwlocklist.h. Looking forward to your feedback, Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
Add AioUringCompletion in wait_event_names.txt
- c3623703f363 18.0 landed