Re: Purpose of wal_init_zero

From: Robert Pang <robertpang(at)google(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andy Fan <zhihuifan1213(at)163(dot)com>, Ritu Bhandari <mailritubhandari(at)gmail(dot)com>
Subject: Re: Purpose of wal_init_zero
Date: 2025-01-22 21:18:00
Message-ID: CAJhEC05A=77oaL_Zt94JttaQMbBJFx7kiBivN62+N9j-VC9uow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 15, 2025 at 12:05 PM Andres Freund <andres(at)anarazel(dot)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?

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-01-22 21:24:19 Re: BitmapHeapScan streaming read user and prelim refactoring
Previous Message Masahiko Sawada 2025-01-22 21:17:03 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart