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
Hello Michail,
07.07.2025 03:18, Michael Paquier wrote:
I'm failing to reproduce it, unfortunately. It looks like just a
timing issue with the reports, so the best option I can think of here
would be to switch the test to do a wait until the stats have been
generated, leading to the attached.
On Sun, Jul 06, 2025 at 12:00:00PM +0300, Alexander Lakhin wrote:
> This test case is rather new, it was added by f4694e0f3 (from 2025-03-05).
Thanks for the report.
> I could reproduce this failure within 20 test runs with the following
> modification:
> --- a/src/backend/postmaster/walsummarize
Hello hackers,
A couple of the 002.blocks test's failures occurred during past three
months: [1], [2] with the following diagnostics:
# Failed test 'WAL summarizer generates statistics for WAL reads'
# at
/home/bf/bf-build/culicidae/REL_18_STABLE/pgsql/src/bin/pg_walsummary/t/002_blocks.pl
