7 ms·
I'm seeing OrioleDB as a future engine for PostgreSQL. I'd like to see it as the default engine. However, the changes in OrioleDB are too big to be made increme
by akorotkov 3y ago
I'm seeing OrioleDB as a future engine for PostgreSQL. I'd like to see it as the default engine.
However, the changes in OrioleDB are too big to be made incrementally. This is why I'm comparing the current PostgreSQL engine (with more than just heap, but many other subsystems as well) with OrioleDB.
- tarasglek 3y agoJust curious, are you ukrainian? Never thought I would see a fellow ukrainian rewriting my fav db.
- tarasglek 3y agoCurious if you could share further roadmap. Potential interesting directions: 1. plans for integration with object store ala neon? 2. Columnar? 3. Async-io oriented redesign 4. Interesting new features ala subscriotions to table changes 5. Zero copy client bindings
- orthoxerox 3y agoAre there plans to build flashback-like functionality on top of Oriole DB? Being able to query data "as of xid" would be a great feature.