Re: Generate pg_stat_get_* functions with Macros

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Generate pg_stat_get_* functions with Macros
Date: 2022-12-05 08:11:43
Message-ID: 292fc2a0-189f-c44e-1da6-6b4d71effdc2@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 12/5/22 8:44 AM, Michael Paquier wrote:
> On Mon, Dec 05, 2022 at 08:27:15AM +0100, Drouvot, Bertrand wrote:
>> On 12/4/22 6:32 PM, Nathan Bossart wrote:
>>> Alright. I marked this as ready-for-committer.
>>
>> Thanks!
>
> Well, that's kind of nice:
> 5 files changed, 139 insertions(+), 396 deletions(-)
> And I like removing code, so..
>

Thanks for looking at it!

> In the same area, I am counting a total of 21 (?) pgstat routines for
> databases that rely on pgstat_fetch_stat_dbentry() while returning an
> int64. This would lead to more cleanup.
> --

Yeah, good point, thanks!

I'll look at the "databases" ones but I think in a separate patch. The reason is that the current one is preparatory work for [1].
Means, once the current patch is committed, working on [1] and "cleaning" the databases one could be done in parallel. Sounds good to you?

[1]: https://commitfest.postgresql.org/41/3984/

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 Dmitry Koval 2022-12-05 08:11:51 Re: Operation log for major operations
Previous Message Peter Eisentraut 2022-12-05 08:04:58 Re: pg_dump: Remove "blob" terminology