| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Decibel! <decibel(at)decibel(dot)org>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Index Tuple Compression Approach? |
| Date: | 2007-08-15 17:41:08 |
| Message-ID: | 1187199668.5203.17.camel@dogma.ljc.laika.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-08-15 at 06:51 +0100, Heikki Linnakangas wrote:
> What Chris is suggesting is basically a special case of GIT, where all
> the heap tuples represented by an index tuple have the same key. I was
> actually thinking of adding a flag to index tuples to indicate that
> special case in GIT. We could effectively do both.
>
The bigger difference that I see is that GIT doesn't just group together
ranges of keys, it also groups by heap page number (or a small range of
page numbers, as Simon pointed out).
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Rylander | 2007-08-15 17:54:46 | Re: Another idea for index-only scans |
| Previous Message | Darcy Buskermolen | 2007-08-15 17:15:37 | Re: XID wraparound and busy databases |