Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1euSV6-0003sO-V0
	for pgsql-www@arkaria.postgresql.org; Sat, 10 Mar 2018 00:36:41 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1euSV5-00016p-BD
	for pgsql-www@arkaria.postgresql.org; Sat, 10 Mar 2018 00:36:39 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1euSV5-00016g-5w
	for pgsql-www@lists.postgresql.org; Sat, 10 Mar 2018 00:36:39 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1euSUx-0003Y2-5a
	for pgsql-www@lists.postgresql.org; Sat, 10 Mar 2018 00:36:38 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w2A0aSLD030023
	for <pgsql-www@lists.postgresql.org>; Fri, 9 Mar 2018 19:36:29 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-www@lists.postgresql.org
Subject: Bogus reports from coverage.postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30021.1520642188.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 09 Mar 2018 19:36:28 -0500
Message-ID: <30022.1520642188@sss.pgh.pa.us>
List-Id: <pgsql-www.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-www@lists.postgresql.org>
List-Owner: <mailto:pgsql-www-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-www>
Precedence: bulk

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.

This would be quite astonishing if true, but it isn't true, since
the regression tests aren't reporting any such failure.

Needless to say, this puts quite a damper on my faith in the coverage
reports.  Maybe that machine needs a software update?

			regards, tom lane