On Thu, Apr 28, 2022 at 5:50 AM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> psql:<stdin>:1: ERROR: prepared transaction with identifier "xact_012_1" does not exist
> [10:26:16.314](1.215s) not ok 11 - Rollback of PGPROC_MAX_CACHED_SUBXIDS+ prepared transaction on promoted standby
> [10:26:16.314](0.000s)
> [10:26:16.314](0.000s) # Failed test 'Rollback of PGPROC_MAX_CACHED_SUBXIDS+ prepared transaction on promoted
standby'
> [10:26:16.314](0.000s) # at t/012_subtransactions.pl line 208.
> [10:26:16.314](0.000s) # got: '3'
> # expected: '0'
FWIW I see that on my FBSD/clang system when I build with
-fsanitize=undefined -fno-sanitize-recover=all. It's something to do
with our stack depth detection and tricks being used by -fsanitize,
because there's a stack depth exceeded message in the log.
