2min chapter

Postgres FM cover image

Queues in Postgres

Postgres FM

CHAPTER

How to Stop a Fire From Happening

It's not a big issue compared to constant pain they feel from degradation related to bloat and that topples. By the way, that happens themselves can be a problem. For example, when you delete and batch, you do everything right but in you have index only scan. And then you start noticing that index only scan, even if it deals with same number of rows, somehow deals with more and more buffers. Why? Because it scans through all those that are all the time. So what can we do instead? We can do like insane, but quite reliable way,. You just put fucking fool to crone. It blocks everyone, but inside the second, you have fresh state.

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode