Re: Fix lwlock.c and wait_event_names.txt discrepancy
Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-18T13:40:55Z
Lists: pgsql-hackers
Hi, On Thu, Jul 17, 2025 at 02:25:46PM +0000, Bertrand Drouvot wrote: > Hi, > > On Thu, Jul 17, 2025 at 09:50:12AM +0900, Michael Paquier wrote: > > On Wed, Jul 16, 2025 at 11:41:09AM +0000, Bertrand Drouvot wrote: > > > > > As a way to prevent this to occur we might want to add extra input file(s) > > > parameter to generate-wait_event_types.pl (as proposed in [1]). > > > > > > [1]: https://www.postgresql.org/message-id/flat/aDQdDhcwMHjZRhSV%40ip-10-97-1-34.eu-west-3.compute.internal > > > > That's the second issue so far, so we had better do so. > > Yeah, I'll look at it. Done in [1]. [1]: https://www.postgresql.org/message-id/aHpOgwuFQfcFMZ/B%40ip-10-97-1-34.eu-west-3.compute.internal Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
Fix inconsistent LWLock tranche names for MultiXact*
- b3abec0adeb0 17.6 landed
- 4fcbe06aa8f8 18.0 landed
- a493e741d32b 19 (unreleased) landed
-
Improve performance of subsystems on top of SLRU
- 53c2a97a9266 17.0 cited