Re: Intermittent BRIN failures on hyrax and lousyjack

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Intermittent BRIN failures on hyrax and lousyjack
Date: 2020-07-09 22:46:20
Message-ID: 2011047.1594334780@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-09 22:51:18 Re: Stale external URL in doc?
Previous Message Peter Geoghegan 2020-07-09 22:32:20 Re: Default setting for enable_hashagg_disk