Re: Fractal tree indexing

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, 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 19:34:02
Message-ID: CAAZKuFYMcOsCFH_+im=dCx1xP8e4heyaGQk-v_JFbEL_0Ly9MQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 13, 2013 at 8:20 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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?

The name in the literature is "Cache Oblivious Lookahead Array", aka
COLA. The authors also are founders of TokuTek, and seemed to have
take pains to ring-fence mentions of the algorithm with reference to
its patent.

Well, at least nobody can blame them for submarine patent action.

--
fdr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-02-13 19:37:44 Re: 9.2.3 crashes during archive recovery
Previous Message Heikki Linnakangas 2013-02-13 19:33:44 Re: 9.2.3 crashes during archive recovery