| From: | Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Support to define custom wait events for extensions |
| Date: | 2023-06-16 02:17:37 |
| Message-ID: | 478dcb9c6e76be3dc9cbadfaeb8247b8@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-06-15 22:21, Drouvot, Bertrand wrote:
> 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.
Great! Thanks.
Regards,
--
Masahiro Ikeda
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2023-06-16 02:22:31 | Re: Allow pg_archivecleanup to remove backup history files |
| Previous Message | Julien Rouhaud | 2023-06-16 02:17:00 | Re: [PATCH] Slight improvement of worker_spi.c example |