Horton

Re: GIN predicate locking slows down valgrind isolationtests tremendously

Alexander Korotkov <a.korotkov@postgrespro.ru>

View thread View on postgr.es
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Teodor Sigaev <teodor@sigaev.ru>, Shubham Barai <shubhambaraiss@gmail.com>, Dmitry Ivanov <d.ivanov@postgrespro.ru>
Date: 2018-12-20T22:50:41Z
Lists: pgsql-hackers 
чт, 20 дек. 2018 г., 2:22 Andres Freund andres@anarazel.de:

> 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...
>

I'm going to take a look on that.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Reduce length of GIN predicate locking isolation test suite

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