Re: Potential BRIN Index Corruption

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Huan Ruan <leohuanruan(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Potential BRIN Index Corruption
Date: 2020-11-26 02:42:44
Message-ID: 20201126024244.GA15675@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2020-Nov-26, Huan Ruan wrote:

> Hi All
>
> We cannot work out a reproducible case but we have a copy of the offending
> database. I was hoping to know

I think the way to debug this would be to see what WAL records have been
emitted for the index, using pageinspect to find the problem index
tuple.

Use 'select ctid rrom large_table_with_623m_records where ...' to
pinpoint the unindexed tuple's page number; see when (in LSN) was that
tuple written; inspect WAL surroundings looking for updates (or lack
thereof) for the BRIN index. Use pageinspect to examine raw brin data.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message 江川潔 2020-11-26 03:06:53 Re: archive file "00000001000000000000006F" has wrong size: 67118648 instead of 16777216
Previous Message Huan Ruan 2020-11-26 00:46:08 Potential BRIN Index Corruption