Re: BRIN de-summarize ranges

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: "Seki, Eiji" <seki(dot)eiji(at)jp(dot)fujitsu(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BRIN de-summarize ranges
Date: 2017-04-01 17:42:27
Message-ID: 20170401174227.t3326opnqo7co4zx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-Support-BRIN-de-summarization.patch text/plain 14.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-04-01 17:54:45 Re: New CORRESPONDING clause design
Previous Message anant khandelwal 2017-04-01 17:13:26 Re: GSoC 2017 Proposal for "Explicitly support predicate locks in index access methods besides btree"