|
|
|
|
|
by akorotkov
1062 days 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. |
|
2. Columnar?
3. Async-io oriented redesign
4. Interesting new features ala subscriotions to table changes
5. Zero copy client bindings