| From: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WIP: new system catalog pg_wait_event |
| Date: | 2023-08-07 08:23:27 |
| Message-ID: | 0109438a-9672-322b-7638-04ad47c97d0f@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 8/4/23 5:08 PM, Tom Lane wrote:
> "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> writes:
>> Now that fa88928470 generates automatically code and documentation
>> related to wait events, why not exposing the wait events description
>> through a system catalog relation?
>
> I think you'd be better off making this a view over a set-returning
> function. The nearby work to allow run-time extensibility of the
> set of wait events is not going to be happy with a static catalog.
Oh right, good point, thanks!: I'll come back with a new patch version to make
use of SRF instead.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2023-08-07 08:31:50 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |
| Previous Message | Drouvot, Bertrand | 2023-08-07 08:21:50 | Re: "duplicated" wait events |