| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mike Christensen <imaudi(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: What are the benefits of using a clustered index? |
| Date: | 2009-03-20 15:48:51 |
| Message-ID: | 1237564131.3953.433.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2009-03-20 at 09:33 -0600, Scott Ribe wrote:
> > Hopefully we regard it as a missing feature rather than as a separate
> > definition. We could cluster the index, we just don't, yet.
>
> Wouldn't this require keeping around multiple versions of index pages for
> MVCC?
No, it wouldn't require that.
Just think one index tuple points to more than one heap row. We would
still need to check visibility on the rows returned to ensure MVCC.
Less index pointers, smaller index.
The trick is: How? But that's a secondary issue to getting it on the
TODO list, which is all I'm suggesting at present.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2009-03-20 15:53:18 | Re: What are the benefits of using a clustered index? |
| Previous Message | Tom Lane | 2009-03-20 15:37:07 | Re: Srf function : missing library on PostgreSQL 8.3.6 on Windows? |