| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, robertmhaas(at)gmail(dot)com |
| Subject: | Re: pg_stat_get_backend_subxact() and backend IDs? |
| Date: | 2023-08-25 15:32:51 |
| Message-ID: | 20230825153251.GA1593219@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 25, 2023 at 09:36:18AM +0900, Ian Lawrence Barwick wrote:
> Thanks for looking at this. In summary we now have these functions:
>
> extern PgBackendStatus *pgstat_get_beentry_by_backend_id(BackendId beid);
> extern LocalPgBackendStatus
> *pgstat_get_local_beentry_by_backend_id(BackendId beid);
> extern LocalPgBackendStatus *pgstat_get_local_beentry_by_index(int beid);
>
> which LGTM; patches work as expected and resolve the reported issue.
On second thought, renaming these exported functions so close to release is
probably not a great idea. I should probably skip back-patching that one.
Or I could have the existing functions call the new ones in v16 for
backward compatibility...
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-08-25 15:36:21 | Re: pg_stat_get_backend_subxact() and backend IDs? |
| Previous Message | Imseih (AWS), Sami | 2023-08-25 15:01:40 | Re: pg_stat_get_backend_subxact() and backend IDs? |