Re: BRIN index bug due to WAL refactoring

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BRIN index bug due to WAL refactoring
Date: 2015-06-26 18:35:24
Message-ID: 20150626183524.GS3289@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes wrote:

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

Nice. As I understand it, the problem is that the replay is using the
block number of the revmap page as target blkno of the revmap entry,
when it should be using the block number of the data page. This should
fix it.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
brin-wal-replay.patch text/x-diff 1.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-06-26 18:37:23 Re: 9.5 release notes
Previous Message Robert Haas 2015-06-26 18:32:35 Re: Support for N synchronous standby servers - take 2