MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Aug 2023 09:14:15 +0900
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>, Bharath Rupireddy
 <bharath.rupireddyforpostgres@gmail.com>, Tristan Partin
 <tristan@neon.tech>, pgsql-hackers@lists.postgresql.org
Subject: Re: Support to define custom wait events for extensions
In-Reply-To: <ZNnzUiB1KBZsUt+a@paquier.xyz>
References: <ZNLJwViP14/4zcBx@paquier.xyz>
 <20230809003710.qhys7nvwhdujd4pm@awork3.anarazel.de>
 <0850ea2f23217b3a87340dd2d721d051@oss.nttdata.com>
 <ZNQlJ8pQIIWjv/he@paquier.xyz>
 <53dc58793eb3df17d2da8c2fc2275fac@oss.nttdata.com>
 <ZNSh41m/w9NERlnC@paquier.xyz> <ZNlh9aeJe5KSJBNt@paquier.xyz>
 <b65a0ce07dd2c8a4f0edad04bf613d3b@oss.nttdata.com>
 <ZNnJmReugnGO3Sdd@paquier.xyz>
 <4f5e455cde9805dd81332d515376bc12@oss.nttdata.com>
 <ZNnzUiB1KBZsUt+a@paquier.xyz>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <dc1ad62d0b274063376b420e3bfe8cd0@oss.nttdata.com>
Archived-At: 
 <https://www.postgresql.org/message-id/dc1ad62d0b274063376b420e3bfe8cd0%40oss.nttdata.com>
Precedence: bulk

On 2023-08-14 18:26, Michael Paquier wrote:
> On Mon, Aug 14, 2023 at 05:55:42PM +0900, Masahiro Ikeda wrote:
>> I'm thinking a name like "contrib name + description summary" would
>> be nice. The "contrib name"  is namespace-like and the "description 
>> summary"
>> is the same as the name of the waiting event name in core. For 
>> example,
>> "DblinkConnect" for dblink. In the same as the core one, I thought the 
>> name
>> should be the camel case.
> 
> Or you could use something more in line with the other in-core wait
> events formatted as camel-case, like DblinkConnect, etc.
> 
>> BTW, is it better to discuss this in a new thread because other 
>> developers
>> might be interested in user-facing wait event names? I also would like 
>> to
>> add documentation on the wait events for each modules, as they are not 
>> mentioned
>> now.
> 
> Saying that, having some documentation on the page of each extension
> is mandatory once these can be customized, in my opinion.  All that
> should be discussed on a new, separate thread, to attract the correct
> audience.

OK. I'll make a new patch and start a new thread.

Regards,
-- 
Masahiro Ikeda
NTT DATA CORPORATION