From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
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 16:43:24 |
Message-ID: | 511BC2AC.8070202@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02/13/2013 11:20 AM, Tom Lane 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?
>
>
And if that's all it is then I have some doubt about its patentability.
For one thing I'd be mildly surprised if there weren't prior art. But of
course, IANAL :-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-02-13 16:48:36 | Re: Fractal tree indexing |
Previous Message | Andrew Dunstan | 2013-02-13 16:36:45 | Re: JSON Function Bike Shedding |