Re: Indirect indexes - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Indirect indexes
Date
Msg-id CAGTBQpYWd7zFJGYGYB08=jCM6ei+om0KpxXFzViE-q=M6=HPrA@mail.gmail.com
Whole thread Raw
In response to Re: Indirect indexes  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Wed, Oct 19, 2016 at 10:21 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Simon objected that putting the PK
>> into the index tuple would disable HOT, but I don't think that's a
>> valid objection.
>
> Just to be clear, that's not what I objected to. Claudio appeared to
> be suggesting that an indirect index is the same thing as an index
> with PK tacked onto the end, which I re-confirm is not the case since
> doing that would not provide the primary objective of indirect
> indexes.

No, I was suggesting using the storage format of those indexes.
Perhaps I wasn't clear.

CREATE INDEX could be implemented entirely as the rewrite I mention, I
believe. But everything else can't, as you say.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] packing/alignment annotation for ItemPointerData redux
Next
From: Andreas Joseph Krogh
Date:
Subject: Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.