| From: | Petr Jediný <petr(dot)jediny(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Emre Hasegeli <emre(at)hasegeli(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BRIN is missing in multicolumn indexes documentation |
| Date: | 2016-03-28 17:10:08 |
| Message-ID: | CAD=W4J_+xUiwb_z=097kfDWp_fkuufqWFAAMf+=EbxhN1r4kjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Comments? This is my first patch to postgresql project, so comments
are very much welcomed.
PJ
On Wed, Mar 23, 2016 at 8:40 PM, Petr Jediný <petr(dot)jediny(at)gmail(dot)com> wrote:
>>>
>>> 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.
>
> Thanks for the information, I've attached the patch updated to v2.
>
>
> PJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-03-28 17:20:49 | Re: Speed up Clog Access by increasing CLOG buffers |
| Previous Message | Paul Ramsey | 2016-03-28 17:01:36 | Re: Parallel Queries and PostGIS |