3min chapter

Postgres FM cover image

Read-only considerations

Postgres FM

CHAPTER

Index Only Scans for Critical Queries

There's a couple of other things in terms of queries that you can do to favor index only scan. Just checking that you do need all columns that are being requested. So I would fight hard to have single index only scan in most critical queries. In this case, I know this is the best performance pause was kind of kind of give me. But then my question is what's the state or your of your buffer pool and the file cache? Is it good? Because you started to keep the same data multiple multiple times, like many times, the same records,. basically, you have denormalized the situation. And probably you need more memory to keep because you have more pages. It

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