From: Andres Freund <andres@anarazel.de>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Temporarily skip recovery deadlock test in back branches.
Date: Fri, 06 May 2022 16:36:15 +0000
Message-ID: <E1nn0wA-000IKw-61@gemulon.postgresql.org> (raw)
Temporarily skip recovery deadlock test in back branches.
The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in
HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1)
adjust_conf() doesn't exist, which is easy enough to work around 2) a restart
cleares the recovery conflict stats < 15.
These issues can be worked around, but given the upcoming set of minor
releases, skip the problematic test for now. The buildfarm doesn't show
failures in other parts of 031_recovery_conflict.pl.
Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de
Backpatch: 10-14
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/4e39957e6eb52887c2d631e9edf08a07c306ec9f
Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 5 +++++
1 file changed, 5 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: andres@anarazel.de
Subject: Re: pgsql: Temporarily skip recovery deadlock test in back branches.
In-Reply-To: <E1nn0wA-000IKw-61@gemulon.postgresql.org>
References: <E1nn0wA-000IKw-61@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox