Re: BRIN is missing in multicolumn indexes documentation - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: BRIN is missing in multicolumn indexes documentation
Date
Msg-id 20160323124654.GA566706@alvherre.pgsql
Whole thread Raw
In response to Re: BRIN is missing in multicolumn indexes documentation  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: BRIN is missing in multicolumn indexes documentation
List pgsql-hackers
Emre Hasegeli wrote:
> > I guess multicolumn BRIN behaves similarly to B-tree or GiST. But I'm
> > no expert, so I need someone knowledgeable to confirm this. If the
> > following wording is OK, I will update the patch.
> 
> Multicolumn BRIN is like GIN.  Every column is indexed separately.
> The order of the columns doesn't matter.

Right.  You can use one index to cover all columns; the position of the
column in the index won't matter for a query that uses one column.  The
only reason to have multiple BRIN indexes on a single table is to have
a different pages_per_range.

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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_xlogdump fails to handle WAL file with multi-page XLP_FIRST_IS_CONTRECORD data
Next
From: Michael Paquier
Date:
Subject: Re: Postgres_fdw join pushdown - getting server crash in left outer join of three table