Amazing that the Postgres ecosystem got this software for “free” (as in at least a basic version of it is F/OSS, IIRC there wasn’t any core bits held back), and the extremely engineer-heavy company got to make money, AND they got bought out in true acquisition style by a larger player that truly benefits from the tech.

The Postgres ecosystem is pretty unique in its ability to produce a “boring” stable product, innovate, stay F/OSS, and create financial outcomes for participants.

I don't follow: read requests are not served from the WAL. They read the current state of the page from the buffer cache, where the page is updated after the change (FPI or not) is written to the WAL.

Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it.

This feels like "JAMStack" from Netlify happening all over again.

I tweeted about this in 2022, as a general trend, and also from the RocksDB meetup emphasizing disaggregated storage:

- https://x.com/GavinRayDev/status/1607769112234823680

- https://x.com/GavinRayDev/status/1600666127025156096

Many people just keep adding data and think "maybe it will be useful in future" till their system goes down.

Many of your data is essentially useless for anything in future.

You can simply have data retention policy and for most app this ensures your data does not grow top huge

[0] https://www.orioledb.com/

[0] https://ducklake.select/

This appears to only have any effect with datalake style installs, where storage is separate from compute.

Not going to have any effect on those small postgres installs for that generic one off app.