Thomas Munro writes:
> On Tue, Aug 6, 2019 at 6:18 PM Tom Lane wrote:
>> Yeah, there have been half a dozen failures since deadlock-parallel
>> went in, mostly on critters that are slowed by CLOBBER_CACHE_ALWAYS
>> or valgrind. I've tried repeatedly to reproduce that here, without
>> success
On Tue, Aug 6, 2019 at 6:18 PM Tom Lane wrote:
> Thomas Munro writes:
> > On Sat, Aug 3, 2019 at 2:11 AM Tom Lane wrote:
> >> Also worth noting is that anole failed its first try at the new
> >> deadlock-parallel isolation test:
> >>
Thomas Munro writes:
> On Sat, Aug 3, 2019 at 2:11 AM Tom Lane wrote:
>> Also worth noting is that anole failed its first try at the new
>> deadlock-parallel isolation test:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole=2019-08-01%2015%3A48%3A16
> And friarbird (also
On Sat, Aug 3, 2019 at 2:11 AM Tom Lane wrote:
> Thomas Munro writes:
> > There have been five failures on three animals like this, over the
> > past couple of months:
>
> Also worth noting is that anole failed its first try at the new
> deadlock-parallel isolation test:
>
>
Thomas Munro writes:
> There have been five failures on three animals like this, over the
> past couple of months:
Also worth noting is that anole failed its first try at the new
deadlock-parallel isolation test:
Hi,
There have been five failures on three animals like this, over the
past couple of months:
step s6a7: LOCK TABLE a7;
step s7a8: LOCK TABLE a8;
step s8a1: LOCK TABLE a1;
-step s8a1: <... completed>
step s7a8: <... completed>
-error in steps s8a1 s7a8: ERROR: deadlock detected
+step
