Re: Potential BRIN Index Corruption

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Potential BRIN Index Corruption
Дата
Msg-id 20201126024244.GA15675@alvherre.pgsql
обсуждение исходный текст
Ответ на Potential BRIN Index Corruption  (Huan Ruan <leohuanruan@gmail.com>)
Ответы Re: Potential BRIN Index Corruption  (Huan Ruan <leohuanruan@gmail.com>)
Список 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.




В списке pgsql-general по дате отправления:

Предыдущее
От: Huan Ruan
Дата:
Сообщение: Potential BRIN Index Corruption
Следующее
От: 江川潔
Дата:
Сообщение: Re: archive file "00000001000000000000006F" has wrong size: 67118648 instead of 16777216