| From: | Mike Christensen <imaudi(at)comcast(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| 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:26:04 |
| Message-ID: | 49C0237C.1050904@comcast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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..
Mike
Simon Riggs wrote:
> On Tue, 2009-03-17 at 09:16 -0400, Alvaro Herrera wrote:
>
>>> I'm quite sure SQL Server doesn't work this way and I'm not sure
>>>
>> about
>>
>>> Oracle. Can someone enlighten me on the exact benefit of this?
>>>
>> Thanks!!
>>
>> Yeah, they use a completely different definition of "clustered index"
>> from ours.
>>
>
> Hopefully we regard it as a missing feature rather than as a separate
> definition. We could cluster the index, we just don't, yet.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-03-17 22:35:04 | Re: What are the benefits of using a clustered index? |
| Previous Message | benoît carpentier | 2009-03-17 22:23:40 | Re: Benetl, a free ETL tool for files using postgreSQL, is out in version 2.5 ! |