From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Recent failures in IsolationCheck deadlock-hard |
Date: | 2019-08-02 14:11:30 |
Message-ID: | 32202.1564755090@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> 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:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2019-08-01%2015%3A48%3A16
What that looks like is the queries got stuck and eventually
isolationtester gave up and canceled the test. So I'm suspicious
that there's a second bug in the parallel deadlock detection code.
Possibly relevant factoids: all three of the animals in question
run HEAD with force_parallel_mode = regress, and there's reason
to think that their timing behavior could be different from other
animals (anole and gharial run on HPUX, while hyrax uses
CLOBBER_CACHE_ALWAYS).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2019-08-02 14:32:53 | Re: Patch to document base64 encoding |
Previous Message | Konstantin Knizhnik | 2019-08-02 13:45:43 | Re: pglz performance |