Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN

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: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN
Date: 2023-06-09 04:26:07
Message-ID: 351810d2-120b-9b90-a680-cce6ac1c0fa7@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 6/9/23 1:15 AM, Michael Paquier wrote:
> On Thu, Jun 08, 2023 at 10:57:55AM +0900, Masahiro Ikeda wrote:
>> (Excuse me for cutting in, and this is not directly related to the thread.)
>> +1. I'm interested in the feature.
>>
>> This is just a example and it probable be useful for other users. IMO, at
>> least, it's better to improve the specification that "Extension"
>> wait event type has only the "Extension" wait event.
>
> I hope that nobody would counter-argue you here. In my opinion, we
> should just introduce an API that allows extensions to retrieve wait
> event numbers that are allocated by the backend under
> PG_WAIT_EXTENSION, in a fashion similar to GetNamedLWLockTranche().
> Say something like:
> int GetExtensionWaitEvent(const char *wait_event_name);

+1, that's something I've in mind to work on once/if this patch is/get
committed.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-06-09 04:55:56 Re: Fix search_path for all maintenance commands
Previous Message Nathan Bossart 2023-06-09 04:24:22 Re: Typo in src/backend/access/nbtree/README?