Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks - Mailing list pgsql-bugs

From Bertrand Drouvot
Subject Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks
Date
Msg-id Z01xhpTy5y6bxEpp@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-bugs
Hi,

On Thu, Nov 28, 2024 at 11:27:02AM +0000, Bertrand Drouvot wrote:
> So, it seems to me that the thing to do would be to remove the "Lock" suffix from 
> the LWLock wait event names.
> 

Proposed that way in [1].

[1]: https://www.postgresql.org/message-id/flat/Z01w1%2BLihtRiS0Te%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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18729: update with multiple subpartitions return error: too many range table entries
Next
From: "Euler Taveira"
Date:
Subject: Re: BUG #18729: update with multiple subpartitions return error: too many range table entries