Re: BRIN de-summarize ranges - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: BRIN de-summarize ranges
Date
Msg-id 20170401174227.t3326opnqo7co4zx@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] BRIN de-summarize ranges  ("Seki, Eiji" <seki.eiji@jp.fujitsu.com>)
Responses Re: BRIN de-summarize ranges  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Seki, Eiji wrote:

> However, I found that when calling brin_desummarize_range
> successively, an assertion is failed. It seems to me that it occurs
> when desummarizing a revmap page that is already desummarized.

You're right, it's broken for that case.  Here's a fixed patch.


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

pgsql-hackers by date:

Previous
From: anant khandelwal
Date:
Subject: Re: GSoC 2017 Proposal for "Explicitly support predicate locks inindex access methods besides btree"
Next
From: Tom Lane
Date:
Subject: Re: New CORRESPONDING clause design