| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Csaba Nagy" <nagy(at)ecircle-ag(dot)com> |
| Cc: | "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Including Snapshot Info with Indexes |
| Date: | 2007-10-08 09:17:00 |
| Message-ID: | 4709F58C.4020804@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Csaba Nagy wrote:
> On Mon, 2007-10-08 at 09:40 +0100, Heikki Linnakangas wrote:
>> This idea has been discussed to death many times before. Please search
>> the archives.
>
> Somewhat related to the "visibility in index" thing: would it be
> possible to have a kind of index-table ? We do have here some tables
> which have 2-4 fields, and the combination of them forms the primary key
> of the table. There are usually no other indexes on the table, and the
> net result is that the PK index duplicates the heap. So it would be cool
> if the index would be THE heap somehow...
The clustered index patch I worked on for 8.3, but didn't make it in,
would have helped that use case a lot.
A column-store kind of mechanism would be nice. Some columns could be
stored in index-like structures, while other would be in the heap. I
haven't seen any practical proposal on how to do it though.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-10-08 09:18:52 | Re: Improving the Performance of Full Table Updates |
| Previous Message | Csaba Nagy | 2007-10-08 09:08:17 | Re: Including Snapshot Info with Indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2007-10-08 10:01:27 | Re: Including Snapshot Info with Indexes |
| Previous Message | Csaba Nagy | 2007-10-08 09:08:17 | Re: Including Snapshot Info with Indexes |