From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Covering Indexes |
Date: | 2012-07-17 15:18:19 |
Message-ID: | CA+U5nMKu5UNfjxc4c7LE3EKzu0-EwNFgezj0nrTK108Yw-OK4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 June 2012 13:16, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> Very interesting design document for SQLite 4:
>
> http://www.sqlite.org/src4/doc/trunk/www/design.wiki
>
> I'm particularly intrigued by "covering indexes". For example:
>
> CREATE INDEX cover1 ON table1(a,b) COVERING(c,d);
>
> This allows the following query to do an index-only scan:
>
> SELECT c, d FROM table1 WHERE a=? AND b=?;
>
> Now that we have index-only scans in 9.2, I'm wondering if it would make sense to add covering index support, too, where additional, unindexed columns are stored alongside indexed columns.
Just to be clear, the ability to have covered indexes is already in
9.2, I updated the release notes to explain that a few months back.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2012-07-17 15:21:51 | Re: Covering Indexes |
Previous Message | Simon Riggs | 2012-07-17 15:05:49 | Re: Closing out the June commitfest |