Re: Track IO times in pg_stat_io - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Track IO times in pg_stat_io
Date
Msg-id ZtXTEP9ZQkbgo8T5@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Track IO times in pg_stat_io  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
Hi,

On Fri, Aug 23, 2024 at 07:32:16AM +0000, Bertrand Drouvot wrote:
> Hi,
> 
> On Wed, Mar 08, 2023 at 04:34:38PM -0800, Andres Freund wrote:
> > On 2023-03-08 12:55:34 +0100, Drouvot, Bertrand wrote:
> > > - pg_stat_io is "global" across all sessions. So, even if one session is doing some "testing" and needs to turn
track_io_timingon, then it
 
> > > is even not sure it's only reflecting its own testing (as other sessions may have turned it on too).
> > 
> > I think for 17 we should provide access to per-existing-connection pg_stat_io
> > stats, and also provide a database aggregated version. Neither should be
> > particularly hard.
> 
> FWIW, I think that would be great and plan to have a look at this (unless someone
> beats me to it).

FWIW, here is the patch proposal for per backend I/O statistics [1].

[1]: https://www.postgresql.org/message-id/ZtXR%2BCtkEVVE/LHF%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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Flush pgstats file during checkpoints
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: PG_TEST_EXTRA and meson