Re: Index only scan paving the way for "auto" clustered tables? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Index only scan paving the way for "auto" clustered tables?
Date
Msg-id 4E944C900200002500041DFB@gw.wicourts.gov
Whole thread Raw
In response to Re: Index only scan paving the way for "auto" clustered tables?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Index only scan paving the way for "auto" clustered tables?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> wrote:
>> [implement "clustered index" as a covering index with all columns
>> which are present in the heap]

> I guess we could do that, but I'm not convinced there would be
> much benefit. 
The "traditional" way to implement a clustered index is to have the
leaf level of the index contain the tuples rather than pointers to
the tuples.  If we're going to do clustered tables, we might want to
jump all the way to that, rather than a half-way solution which
stores everything twice.
-Kevin


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: SET variable - Permission issues
Next
From: Josh Berkus
Date:
Subject: Re: unite recovery.conf and postgresql.conf