3 ms·
A couple of months back there was a post from someone who made a presentation about a lot of things that are 'bad' in postgres (mostly performance-wise) and a g
by kabes 4y ago
A couple of months back there was a post from someone who made a presentation about a lot of things that are 'bad' in postgres (mostly performance-wise) and a github repo that tried to fix that (in first instance with patches and the idea was to later have it either upstreamed or as an addon).
I can't find anything of this effort anymore. Does someone know what I'm talking about and what the current status of that is?
EDIT: found it: https://github.com/orioledb/orioledb https://github.com/orioledb/orioledb
I'd love to hear what PG devs here think of his criticism and proposed solutions.
- canadiantim 4y agoYeah I’ve been following orioleDB as well. I think the guys behind it are also going to be offering a managed version of it too. I fully intend to use it in my next project.
- fuy 4y agoAgree with you - would love to hear some of the core PG devs to pay attention and discuss this work.
- ConnorLeet 4y agoI think that this repo was created by a core PG dev. https://github.com/orioledb/orioledb/commits?author=akorotkov https://github.com/orioledb/orioledb/commits?author=akorotko... https://github.com/akorotkov https://github.com/akorotkov
- fuy 4y agothat's the point - my understanding is that he created it as a result of reluctance of core pg team to make progress on these more low level and fundamental problems. I'd be interested to know what core pg people think of it - whether it's just too costly to implement these enhancements in pg, or they think these are just not desirable/correct per se.