3min chapter

Postgres FM cover image

Queues in Postgres

Postgres FM

CHAPTER

How to Improve Throughput With PQ

Skype had the requirement to handle billion users. Declarative partitioning didn't exist at time. They used inheritance based partitioning, three partitions and rotation. So we use one partition, we maintaining another one and third one is like one idle. And maintaining means like we just truncate. Cuncate is fast. I was trying to work out why there are three. Is it that we have one that new rows are going into currently? One where we're trying to finish the final jobs in it just while we're switching between partitions. And then the third one that is always going to be ready for. Honestly, I don't remember. But nowadays we have declarative partition

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