public inbox for [email protected]  

help / color / mirror / Atom feed

From: Raj <[email protected]>
To: Thomas Carroll <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Wal_keep_size
Date: Tue, 7 Oct 2025 10:22:47 +0530
Message-ID: <CAJk5AtbeY+O71bbESq1+rG3zqv=mPzEDaxMniXuBfjZ7+RKpaw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAJk5AtbaQYshqms+AnVn0A_BOHFjfYhdEaAsLGWf0zVnA_5N7Q@mail.gmail.com>
	<[email protected]>

If wal_keep_size is more than max_wal_size wouldn't it always trigger
checkpoint ?

On Tue, 7 Oct 2025, 03:08 Thomas Carroll, <[email protected]> wrote:

> Hope nobody minds me chipping in here.
>
> The answer is "not necessarily."  The names make them seem closely
> related, but not so much.
>
> max_wal_size is all about *checkpoints*.  When the WAL exceeds this,
> Postgres will try to run a checkpoint.  Under some circumstances it won't,
> but let's keep it simple for now.
>
> wal_keep_size is all about *replication*.  Replicas need WAL files to
> stick around for long enough that they can process them.  wal_keep_size is
> a minimum figure.
>
> Tom
> On Monday, October 6, 2025 at 03:51:17 PM EDT, Raj <
> [email protected]> wrote:
>
>
> Should Wal_keep_size <= max_wal_size ?
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Wal_keep_size
  In-Reply-To: <CAJk5AtbeY+O71bbESq1+rG3zqv=mPzEDaxMniXuBfjZ7+RKpaw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox