Re: Intermittent BRIN failures on hyrax and lousyjack

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Intermittent BRIN failures on hyrax and lousyjack
Date: 2020-07-01 03:28:39
Message-ID: 20200701032839.GA16862@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
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
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2020-07-01 04:12:14 v12 and TimeLine switches and backups/restores
Previous Message Alvaro Herrera 2020-07-01 03:26:05 Re: max_slot_wal_keep_size and wal_keep_segments