Weird failure with latches in curculio on v15

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Weird failure with latches in curculio on v15
Date: 2023-02-01 01:53:17
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi all,

While browsing the buildfarm, I have noticed this failure on curcilio:

The test that has reported a failure is the check on the archive
module callback:
# Failed test 'check shutdown callback of shell archive module'
# at t/ line 248.
# Looks like you failed 1 test of 17.
[02:28:06] t/ ..............
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/17 subtests

Looking closer, this is a result of an assertion failure in the latch
2023-02-01 02:28:05.615 CET [6961:8] LOG: received fast shutdown request
2023-02-01 02:28:05.615 CET [6961:9] LOG: aborting any active transactions
2023-02-01 02:28:05.616 CET [30681:9] LOG: process 30681 releasing ProcSignal slot 33, but it contains 0
TRAP: FailedAssertion("latch->owner_pid == MyProcPid", File: "latch.c", Line: 451, PID: 30681)

The information available in standby2.log shows that 30681 is the
startup process. I am not sure what all that means, yet.

Thoughts or comments welcome.


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-02-01 01:58:46 Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?
Previous Message Thomas Munro 2023-02-01 01:44:53 Re: pg_upgrade test failure