Re: Intermittent BRIN failures on hyrax and lousyjack - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Intermittent BRIN failures on hyrax and lousyjack
Date
Msg-id 2011047.1594334780@sss.pgh.pa.us
Whole thread Raw
In response to Re: Intermittent BRIN failures on hyrax and lousyjack  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Intermittent BRIN failures on hyrax and lousyjack  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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=trilobite&dt=2020-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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Default setting for enable_hashagg_disk
Next
From: Tom Lane
Date:
Subject: Re: Stale external URL in doc?