Re: 019_replslot_limit.pl might fail due to checkpoint skipped

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 019_replslot_limit.pl might fail due to checkpoint skipped
Date: 2026-08-09 10:00:00
Message-ID: 27c8e9ee-fe77-4b2a-a687-50953a01518c@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Kuroda-san,

07.08.2026 09:44, Hayato Kuroda (Fujitsu) wrote:
> IIUC, the workaround is to force the CHECKPOINT after advancing WAL segments.
> Also, we can increase the max_wal_size to avoid the checkpoint due to WAL files.
>
> Please see attached. How do you feel?
>
> [1]: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=partridge&dt=2026-08-06%2018%3A00%3A11

Thank you for paying attention to the issue!

I've tested $checkpoint->query_until() and confirmed that this approach
(which is also used in 4 other tests) eliminates the failure. I haven't
observed an effect of "max_wal_size = 40MB", so I'm not sure about it.
Do you have a scenario in mind, when it could be useful for the test?

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-08-09 11:22:19 Re: Adding comments to extension objects
Previous Message Hüseyin Demir 2026-08-09 08:54:55 Re: PSQL - improve tab completion for pub/sub options