Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness - Mailing list pgsql-hackers

From Andres Freund
Subject Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness
Date
Msg-id 20210727004800.ctofuuxnd4prp4as@alap3.anarazel.de
Whole thread Raw
In response to Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
Hi,

On 2021-07-26 20:27:21 +0000, Bossart, Nathan wrote:
> +1.  I was confused by this when working on a WAL pre-allocation
> patch [0].  Perhaps it could be replaced by a new parameter and a new
> field in pg_stat_wal.  How about something like log_wal_init_interval,
> where the value is the minimum amount of time between reporting the
> number of WAL segments created since the last report?

Why not just make the number in log_checkpoints accurate? There's no
point in the current number, so we don't need to preserve it...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness
Next
From: Andres Freund
Date:
Subject: Re: log_checkpoint's "WAL file(s) added" is misleading to the point of uselessness