Re: Show WAL write and fsync stats in pg_stat_io

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "bharath(dot)rupireddyforpostgres(at)gmail(dot)com" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Show WAL write and fsync stats in pg_stat_io
Date: 2025-02-07 00:47:53
Message-ID: Z6VYORRR7iCeYRbu@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 06, 2025 at 03:39:05PM +0300, Nazir Bilal Yavuz wrote:
> My vote goes to 029. It already has the '## check checkpoint and wal
> stats are incremented due to restart' part and what we are adding is
> similar to that.

Okay, sold, with a routine grabbing some stats from pg_stat_io based
on an object, a context and a backend type to match with the style of
the test. The stats are checked just after initialization, which
should be enough for our purpose.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-02-07 01:52:53 Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Previous Message Anton A. Melnikov 2025-02-07 00:15:17 FSM doesn't recover after zeroing damaged page.