Re: BRIN is missing in multicolumn indexes documentation

From: Petr Jediný <petr(dot)jediny(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BRIN is missing in multicolumn indexes documentation
Date: 2016-03-22 14:36:44
Message-ID: CAD=W4J-oYgX_GVz3mSuiqkX_GnXOVC9AZaDXNzFdQzd_CTUJQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Good catch!
>
> In addtion to your patch, we should add the description for
> the multicolumn brin index, like the following one in the doc?
>
> ---------------
> A multicolumn GIN index can be used with query conditions that
> involve any subset of the index's columns. Unlike B-tree or GiST,
> index search effectiveness is the same regardless of which index
> column(s) the query conditions use.
> ---------------

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.

-----
A multicolumn BRIN index can be used with query conditions that
involve any subset of the index's columns. Conditions on additional
columns restrict the entries returned by the index, but the condition
on the first column is the most important one for determining how much
of the index needs to be scanned.
-----

Regards,

PJ

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2016-03-22 14:37:15 Re: NOT EXIST for PREPARE
Previous Message Amit Kapila 2016-03-22 14:36:13 Re: Speed up Clog Access by increasing CLOG buffers