Re: Failure in test_slru for host gokiburi (REL_16_STABLE only)

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>
Subject: Re: Failure in test_slru for host gokiburi (REL_16_STABLE only)
Date: 2026-05-26 08:09:31
Message-ID: ahVVO62s9iXxb7RU@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 18, 2026 at 08:41:45PM +0900, Michael Paquier wrote:
> While reading through the module, I think that the LWLock
> initialization logic is borked, where we decide to do a
> LWLockInitialize() more times than necessary, confusing the internal
> states. Honestly, I have no clue why the test has suddenly been
> failing, and why other buildfarm members don't complain. The host has
> been upgraded a couple of days ago to the latest Debian, but I also
> had a few clean runs in the buildfarm before this began showing up.
> What I do know is that the patch attached is able to make the tests of
> the module pass for v16 on the problematic host with -DEXEC_BACKEND.

Hearing nothing, I have fixed that on REL_16_STABLE to bring back my
animal to green. The tranche ID allocation calls are wasteful in the
module for v17 and v18, but it does not really matter much for the
sake of the tests. HEAD is in a much better state by saving the same
names in shmem (pronounced as in "shmemme").
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message SATYANARAYANA NARLAPURAM 2026-05-26 08:11:36 Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Previous Message Chao Li 2026-05-26 07:46:46 Re: Fix bug of CHECK constraint enforceability recursion