| From: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | Thomas Carroll <tomfecarroll(at)yahoo(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Wal_keep_size |
| Date: | 2025-10-07 04:54:51 |
| Message-ID: | CAJk5Ata7Kz-k=KfEyZVhckVgrk8_faNgGd3RcRnV2tzqs_D5ig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Note archive mode is enabled.
On Tue, 7 Oct 2025, 10:22 Raj, <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
> 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, <tomfecarroll(at)yahoo(dot)com> 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 <
>> rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
>>
>>
>> Should Wal_keep_size <= max_wal_size ?
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-10-07 05:28:45 | Re: Wal_keep_size |
| Previous Message | Raj | 2025-10-07 04:52:47 | Re: Wal_keep_size |