Re: WIP: new system catalog pg_wait_event - Mailing list pgsql-hackers

From Drouvot, Bertrand
Subject Re: WIP: new system catalog pg_wait_event
Date
Msg-id b21e5706-b6dd-42f1-a744-3afffe87c2c9@gmail.com
Whole thread Raw
In response to Re: WIP: new system catalog pg_wait_event  (Michael Paquier <michael@paquier.xyz>)
Responses Re: WIP: new system catalog pg_wait_event
List pgsql-hackers
Hi,

On 8/8/23 5:05 AM, Michael Paquier wrote:
> On Tue, Aug 08, 2023 at 11:53:32AM +0900, Kyotaro Horiguchi wrote:
>> As I mentioned in another thread, I'm uncertain about our stance on
>> the class id of the wait event. If a class acts as a namespace, we
>> should include it in the view. Otherwise, if the class id is just an
>> attribute of the wait event, we should make the event name unique.
> 
> Including the class name in the view makes the most sense to me, FWIW,
> as it could be also possible that one reuses an event name in the
> existing in-core list, but for extensions.  That's of course not
> something I would recommend.

Thanks Kyotaro-san and Michael for the feedback. I do agree and will
add the class name.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Fix badly generated entries in wait_event_names.txt
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: Synchronizing slots from primary to standby