From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Bug in bttext_abbrev_convert() |
Date: | 2015-07-01 05:35:33 |
Message-ID: | CAM3SWZQ+aTShUVmZ6aN+P+TKVJnFxaN4pueNhWoC9aZY2EB_0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 30, 2015 at 10:25 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> It would be nice to always have a html report from gcov always
> available on the internet. That would be something useful to automate,
> IMV. Watching that regress over time might provide useful insight, but
> I only use gcov a couple of times a year, so that's not going to
> happen on its own.
I generated such a report just now, and noticed this:
1137 : tuplesort_performsort(btspool->sortstate);
214 1131 : if (btspool2)
215 0 : tuplesort_performsort(btspool2->sortstate);
216 :
217 1131 : wstate.heap = btspool->heap;
218 1131 : wstate.index = btspool->index;
The regression tests have zero coverage for this
tuplesort_performsort() "btspool2" case. That's a fairly common case
to have no coverage for, and that took me all of 5 minutes to find.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-07-01 05:37:23 | Re: Parallel Seq Scan |
Previous Message | Peter Geoghegan | 2015-07-01 05:25:46 | Re: Bug in bttext_abbrev_convert() |