From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Intermittent BRIN failures on hyrax and lousyjack
In-reply-to: <20200701032839.GA16862@alvherre.pgsql>
References: <20200701032839.GA16862@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Tue, 30 Jun 2020 23:28:39 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2011046.1594334780.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Jul 2020 18:46:20 -0400
Message-ID: <2011047.1594334780@sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2020-Jun-30, Tom Lane wrote:
>> SELECT brin_desummarize_range('brinidx', 0);
>> +WARNING:  leftover placeholder tuple detected in BRIN index "brinidx",=
 deleting

>> So (1) the comment needs to be adjusted to mention that vacuum
>> cancellation is enough to create the situation, and (2) probably the
>> message needs to be downgraded quite a lot, DEBUG2 or even less.
>> Or maybe we could just delete the quoted stanza altogether.

> Yeah, maybe deleting the whole thing is a decent answer.  When I wrote
> that, I was thinking that it was a very unlikely event, but evidently
> that's not true.

trilobite (also a CCA animal) just reported one of these, too:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dtrilobite&dt=3D2=
020-07-09%2008%3A03%3A08

Were you going to fix this, or did you expect me to?
If the latter, I lean to just deleting the message.

			regards, tom lane