Discussion on "Changing one number from 32 to 34 made a Postgres query 6,000× faster. Here's exactly why."

Payyavula Balanagaraju · 2026-11-01T21:48:53.515Z

Who this is for: anyone who has seen a Postgres query that should be fast but isn't, and EXPLAIN shows a bad plan without saying why. You don't need to know planner internals. Everything is explained

Discussion on "Changing one number from 32 to 34 made a Postgres query 6,000× faster. Here's exactly why." | Hashnode

Search Hashnode

Changing one number from 32 to 34 made a Postgres query 6,000× faster. Here's exactly why.

Responses