#PostgresMarathon 2-011: Prepared statements and partitioned tables — the paradox, part 3
In #PostgresMarathon 2-009[1] and #PostgresMarathon 2-010[2], we explored why execution 6 causes a lock explosion when building a generic plan for partitioned tables — the planner must lock all 52 relations because it can't prune without parameter values.
Today we'll test what actually happens with different plan_cache_mode settings.
Links
- [1] #PostgresMarathon 2-009 https://postgres.ai/blog/20251028-postgres-marathon-2-009
- [2] #PostgresMarathon 2-010 https://postgres.ai/blog/20251029-postgres-marathon-2-010
