| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Ants Aasma <ants(dot)aasma(at)cybertec(dot)at>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_stat_io_histogram |
| Date: | 2026-02-19 17:15:53 |
| Message-ID: | aZdFSSXaW6C3RJbJ@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, Feb 18, 2026 at 06:12:47PM -0500, Andres Freund wrote:
> Just rediscovered that the per-backend tracking patch added an external
> function call to pgstat_count_io_op_time(), pgstat_count_backend_io_op() and
> that a fair number of more recently added branches are constants at the
> callsite :(. Probably doesn't matter, but makes me sad nonetheless :)
Yeah, we have a dedicated thread to remove those [1].
Sorry that my message is not directly linked to $SUBJECT, but I was reading this
thread and saw Andres's message above that remind me of [1].
[1]: https://postgr.es/m/aNVWe2tR1jj5Tsct%40ip-10-97-1-34.eu-west-3.compute.internal
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-02-19 17:20:44 | assume availability of "inline" keyword |
| Previous Message | Ants Aasma | 2026-02-19 17:06:04 | Re: Hash aggregate collisions cause excessive spilling |