Petr Jediný wrote:
> Comments? This is my first patch to postgresql project, so comments
> are very much welcomed.
I think it's fine, so I pushed it. Thanks.
I hope you already read this
https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F
--
Álvaro Herrera
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ý wrote:
>>>
>>> Multicolumn BRIN is like GIN. Every column is indexed separately.
>>> The order of the columns doesn't matter.
>>
>>
>>
>> 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
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
> 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
> 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,
>
On Tue, Mar 22, 2016 at 12:53 AM, Petr Jediný wrote:
> Hello,
>
> the http://www.postgresql.org/docs/9.5/static/indexes-multicolumn.html
> page doesn't mention BRIN support, but according to the
> http://www.postgresql.org/docs/9.5/static/sql-createindex.html it is
>