From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: per backend WAL statistics |
Date: | 2025-01-10 09:40:38 |
Message-ID: | Z4DrFhdlO6Xf13Xd@ip-10-97-1-34.eu-west-3.compute.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Michael Paquier wrote:
> An extra thing I have finished by doing is removing
> PgStat_BackendPendingIO, then applied the change. It was useful when
> returned as a result of pgstat_prep_backend_pending(), but not so much
> with the new PgStat_BackendPending that includes all the pending stats
> data.
Yeah, makes sense, thanks!
Please find attached v4 taking into account 2c14037bb5.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Extract-logic-filling-pg_stat_get_wal-s-tuple-int.patch | text/x-diff | 3.9 KB |
v4-0002-per-backend-WAL-statistics.patch | text/x-diff | 22.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei Harikae (Fujitsu) | 2025-01-10 09:43:02 | RE: Windows meson build |
Previous Message | Antonin Houska | 2025-01-10 09:31:47 | Re: why there is not VACUUM FULL CONCURRENTLY? |