Horton

Re: GIN predicate locking slows down valgrind isolationtests tremendously

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
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-19T23:22:28Z
Lists: pgsql-hackers 
On 2018-12-03 16:07:40 -0800, Andres Freund wrote:
> 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?

Ping?

It's also one of the slowest tests outside of valgrind...

Greetings,

Andres Freund

Commits

  1. Reduce length of GIN predicate locking isolation test suite

  2. Remove entry tree root conflict checking from GIN predicate locking