Re: GIN predicate locking slows down valgrind isolationtests tremendously - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: GIN predicate locking slows down valgrind isolationtests tremendously
Date
Msg-id CAPpHfduGUPreQSAV2q0W4XcOEDPM8PdCSrEOMWnX6nadKs1c3A@mail.gmail.com
Whole thread Raw
In response to Re: GIN predicate locking slows down valgrind isolationteststremendously  (Andres Freund <andres@anarazel.de>)
Responses Re: GIN predicate locking slows down valgrind isolationtests tremendously  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Re: GIN predicate locking slows down valgrind isolationtests tremendously  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
List 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 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Tid scan improvements
Next
From: Tom Lane
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)