| From: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Orphaned wait event |
| Date: | 2023-03-24 06:23:20 |
| Message-ID: | 2b60c993-706c-f6a1-029d-341a7055aa66@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 3/23/23 11:00 PM, Thomas Munro wrote:
> I think if we want proper automation here we
> should look into a way to define wait events in a central file similar
> to what we do for src/backend/storage/lmgr/lwlocknames.txt. It could
> give the enum name, the display name, and the documentation sentence
> on one tab-separated line, and we could generate all the rest from
> that, or something like that? I suspect that downstream/monitoring
> tools might appreciate the existence of such a file too.
Yeah, I think that makes sense. I'll look at this and start a new
thread once I've a patch to share. FWIW, I'm also working on wait event "improvements"
(mainly adding extra info per wait event) that 1) I'll share once ready 2) could also probably
benefit from your proposal here.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2023-03-24 06:30:13 | Re: Orphaned wait event |
| Previous Message | Amit Kapila | 2023-03-24 06:16:53 | Re: Data is copied twice when specifying both child and parent table in publication |