| From: | Thomas Munro <munro(at)ip9(dot)org> |
|---|---|
| To: | Rob Wultsch <wultsch(at)gmail(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Covering Indexes |
| Date: | 2012-06-30 10:12:09 |
| Message-ID: | CADLWmXV-oDoD8+A+0n+xv3uE8n86jTTxfQtfMsm8-XXXQTC_JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 June 2012 14:02, Rob Wultsch <wultsch(at)gmail(dot)com> wrote:
> On Thu, Jun 28, 2012 at 8:16 AM, David E. Wheeler <david(at)justatheory(dot)com> wrote:
>> I'm particularly intrigued by "covering indexes". For example:
>>
>> CREATE INDEX cover1 ON table1(a,b) COVERING(c,d);
>
> IRC MS SQL also allow unindexed columns in the index.
For what it's worth, DB2 also has this feature, written roughly the
same way as MS SQL Server: CREATE INDEX cover1 ON table1(a, b) INCLUDE
(c, d).
Oracle doesn't seem to have this feature (and the SQL standard doesn't
mention indexes at all).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-06-30 10:44:04 | Re: elog/ereport noreturn decoration |
| Previous Message | Andres Freund | 2012-06-30 09:51:31 | XX000: enum value 117721 not found in cache for enum enumcrash |