| From: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Support to define custom wait events for extensions |
| Date: | 2023-06-15 13:21:50 |
| Message-ID: | d8c5435d-fde4-8ddb-3af0-88d25de00c97@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 6/15/23 10:00 AM, Michael Paquier wrote:
> On Thu, Jun 15, 2023 at 03:06:01PM +0900, Masahiro Ikeda wrote:
>> Currently, only one PG_WAIT_EXTENSION event can be used as a
>> wait event for extensions. Therefore, in environments with multiple
>> extensions are installed, it could take time to identify which
>> extension is the bottleneck.
>
> Thanks for taking the time to implement a patch to do that.
+1 thanks for it!
>
>> I want to know your feedbacks. Please feel free to comment.
>
> I think that's been cruelly missed.
Yeah, that would clearly help to diagnose which extension(s) is/are causing the waits (if any).
I did not look at the code yet (will do) but just wanted to chime in to support the idea.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2023-06-15 13:39:17 | Re: Avoid unncessary always true test (src/backend/storage/buffer/bufmgr.c) |
| Previous Message | Tom Lane | 2023-06-15 13:21:38 | Re: When IMMUTABLE is not. |