From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regression test coverage of GiST index build is awful |
Date: | 2019-04-24 19:23:15 |
Message-ID: | 12006.1556133795@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> On Wed, Apr 24, 2019 at 9:31 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Why is this so bad? It's not like the gist regression test isn't
>> ridiculously expensive already; I'd have expected it to provide
>> darn near 100% coverage for what it's costing in runtime.
> I don't think there is any idea behind this. Seems to be just oversight.
After poking at it a bit, the answer seems to be that the gist buffering
code isn't invoked till we get to an index size of effective_cache_size/4,
which by default would be way too much for any regression test index.
> Do you like me to write a patch improving coverage here?
Somebody needs to... that's an awful lot of code to not be testing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2019-04-24 21:07:13 | TRACE_SORT defined by default |
Previous Message | Ashwin Agrawal | 2019-04-24 19:19:20 | Re: Zedstore - compressed in-core columnar storage |