GIN predicate locking slows down valgrind isolationtests tremendously
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@postgresql.org, Teodor Sigaev <teodor@sigaev.ru>, Shubham Barai <shubhambaraiss@gmail.com>, Alexander Korotkov <a.korotkov@postgrespro.ru>, Dmitry Ivanov <d.ivanov@postgrespro.ru>
Date: 2018-12-04T00:07:40Z
Lists: pgsql-hackers
Hi, https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2018-03-31%2014%3A40%3A02 isolation-check (02:19:36) https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2018-03-28%2010%3A40%3A02 isolation-check (00:18:44) As far as I can tell that increase comes laregely from the new GIN tests. Could one of you please look at keeping the test time increase to something more reasonable? Greetings, Andres Freund
Commits
-
Reduce length of GIN predicate locking isolation test suite
- fcdda202bcf8 11.2 landed
- 0c6f4f9212cf 12.0 landed
-
Remove entry tree root conflict checking from GIN predicate locking
- b450abd2551e 12.0 landed
- fd7c08195592 11.2 landed