PostgreSQL: No More Vacuum, No More Bloat

Re:PostgreSQL: No More Vacuum, No More Bloat by ctippett on Saturday July 15, 2023 @09:28PM (#36742620)

The article makes some convincing arguments and the benchmarks seem to corroborate their performance claims, but I don't understand the dichotomy between this proposed new storage engine (OrioleDB?) and PostgreSQL itself.

Besides the commercial motivations and wanting to profit from the innovations discussed in the article, is there any reason why this needs to be a whole new database marketed as OrioleDB versus contributing these improvements upstream?

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by waplot on Saturday July 15, 2023 @09:57PM (#36742773)

These changes are way too big to integrated into postgresql's engine itself. It fundamentally changes how MVCC is done.

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by fuy on Saturday July 15, 2023 @10:00PM (#36742793)

Alexander Korotkov (OrioleDb author) idea, - based on his Postgres committer experience, I believe, - is that these changes are way too big to be ever accepted upstream, hence separate engine. More info https://www.socallinuxexpo.org/sites/default/files/presentat..., see esp. slides 9-11

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by akorotkov on Saturday July 15, 2023 @10:39PM (#36742992)

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.

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by tarasglek on Sunday July 16, 2023 @02:38AM (#36744250)

Just curious, are you ukrainian?

Never thought I would see a fellow ukrainian rewriting my fav db.

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by tarasglek on Sunday July 16, 2023 @02:44AM (#36744272)

Curious 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

[ Parent | on HN ]

Re:PostgreSQL: No More Vacuum, No More Bloat by orthoxerox on Sunday July 16, 2023 @07:07AM (#36745624)

Are 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.

[ Parent | on HN ]