Re: BRIN indexes - TRAP: BadArgument - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: BRIN indexes - TRAP: BadArgument
Date
Msg-id CA+U5nMLxzTzkn1-MzsQKm3mu9VXwQLKS-t2AKOi0eHBWceWypg@mail.gmail.com
Whole thread Raw
In response to Re: BRIN indexes - TRAP: BadArgument  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 3 November 2014 22:18, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:

> So here's v21.  I also attach a partial diff from v20, just in case
> anyone wants to give it a look.

Looks really good.

I'd like to reword this sentence in the readme, since one of the main
use cases would be tables without btrees  It's unlikely that BRIN would be the only
+ indexes in a table, though, because primary keys can be btrees only, and so
+ we don't implement this optimization.

I don't see a regression test. Create, use, VACUUM, just so we know it
hasn't regressed after commit.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Let's drop two obsolete features which are bear-traps for novices
Next
From: Andres Freund
Date:
Subject: Re: tracking commit timestamps