Re: 019_replslot_limit.pl might fail due to checkpoint skipped - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: 019_replslot_limit.pl might fail due to checkpoint skipped
Date
Msg-id CAHGQGwF_O7ZxAdW-TRQ1K83nm9OcHyAhAaVB4bXu_j+GaskvQQ@mail.gmail.com
Whole thread
In response to 019_replslot_limit.pl might fail due to checkpoint skipped  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: [PATCH] REPLICA IDENTITY USING INDEX accepts column with invalid NOT NULL
Re: [PATCH] REPLICA IDENTITY USING INDEX accepts column with invalid NOT NULL
List pgsql-hackers
On Wed, Aug 12, 2026 at 12:06 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
> Actually the test can pass without increasing the max_wal_size. Ultimately, we do
> not have to set both min_wal_size and max_wal_size: we enforce the CHECKPOINT
> here. My fresh brain feels that such unnecessary settings can be avoided, done
> in v2.

Thanks for updating the patch! The test changes look good to me.

I also updated the commit message and adjusted the comment for the new
test. Attached is v3.

Barring any objections, I'm thinking to commit it.

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Offline data checksum changes can cause incorrect checksum state on standbys
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Logical replication row filter loses unchanged toasted columns