BRIN index bug due to WAL refactoring - Mailing list pgsql-hackers

From Jeff Janes
Subject BRIN index bug due to WAL refactoring
Date
Msg-id CAMkU=1yKeTbjg0ThETaqhmgk2xRTrG6sTzChCP+OP0XKDKHPKQ@mail.gmail.com
Whole thread Raw
Responses Re: BRIN index bug due to WAL refactoring  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: BRIN index bug due to WAL refactoring  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
BRIN index WAL is broken in HEAD.

Commit 2c03216d831160bedd72d4, the Revamp the WAL record format, is the culprit.

The easiest way to see this is via streaming replication.

On master:

create table foobar as select * from generate_series(1,10000);
create index on foobar using brin (generate_series );

On replica:

set enable_seqscan TO off;
explain (analyze) select count(*) from foobar ;
ERROR:  corrupted BRIN index: inconsistent range map

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Next
From: Alvaro Herrera
Date:
Subject: Re: BRIN index bug due to WAL refactoring