Re: Intermittent BRIN failures on hyrax and lousyjack
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2020-07-09T22:46:20Z
Lists: 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
Commits
-
Remove WARNING message from brin_desummarize_range
- ca5001a36188 12.4 landed
- c3a79e71929a 13.0 landed
- 986529ce40c6 14.0 landed
- 907283576da5 11.9 landed
- 40316dfedc10 10.14 landed
-
BRIN de-summarization
- c655899ba9ae 10.0 cited