Re: verify predefined LWLocks have entries in wait_event_names.txt
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Michael Paquier <michael@paquier.xyz>
Date: 2024-01-05T17:46:20Z
Lists: pgsql-hackers
Attachments
On Fri, Jan 05, 2024 at 10:42:03AM -0600, Nathan Bossart wrote: > On Fri, Jan 05, 2024 at 07:39:39AM +0000, Bertrand Drouvot wrote: >> + die "lists of predefined LWLocks in lwlocknames.txt and wait_event_names.txt do not match" >> + unless $wait_event_lwlocks[$i] eq $lockname; >> >> What about printing $wait_event_lwlocks[$i] and $lockname in the error message? >> Something like? >> >> " >> die "lists of predefined LWLocks in lwlocknames.txt and wait_event_names.txt do not match (comparing $lockname and $wait_event_lwlocks[$i])" >> unless $wait_event_lwlocks[$i] eq $lockname; >> " >> >> I think that would give more clues for debugging purpose. > > Sure, I'll add something like that. I think this particular scenario is > less likely, but that's not a reason to make the error message hard to > decipher. Here is a new version of the patch with this change. I also tried to make the verification logic less fragile. Instead of depending on the exact location of empty lines in wait_event_names.txt, v3 adds a marker comment below the list that clearly indicates it should not be changed. This simplifies the verification code a bit, too. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
Cross-check lists of predefined LWLocks.
- 5b1b9bce8449 17.0 landed
-
Remove Lock suffix from WALSummarizerLock in wait_event_names.txt
- 371b07e89449 17.0 landed
-
Drop the redundant "Lock" suffix from LWLock wait event names.
- 14a910109126 13.0 cited