Re: Inconsistency in reporting checkpointer stats
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: nitinjadhavpostgres@gmail.com, pgsql-hackers@postgresql.org
Date: 2022-12-19T12:35:38Z
Lists: pgsql-hackers
On Fri, Dec 16, 2022 at 2:14 PM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > > In the first place I don't like that we count the same things twice. > Couldn't we count the number only by any one of them? > > If we remove CheckPointerStats.ckpt_bufs_written, CreateCheckPoint can > get the final number as the difference between the start-end values of > *the shared stats*. As long as a checkpoint runs on a single process, > trace info in BufferSync will work fine. Assuming single process > checkpointing there must be no problem to do that. (Anyway the current > shared stats update for checkpointer is assuming single-process). What if someone resets checkpointer shared stats with pg_stat_reset_shared()? In such a case, the checkpoint complete message will not have the stats, no? -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
Fix inconsistent reporting of checkpointer stats.
- 17cc5f666f6a 18.0 landed
-
Defer flushing of SLRU files.
- dee663f78439 14.0 cited