Re: [PATCH] Covering SPGiST index - Mailing list pgsql-hackers

From Pavel Borisov
Subject Re: [PATCH] Covering SPGiST index
Date
Msg-id CALT9ZEGtcCEogHNg72kxTJYs_XZoEVt2Lb894-Q6gw_JRtidWQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Covering SPGiST index  ("Andrey M. Borodin" <x4mmm@yandex-team.ru>)
Responses Re: [PATCH] Covering SPGiST index
List pgsql-hackers
On a first glance the whole concept of non-multicolumn index with included attributes seems...well, just difficult to understand.
But I expect for SP-GiST this must be single key with multiple included attributes, right?
I couldn't find a test that checks impossibility of on 2-column SP-GiST, only few asserts about it. Is this checked somewhere else?

Yes, SpGist is by its construction a single-column index, there is no such thing like 2-column SP-GiST yet. In the same way like original SpGist will refuse to add a second key column, this remains after modification as well, with exception of columns attached by INCLUDE directive. They can be (INDEX_MAX_KEYS -1) pieces and they will not be used to create additional index trees (as there is only one), they will be just attached to the key tree leafs tuple. 

I also little bit corrected error reporting for the case when user wants to invoke index build with not one column. Thanks!

-- 
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com
Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Unnecessary delay in streaming replication due to replay lag
Next
From: Magnus Hagander
Date:
Subject: Re: public schema default ACL