Re: Unstable tests for recovery conflict handling

From: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Unstable tests for recovery conflict handling
Date: 2022-04-28 15:42:38
Message-ID: 40CF9459-C04E-49DE-9D7E-E778CA2352E9@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

> On Apr 27, 2022, at 6:26 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> I'm a bit confused - what's the relation of that failure to this thread / the
> tests / this commit?

None, upon further reflection. It turned out to be unrelated. Sorry for the noise.


Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2022-04-28 19:34:41 pgsql: Fix JSON_OBJECTAGG uniquefying bug
Previous Message Etsuro Fujita 2022-04-28 06:27:12 pgsql: Disable asynchronous execution if using gating Result nodes.

Browse pgsql-hackers by date

  From Date Subject
Next Message Przemysław Sztoch 2022-04-28 16:50:57 [PATCH] Completed unaccent dictionary with many missing characters
Previous Message Tomas Vondra 2022-04-28 15:35:09 Re: bogus: logical replication rows/cols combinations