4 ms·
I'm excited about the title, but I have to say that my initial impression has left me frustrated. The main README on GitHub[1] smells of corporate-speak. So far
by mjlawson 3y ago
I'm excited about the title, but I have to say that my initial impression has left me frustrated. The main README on GitHub[1] smells of corporate-speak. So far I've learned that:
- OrioleDB is a new storage engine for PostgreSQL
- PostgreSQL is most-loved (whatever that means)
- OrioleDB is an extension that builds on.. other extensions?
- OrioleDB opens the door to the cloud!
In the wake of crypto and other Web 3.0 grift, this is not the tact that I'd take to release something that extends and improves on something as important as PostgreSQL.
[1] https://github.com/orioledb/orioledb https://github.com/orioledb/orioledb
- newaccount74 3y ago> OrioleDB is an extension that builds on.. other extensions I assume you are referring to this part: > OrioleDB consists of an extension, building on the innovative table access method framework and other standard Postgres extension interfaces. I don't know how they could be more clear? Table access methods were introduced in PostgreSQL to support alternative storage methods (like zheap, which tries to do something very similar, or possibly columnar data stores). Mentioning this fact is important, because there are a bunch of forks of PostgreSQL with alternative data storage systems; this is designed to work as an extension for an unforked PostgreSQL. (It doesn't yet) The Readme seems very clear if you are familiar with PostgreSQL.
- nextaccountic 3y ago> this is designed to work as an extension for an unforked PostgreSQL. That's pretty cool! > (It doesn't yet) What's missing?
- HHad3 3y agoThe PostgresBuild 2021 slides of OrioleDB [1] (also linked in the GitHub project's readme) mention that there is a 1K LoC patch that adds features to the extension interface. I guess the patch is larger by now in 2023. Slide 45 specifically lists: * Extended table AM * Custom toast handlers * Custom row identifiers * Custom error cleanup * Recovery & checkpointer hooks * Snapshot hooks [1] https://www.slideshare.net/AlexanderKorotkov/solving-postgresql-wicked-problems https://www.slideshare.net/AlexanderKorotkov/solving-postgre...