Re: Generate pg_stat_get_* functions with Macros

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
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-07 00:16:14
Message-ID: Y4/bTjgdhZRQ3JaP@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 06, 2022 at 05:28:47AM +0100, Drouvot, Bertrand wrote:
> Fields renaming was mandatory in the previous ones as there was
> already a mix of with/without "n_" in the existing fields names.
>
> That said, I think it's better to rename the fields as you did (to
> be "consistent" on the naming between relation/db stats), so the
> patch LGTM.

Yeah, PgStat_StatDBEntry is the last one using this style, so I have
kept my change with the variables renamed rather than painting more
CppConcat()s. The functions are still named the same as the original
ones.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2022-12-07 00:33:38 Collation DDL inconsistencies
Previous Message Peter Smith 2022-12-06 23:45:52 Re: Force streaming every change in logical decoding