| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fractal tree indexing |
| Date: | 2013-02-13 16:20:26 |
| Message-ID: | 19381.1360772426@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> The basic idea of a fractal tree index is to attach a buffer to every
> non-leaf page. On insertion, instead of descending all the way down to
> the correct leaf page, the new tuple is put on the buffer at the root
> page. When that buffer fills up, all the tuples in the buffer are
> cascaded down to the buffers on the next level pages. And recursively,
> whenever a buffer fills up at any level, it's flushed to the next level.
[ scratches head... ] What's "fractal" about that? Or is that just a
content-free marketing name for this technique?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-02-13 16:36:45 | Re: JSON Function Bike Shedding |
| Previous Message | Atri Sharma | 2013-02-13 16:10:25 | Re: Fractal tree indexing |