Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN
| От | Drouvot, Bertrand |
|---|---|
| Тема | Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN |
| Дата | |
| Msg-id | 351810d2-120b-9b90-a680-cce6ac1c0fa7@gmail.com обсуждение исходный текст |
| Ответ на | Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN
|
| Список | 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
В списке pgsql-hackers по дате отправления: