Re: Fractal tree indexing - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Fractal tree indexing
Date
Msg-id CA+U5nMLUCyChn1BrAwCvE3_qtbwp3fzrhZuCa+ocoaSLqtGjFg@mail.gmail.com
Whole thread Raw
In response to Re: Fractal tree indexing  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Fractal tree indexing  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Fractal tree indexing  (Andrew Borodin <borodin@octonica.com>)
List pgsql-hackers
On 13 February 2013 16:48, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
> On 13.02.2013 18:20, Tom Lane wrote:
>>
>> Heikki Linnakangas<hlinnakangas@vmware.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?
>
>
> I'd call it out as a marketing name. I guess it's fractal in the sense that
> all levels of the tree can hold "leaf tuples" in the buffers; the structure
> looks the same no matter how deep you zoom, like a fractal.. But "Buffered"
> would be more appropriate IMO.

I hope for their sake there is more to it than that. It's hard to see
how buffering can be patented.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Alias hstore's ? to ~ so that it works with JDBC
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Fractal tree indexing