Aug 2, 2026 · 17 min · 11 segments
In this episode of Scaling Postgres, we discuss how bad Postgres MVCC is, a startup's survival guide for Postgres, an examination of DBOS, and different ways of performing hybrid searches. To get the…
Creston JamisonHost
This is from boringsql.com, and he says, quote, if you follow people who don't like Postgres, basically they say MVC is bad and call it a 40-year-old design mistake.

And it can cover all the issues I mentioned in the intro, you know, the write amplification, running out of transaction IDs, bloated tables.

But he breaks it down and said, you know, essentially we're asking four questions.

Where do the old versions of the data live? Is it in the table itself or in a separate structure? Which way do version chains point? Is it from old to new or new to old? What do indexes point at? Do they point at the physical row location or a logical key? And then who cleans up what and when? Is it a background process later or is it the transaction itself? Because each of these is a trade-off you have to make.

Because in terms of Postgres, the old versions live in the table, the version chain points from old to new, the indexes point at a physical location, and then...

Now, next he discusses the charges against PostgreSQL, basically the write amplification.

So when you update, say, 100,000 rows touching a non-indexed row, you can see the wall generation but essentially almost double the size when you use an index table, because each of those indexes need to now reference the new physical row.

And the more while you generate, the more checkpoints that have to happen, which leads to more full-page image rights and more bytes shipped to a replica.

There are heap-only tuple updates, or a hot update, But sometimes to get the most benefit out of this, you do have to adjust the fill factor, which again, increases the size of the database tables themselves because you're essentially reserving additional space.

The next charge is your table is an accident scene, which I guess to him means every update is an insert plus a deferred delete by vacuum.

And if you don't have vacuum configured well, basically your dead versions accumulate and it results in a bloated table.

So basically you have issues with long-running transactions that can prevent rows from being cleaned up.


This is from boringsql.com, and he says, quote, if you follow people who don't like Postgres, basically they say MVC is bad and call it a 40-year-old design mistake.

And it can cover all the issues I mentioned in the intro, you know, the write amplification, running out of transaction IDs, bloated tables.

But he breaks it down and said, you know, essentially we're asking four questions.

Where do the old versions of the data live? Is it in the table itself or in a separate structure? Which way do version chains point? Is it from old to new or new to old? What do indexes point at? Do they point at the physical row location or a logical key? And then who cleans up what and when? Is it a background process later or is it the transaction itself? Because each of these is a trade-off you have to make.

Because in terms of Postgres, the old versions live in the table, the version chain points from old to new, the indexes point at a physical location, and then...

Now, next he discusses the charges against PostgreSQL, basically the write amplification.

So when you update, say, 100,000 rows touching a non-indexed row, you can see the wall generation but essentially almost double the size when you use an index table, because each of those indexes need to now reference the new physical row.

And the more while you generate, the more checkpoints that have to happen, which leads to more full-page image rights and more bytes shipped to a replica.

There are heap-only tuple updates, or a hot update, But sometimes to get the most benefit out of this, you do have to adjust the fill factor, which again, increases the size of the database tables themselves because you're essentially reserving additional space.

The next charge is your table is an accident scene, which I guess to him means every update is an insert plus a deferred delete by vacuum.

And if you don't have vacuum configured well, basically your dead versions accumulate and it results in a bloated table.

So basically you have issues with long-running transactions that can prevent rows from being cleaned up.

The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.