Re: Purpose of wal_init_zero - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Purpose of wal_init_zero
Date
Msg-id CAMT0RQRLjftQ1M-PPAy8SxnyUr5GhuXNRRMct8YXzbSdVX0qFQ@mail.gmail.com
Whole thread Raw
In response to Re: Purpose of wal_init_zero  (Robert Pang <robertpang@google.com>)
List pgsql-hackers
On Wed, Jan 22, 2025 at 10:18 PM Robert Pang <robertpang@google.com> wrote:
>
> On Wed, Jan 15, 2025 at 12:05 PM Andres Freund <andres@anarazel.de> wrote:
> >
> > If you have wal_recycle=true, this overhead will only be paid the first time a
> > WAL segment is used, of course, not after recycling.
>
> Today, our pg_stat_wal view [1] does not report the no. of WAL
> segments recycled. How about if we add a column to report it so users
> can track how many WAL segments are recycled vs. created over a period
> of time?

Maybe even add the full set of (recycled, created, deleted and
zero-filled) so we have a full picture.

And possible duplicate the set for "in the background" and "inline /
stalling the production work" for the operations where it makes sense
(created, zero-filled)

> [1] https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-WAL-VIEW
>
>



pgsql-hackers by date:

Previous
From: Maxim Orlov
Date:
Subject: Re: postgres_fdw could deparse ArrayCoerceExpr
Next
From: Tom Lane
Date:
Subject: Re: why -Fdance archive format option works with ./pg_restore but not with ./pg_dump?