| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, heikki(dot)linnakangas(at)enterprisedb(dot)com, "Karl Schnaitter" <karlsch(at)gmail(dot)com>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A thought on Index Organized Tables |
| Date: | 2010-02-24 16:39:20 |
| Message-ID: | 8773.1267029560@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> So you are essentially proposing that rather than moving the heap
> data into the leaf tuples of the index in the index file, you will
> move the leaf index data into the heap tuples? The pages in such a
> IOT heap file would still need to look a lot like index pages, yes?
> I'm not saying it's a bad idea, but I'm curious what benefits you
> see to taking that approach.
Isn't that just a variant on Heikki's "grouped index tuples" idea?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-02-24 16:40:14 | Re: Recent vendor SSL renegotiation patches break PostgreSQL |
| Previous Message | Jaime Casanova | 2010-02-24 16:37:34 | Re: Determining client_encoding from client locale |