Re: pg_stat_get_backend_subxact() and backend IDs?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>
Subject: Re: pg_stat_get_backend_subxact() and backend IDs?
Date: 2023-08-29 23:22:27
Message-ID: ZO59s6in+aACdCGb@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 29, 2023 at 09:46:55AM -0700, Nathan Bossart wrote:
> This was my first reaction [0]. I was concerned about renaming the
> exported functions so close to release, so I was suggesting that we hold
> off on that part until v17. If there isn't a concern with renaming these
> functions in v16, I can proceed with something more like v2.

Thanks for the pointer. This version is much better IMO, because it
removes entirely the source of the confusion between the difference in
backend ID and index ID treatments when fetching the local entries in
the array. So I'm okay to rename these functions now, before .0 is
released to get things in a better shape while addressing the issue
reported.

+extern LocalPgBackendStatus *pgstat_get_local_beentry_by_index(int beid);

Still I would to a bit more of s/beid/id/ for cases where the code
refers to an index ID, and not a backend ID, especially for the
internal routines.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-08-30 00:10:47 Re: should frontend tools use syncfs() ?
Previous Message Peter Smith 2023-08-29 23:16:38 Fix shadow warnings in logical replication code