BRIN index bug due to WAL refactoring

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: BRIN index bug due to WAL refactoring
Date: 2015-06-26 01:03:06
Message-ID: CAMkU=1yKeTbjg0ThETaqhmgk2xRTrG6sTzChCP+OP0XKDKHPKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-06-26 01:22:29 Re: BRIN index bug due to WAL refactoring
Previous Message Amit Kapila 2015-06-26 00:53:35 Re: RFC: replace pg_stat_activity.waiting with something more descriptive