3 ms·

I see that fractal tree indexing was brought up back in 2003 for PG. http://www.postgresql.org/message-id/511B5F12.7060500@vmware.com http://www.postgresql.org

I see that fractal tree indexing was brought up back in 2003 for PG. http://www.postgresql.org/message-id/511B5F12.7060500@vmware.com http://www.postgresql.org/message-id/511B5F12.7060500@vmware... But I don't see any patches. Would love to see something like this developed. Also isn't there cstore_fdw for PG for compression? Although I know there are limitaitons with this, which has prevented me from using it. :(

laurencerowe 11y ago
Further down that thread: > Fractal tree indexes are patented. It is distributed as commercial extension to MySQL. So we can't include it into PostgreSQL core. http://www.postgresql.org/message-id/CAPpHfdtV46zQjp88HR5U3hw-Uw7xYWrVDGgyqOE6NWYKQrtPLA@mail.gmail.com http://www.postgresql.org/message-id/CAPpHfdtV46zQjp88HR5U3h...
- jdc0589 11y ago
  wow... thats pretty depressing
  - rch 11y ago
    It's been a while - patents are designed to expire, and in this area they sometimes actually do.
    - hyperpape 11y ago
      Sometimes? I wasn't aware there were exceptions.
- deciplex 11y ago
  Here's the patent: http://www.google.com/patents/US8185551 http://www.google.com/patents/US8185551 Regarding using the tech in OSS, there is an interesting discussion here: https://www.reddit.com/r/linux/comments/1hn7rg/whats_next_after_btrees_as_in_btrfs_fractal_tree/ https://www.reddit.com/r/linux/comments/1hn7rg/whats_next_af... (see the comment from bradleykuszmaul a little ways down).
esmet 11y ago
It's unrelated work. This is the "fractal tree" in question, open source: https://github.com/Tokutek/ft-index https://github.com/Tokutek/ft-index
ddorian43 11y ago
Column store separates each column into separate file, while this stores the row in the index and does block compression of rows (most high level). Column stores are only good for big reads and big inserts.
- mtanski 11y ago
  sequential (clustered) reads and primary append writes
_delirium 11y ago
Fwiw, the thread you linked is from 2013, not 2003. I don't believe the technique existed in 2003 (or if it did, it wasn't under this name).
leif 11y ago
The TokuDB implementation of Fractal Trees uses a single-process, multi-threaded model, which is incompatible with PostgreSQL's multi-process model. In theory, one could patch TokuDB to be suitable, but this is a ton of work.

laurencerowe 11y ago

Further down that thread: > Fractal tree indexes are patented. It is distributed as commercial extension to MySQL. So we can't include it into PostgreSQL core. http://www.postgresql.org/message-id/CAPpHfdtV46zQjp88HR5U3hw-Uw7xYWrVDGgyqOE6NWYKQrtPLA@mail.gmail.com http://www.postgresql.org/message-id/CAPpHfdtV46zQjp88HR5U3h...

jdc0589 11y ago
wow... thats pretty depressing
- rch 11y ago
  It's been a while - patents are designed to expire, and in this area they sometimes actually do.
  - hyperpape 11y ago
    Sometimes? I wasn't aware there were exceptions.
deciplex 11y ago
Here's the patent: http://www.google.com/patents/US8185551 http://www.google.com/patents/US8185551 Regarding using the tech in OSS, there is an interesting discussion here: https://www.reddit.com/r/linux/comments/1hn7rg/whats_next_after_btrees_as_in_btrfs_fractal_tree/ https://www.reddit.com/r/linux/comments/1hn7rg/whats_next_af... (see the comment from bradleykuszmaul a little ways down).

esmet 11y ago

It's unrelated work. This is the "fractal tree" in question, open source: https://github.com/Tokutek/ft-index https://github.com/Tokutek/ft-index

ddorian43 11y ago

Column store separates each column into separate file, while this stores the row in the index and does block compression of rows (most high level). Column stores are only good for big reads and big inserts.

mtanski 11y ago
sequential (clustered) reads and primary append writes

_delirium 11y ago

Fwiw, the thread you linked is from 2013, not 2003. I don't believe the technique existed in 2003 (or if it did, it wasn't under this name).

leif 11y ago

The TokuDB implementation of Fractal Trees uses a single-process, multi-threaded model, which is incompatible with PostgreSQL's multi-process model. In theory, one could patch TokuDB to be suitable, but this is a ton of work.