Re: Covering Indexes

From: Florian Weimer <fw(at)deneb(dot)enyo(dot)de>
To: Jeff Janes <jeff(dot)janes(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-08-25 07:53:30
Message-ID: 877gsns8zp.fsf@mid.deneb.enyo.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Jeff Janes:

> I don't see the virtue of this in this case. Since the index is not
> unique, why not just put the index on (a,b,c,d) and be done with it?

AFAICT, SQLite 4 encodes keys in a way that is not easily reversed
(although the encoding is injective, so it's reversible in principle).
Therefore, covered columns need to be listed separately, so they are
not subject to the key encoding.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit kapila 2012-08-25 11:46:11 Re: [WIP] Performance Improvement by reducing WAL for Update Operation
Previous Message Andres Freund 2012-08-25 05:57:50 Re: plperl sigfpe reset can crash the server