Re: Index only scan paving the way for "auto" clustered tables?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Royce Ausburn" <royce(dot)ml(at)inomial(dot)com>
Cc: "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index only scan paving the way for "auto" clustered tables?
Date: 2011-10-11 19:02:56
Message-ID: 4E944C900200002500041DFB@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-10-11 19:18:51 Re: COUNT(*) and index-only scans
Previous Message Joe Conway 2011-10-11 18:57:29 Re: SET variable - Permission issues