Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: christophe(dot)courtois(at)dalibo(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, alvherre(at)alvh(dot)no-ip(dot)org
Subject: Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks
Date: 2024-12-02 08:36:22
Message-ID: Z01xhpTy5y6bxEpp@ip-10-97-1-34.eu-west-3.compute.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2024-12-02 15:37:59 Re: BUG #18729: update with multiple subpartitions return error: too many range table entries
Previous Message 飞鱼 2024-12-02 07:10:09 回复：BUG #18729: update with multiple subpartitions return error: too many range table entries