From: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: WIP: Covering + unique indexes.
Date: Fri, 4 Dec 2015 20:00:16 +0300
Message-ID: <5661C6A0.2020602@postgrespro.ru> (raw)
In-Reply-To: <CA+TgmoYGPcKVtySqs1OFbfkpOt+mtXiRtCj-vqQ_d4swxNXGCg@mail.gmail.com>
References: <56167F09.3090101@postgrespro.ru>
<56168952.4010101@postgrespro.ru>
<CAA-aLv7mWdu5WCrUH0sw79abDsq4tdZEpkvV8SfgNyLp92+z6Q@mail.gmail.com>
<5617DAA3.6080408@postgrespro.ru>
<565D9859.3040405@postgrespro.ru>
<CA+TgmoYGPcKVtySqs1OFbfkpOt+mtXiRtCj-vqQ_d4swxNXGCg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
03.12.2015 04:03, Robert Haas пишет:
> On Tue, Dec 1, 2015 at 7:53 AM, Anastasia Lubennikova
> <a.lubennikova@postgrespro.ru> wrote:
>> If we don't need c4 as an index scankey, we don't need any btree opclass on
>> it.
>> But we still want to have it in covering index for queries like
>>
>> SELECT c4 FROM tbl WHERE c1=1000; // uses the IndexOnlyScan
>> SELECT * FROM tbl WHERE c1=1000; // uses the IndexOnlyScan
>>
>> The patch "optional_opclass" completely ignores opclasses of included
>> attributes.
> OK, I don't get it. Why have an opclass here at all, even optionally?
We haven't opclass on c4 and there's no need to have it.
But now (without a patch) it's impossible to create covering index,
which contains columns with no opclass for btree.
test=# create index on tbl using btree (c1, c4);
ERROR: data type box has no default operator class for access method
"btree"
ComputeIndexAttrs() processes the list of index attributes and trying to
get an opclass for each of them via GetIndexOpClass().
The patch drops this check for included attributes. So it makes possible
to store any datatype in btree and use IndexOnlyScan advantages.
I hope that this helps to clarify.
--
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: a.lubennikova@postgrespro.ru, robertmhaas@gmail.com
Subject: Re: WIP: Covering + unique indexes.
In-Reply-To: <5661C6A0.2020602@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox