From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Subject: Re: Bogus reports from coverage.postgresql.org
In-reply-to: 
 <CABUevEyydszbZJPF6iyjU45C+Kx4YSCa+KDZJkXNdjiGbE0Ojg@mail.gmail.com>
References: <30022.1520642188@sss.pgh.pa.us>
 <d0eec0fd-bf3b-55da-f5de-4fa1c00ce400@2ndquadrant.com>
 <CABUevEyydszbZJPF6iyjU45C+Kx4YSCa+KDZJkXNdjiGbE0Ojg@mail.gmail.com>
Comments: In-reply-to Magnus Hagander <magnus@hagander.net>
	message dated "Sun, 11 Mar 2018 15:18:13 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30194.1520790475.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Mar 2018 13:47:55 -0400
Message-ID: <30195.1520790475@sss.pgh.pa.us>
Precedence: bulk

Magnus Hagander <magnus@hagander.net> writes:
> On Sun, Mar 11, 2018 at 3:08 PM, Peter Eisentraut <peter.eisentraut@2ndq=
uadrant.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 vers=
ion
> 1.13, and there is no newer version packaged for debian or from what I c=
an
> tell even released?

It could also be a compiler issue, I believe.

			regards, tom lane