Re: Stabilize 026_overwrite_contrecord test

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Stabilize 026_overwrite_contrecord test
Date: 2026-09-03 17:00:00
Message-ID: 66defc33-dfc4-4df5-8813-3a8c0babcb6a@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Michael and Fujii-san,

03.09.2026 03:33, Michael Paquier wrote:
> On Thu, Sep 03, 2026 at 09:28:22AM +0900, Fujii Masao wrote:
>> The attached patch fixes this by setting checkpoint_timeout high enough
>> to prevent unrelated checkpoints during this test. This follows the same
>> approach used by other recovery tests, such as 043_no_contrecord_switch.pl.
> Yes, this failure is also something that was puzzling me a bit, but I
> did not take the time to dig into it. Enforcing a larger checkpoint
> timeout sounds like a safety measure good enough, at quick glance.

Please look at:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures

where all such failures are enumerated with links to corresponding
reports/discussions, e.g. I reported this one previously:
https://www.postgresql.org/message-id/9ffdb19a-7a89-424e-925a-dd981c37f0ba%40gmail.com

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2026-09-03 17:01:09 Re: FOR PORTION OF: BEFORE INSERT triggers can silently drop leftover rows?
Previous Message Jacob Champion 2026-09-03 16:49:49 Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension