MIME-Version: 1.0
References: <E1nca5h-000nN0-6f@gemulon.postgresql.org>
 <394950.1651077914@sss.pgh.pa.us>
 <F9294C25-83A0-49F1-9F39-3179739AEF63@enterprisedb.com>
 <A188C72D-E63F-405A-8992-237E1995CB38@enterprisedb.com>
In-Reply-To: <A188C72D-E63F-405A-8992-237E1995CB38@enterprisedb.com>
From: Thomas Munro <thomas.munro@gmail.com>
Date: Wed, 11 May 2022 17:28:15 +1200
Message-ID: 
 <CA+hUKGLDA-GuQKRvDF3abHadDrrYZ33N9e4DEOGwKH3JqdYSCQ@mail.gmail.com>
Subject: Re: Unstable tests for recovery conflict handling
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>,
	Melanie Plageman <melanieplageman@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BhUKGLDA-GuQKRvDF3abHadDrrYZ33N9e4DEOGwKH3JqdYSCQ%40mail.gmail.com>
Precedence: bulk

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.