| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Grouped Index Tuples / Clustered Indexes |
| Date: | 2007-03-11 11:22:19 |
| Message-ID: | 45F3E66B.2020100@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
>> On Wed, 2007-03-07 at 10:32 +0000, Heikki Linnakangas wrote:
>>> I've been thinking
>>> we should call this feature just Clustered Indexes
>
> So we would have "clustered tables" which are tables whose heap is ordered
> according to an index and separately "clustered indexes" which are indexes
> optimized for such tables?
Yes, that's what I was thinking.
There's a third related term in use as well. When you issue CLUSTER, the
table will be clustered on an index. And that index is then the "index
the table is clustered on". That's a bit cumbersome but that's the
terminology we're using at the moment. Maybe we should to come up with a
new term for that to avoid confusion..
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naz Gassiep | 2007-03-11 15:09:57 | Re: PostgreSQL - 'SKYLINE OF' clause added! |
| Previous Message | Rémi Zara | 2007-03-11 09:59:47 | Re: Why is "osprey" dumping core in REL8_2 branch? |