Re: Intermittent BRIN failures on hyrax and lousyjack
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2020-07-01T03:28:39Z
Lists: pgsql-hackers
On 2020-Jun-30, Tom Lane wrote:
> SELECT brin_desummarize_range('brinidx', 0);
> +WARNING: leftover placeholder tuple detected in BRIN index "brinidx", deleting
> I think the "crash" actually was the forced autovac cancellation we see
> here. Thus, the fact that both these animals use CLOBBER_CACHE_ALWAYS is
> not a direct cause of the failure, though it might contribute to getting
> the timing right for this to happen.
Oh, interesting.
> 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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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