MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jun 2023 11:17:37 +0900
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
To: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
 pgsql-hackers@lists.postgresql.org
Subject: Re: Support to define custom wait events for extensions
In-Reply-To: <d8c5435d-fde4-8ddb-3af0-88d25de00c97@gmail.com>
References: <b9f5411acda0cf15c8fbb767702ff43e@oss.nttdata.com>
 <ZIrFEo5qLcNAGjTs@paquier.xyz>
 <d8c5435d-fde4-8ddb-3af0-88d25de00c97@gmail.com>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <478dcb9c6e76be3dc9cbadfaeb8247b8@oss.nttdata.com>
Archived-At: 
 <https://www.postgresql.org/message-id/478dcb9c6e76be3dc9cbadfaeb8247b8%40oss.nttdata.com>
Precedence: bulk

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