Re: Stabilize 026_overwrite_contrecord test

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: 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 00:33:33
Message-ID: apjAXUXTZRDkH9tU@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Thanks.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-09-03 00:40:23 Re: Remove fcinfo from statistics update internal functions
Previous Message Fujii Masao 2026-09-03 00:28:22 Stabilize 026_overwrite_contrecord test