From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Covering Indexes |
Date: | 2012-06-28 16:53:13 |
Message-ID: | CAMkU=1yHznedk9O4bqZ55RY5Hx8d=cFwmOk2O5rk-eMd7QUhZg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 28, 2012 at 9:12 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>
> Excerpts from Tom Lane's message of jue jun 28 12:07:58 -0400 2012:
>
>> When this came up a couple weeks ago, the argument that was made for it
>> was that you could attach non-significant columns to an index that *is*
>> unique. That might or might not be a wide enough use-case to justify
>> adding such a horrid kludge.
>
> The other question is whether such an index would prevent an update from
> being HOT when the non-indexed values are touched.
That seems like an easy question to answer. How could it not disable
HOT and still work correctly?
> That could be a
> significant difference.
True, adding the covering column would not always be a win. But
surely it more likely to be a win when it can be done without adding
yet another index that also needs to be maintained.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-06-28 17:15:54 | Re: Posix Shared Mem patch |
Previous Message | Jeff Janes | 2012-06-28 16:46:22 | Re: Posix Shared Mem patch |