Re: Bogus reports from coverage.postgresql.org

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Mar 11, 2018 at 3:08 PM, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> On 3/9/18 19:36, Tom Lane wrote:
>>> I happened to notice that if you look at
>>> https://coverage.postgresql.org/src/backend/optimizer/util/predtest.c.gcov.html
>>> it claims that the two occurrences of
>>> elog(ERROR, "predicate_classify returned a bogus value");
>>> at lines 492 and 803 are reached.

>> I can't reproduce this locally, so yeah, maybe we should check whether
>> the toolchain could be updated.

Now that I look, I don't see this behavior on my local machine (RHEL6,
gcc 4.4.7, lcov 1.10) either.

> Is it specifically "lcov" we are considering here? If so, we are on version
> 1.13, and there is no newer version packaged for debian or from what I can
> tell even released?

It could also be a compiler issue, I believe.

regards, tom lane