| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: per backend I/O statistics |
| Date: | 2025-01-03 10:48:41 |
| Message-ID: | Z3fAiV3KRzr7Z5le@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Tue, Dec 24, 2024 at 02:35:16PM +0900, Michael Paquier wrote:
> On Fri, Dec 20, 2024 at 09:57:19AM +0000, Bertrand Drouvot wrote:
> > BTW, now that the per backend I/O statistics is done, I'll start working on per
> > backend wal statistics.
>
> I think that this is a good idea.
Thanks for sharing your thoughts.
> It does not actually overlap the
> proposal in [1] as the stats persistency is not the same. What this
> thread has taught me is that you could just plug in the stats of the
> new backend-level structure a PgStat_WalStats and retrieve them with a
> new function that returns a single tuple with the WAL stats
> attributes. That should be rather straight-forward to achieve.
I started to look at it and should be able to share a patch next week.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-01-03 11:00:41 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | Amit Kapila | 2025-01-03 10:47:57 | Re: Conflict detection for update_deleted in logical replication |