This is an interesting read. Part compressed storage, part columnar storage, part column-family storage, part IOT storage. It is already faster for some queries and yet doesn't have planner support. Up next... Julienne Fries!https://twitter.com/AndresFreundTec/status/1115414115340574720 …
-
-
Replying to @robtreat2
Don't think this really qualifies as IOT? Sure it stores using an index, but it's not a usable key (i.e. the primary key or a candidate key). It's not like you can get any useful ordering out of it? Nor does tableam currently really allow that, due to size limitations of TIDs.
1 reply 1 retweet 0 likes -
Replying to @AndresFreundTec
Heh, yeah, I understand that, but it was one of the first things that came to mind reading about btree oriented setup :-) On a side note, I think someone may try to wedge some kind of IOT into the current system even though it lacks support, as that’s been a long standing request
1 reply 0 retweets 1 like
Probably :) And it'd probably be good too - I really would like to get those limitations fixed. It'd be a lot of the same things that'd need to be fixed for global indexes too.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.