Re: WIP: new system catalog pg_wait_event
Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
From: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
To: Michael Paquier <michael@paquier.xyz>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Date: 2023-08-08T08:16:37Z
Lists: pgsql-hackers
Attachments
- v3-0001-pg_wait_event.patch (text/plain) patch v3-0001
Hi, On 8/8/23 7:37 AM, Drouvot, Bertrand wrote: > 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. > Please find attached v3 adding the wait event types. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
doc: Improve example query related to pg_wait_events
- befe9451fbf5 17.0 landed
-
Add system view pg_wait_events
- 1e68e43d3f0f 17.0 landed