| 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-23 19:40:54 |
| Message-ID: | CAD=W4J_Ui1G7eh=bNqsMgPDMc9GQELLp5sJ2asOLkUpJW-_DHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>
>> 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
| Attachment | Content-Type | Size |
|---|---|---|
| brin-multicolumn-doc-v2.patch | application/octet-stream | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-23 19:43:12 | Re: Relation extension scalability |
| Previous Message | Tom Lane | 2016-03-23 19:38:31 | Re: Rationalizing code-sharing among src/bin/ directories |