Re: BF mamba failure - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: BF mamba failure
Date
Msg-id 1941b7e2-be7c-9c4c-8505-c0fd05910e9a@gmail.com
Whole thread Raw
In response to Re: BF mamba failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BF mamba failure  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-hackers
Hi,

18.03.2023 07:26, Tom Lane wrote:
Amit Kapila <amit.kapila16@gmail.com> writes:
Peter Smith has recently reported a BF failure [1]. AFAICS, the call
stack of failure [2] is as follows:
Note the assertion report a few lines further up:

TRAP: failed Assert("pg_atomic_read_u32(&entry_ref->shared_entry->refcount) == 0"), File: "pgstat_shmem.c", Line: 560, PID: 25004

This assertion failure can be reproduced easily with the attached patch:
============== running regression test queries        ==============
test oldest_xmin                  ... ok           55 ms
test oldest_xmin                  ... FAILED (test process exited with exit code 1)      107 ms
test oldest_xmin                  ... FAILED (test process exited with exit code 1)        8 ms
============== shutting down postmaster               ==============

contrib/test_decoding/output_iso/log/postmaster.log contains:
TRAP: failed Assert("pg_atomic_read_u32(&entry_ref->shared_entry->refcount) == 0"), File: "pgstat_shmem.c", Line: 561, PID: 456844

With the sleep placed above Assert(entry_ref->shared_entry->dropped) this Assert fails too.

Best regards,
Alexander
Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Initial Schema Sync for Logical Replication
Next
From: Tomas Vondra
Date:
Subject: Re: logical decoding and replication of sequences, take 2