pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix timing issue in deadlock recovery conflict test.
Date: Wed, 04 May 2022 20:25:15 +0000
Message-ID: <E1nmLYh-002YY1-Aa@gemulon.postgresql.org> (raw)

Fix timing issue in deadlock recovery conflict test.

Per buildfarm members longfin and skink.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/3197e0f5ae9d58a0dd45e1bf8646ce83791bb2de

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 11 +++++++++++
1 file changed, 11 insertions(+)



view thread (6+ messages)

Message-ID: <E1nmLYh-002YY1-Aa@gemulon.postgresql.org>
Permalink:  ../E1nmLYh-002YY1-Aa@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1nmLYh-002YY1-Aa@gemulon.postgresql.org

 · 

reply

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: Fix timing issue in deadlock recovery conflict test.
  In-Reply-To: <E1nmLYh-002YY1-Aa@gemulon.postgresql.org>
  References: <E1nmLYh-002YY1-Aa@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