| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Mike Christensen <imaudi(at)comcast(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: What are the benefits of using a clustered index? |
| Date: | 2009-03-17 22:35:04 |
| Message-ID: | 1237329305.3953.131.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2009-03-17 at 15:26 -0700, Mike Christensen wrote:
> I would only like this as a feature if the optimizer can really take
> advantage of this. Clustering on every insert or update just for the
> fun of it won't really give us anything but more expensive writes.
>
> I kinda figured if SQL Server and Oracle have it, they probably take
> full advantage of it for reads..
With SQLServer and Oracle the optimization is implicit in the physical
design of the index. The Postgres equivalent would be a grouped index,
not necessarily clustered in the same way.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-03-17 23:12:32 | Re: Maximum transaction rate |
| Previous Message | Mike Christensen | 2009-03-17 22:26:04 | Re: What are the benefits of using a clustered index? |