Re: Instability of pg_walsummary/002_blocks.pl due to timing

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Instability of pg_walsummary/002_blocks.pl due to timing
Date: 2025-07-08 04:59:32
Message-ID: aGyltGtBZUTtOWYc@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 07, 2025 at 08:00:01AM +0300, Alexander Lakhin wrote:
> I'm sorry for not being accurate enough -- I forgot to mention that I
> replicated the config from culicidae, and now I see that "fsync=on"
> is needed to reproduce the failure for me (though maybe).

Even with that, the situation was stable here with two hours running
the test in a loop.

> I got failures on iterations 3, 5, 1. With your patch applied, I got 100
> iterations passed.

This is good enough for me, so applied. Thanks for double-checking.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-07-08 06:02:12 Re: A recent message added to pg_upgade
Previous Message Bertrand Drouvot 2025-07-08 04:46:28 Re: Adding wait events statistics