From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 18:38:56 |
Message-ID: | CAPpHfds1Dre7=Lw3G71MxPD8ukKJke0z5kdz+Et2_TaDHYbufw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 24, 2019 at 9:31 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This tells a pretty scary story:
>
> https://coverage.postgresql.org/src/backend/access/gist/index.html
>
> In particular, gistbuildbuffers.c is not entered *at all*, and
> gistbuild.c is only 21% covered.
>
> I noticed this after adding an assertion that I expected
> gistInitBuildBuffers to fail on, and nonetheless getting
> through check-world just fine.
>
> 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.
Do you like me to write a patch improving coverage here?
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Brusselback | 2019-04-24 18:46:15 | Re: Optimizer items in the release notes |
Previous Message | Tom Lane | 2019-04-24 18:31:18 | Regression test coverage of GiST index build is awful |