Re: Recent failures in IsolationCheck deadlock-hard
От | Tom Lane |
---|---|
Тема | Re: Recent failures in IsolationCheck deadlock-hard |
Дата | |
Msg-id | 32202.1564755090@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Recent failures in IsolationCheck deadlock-hard (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: Recent failures in IsolationCheck deadlock-hard
|
Список | pgsql-hackers |
Thomas Munro <thomas.munro@gmail.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
В списке pgsql-hackers по дате отправления: