Webinar: Postgres Plan Monitoring & Management: Best Practices & Postgres 19
A plan flip is the most common reason a query goes from fast to slow without any code change, but Postgres doesn't normally show you which plan ran and when. We walk through how to make plan history visible with pg_stat_plans and how to influence which plan Postgres picks, including the upcoming pg_plan_advice in Postgres 19.
Lukas Fittl
Founder & CEO, pganalyze
Founder & CEO, pganalyze
In detail, we walk through
- How Postgres 18's Plan ID mechanism lets pg_stat_plans capture which plan runs for every query
- How pg_stat_plans keeps overhead low, and how it compares to auto_explain plan sampling and aurora_stat_plans
- When CREATE STATISTICS or a setting change fixes a bad plan, and when you need to hint instead
- Using pg_hint_plan to influence planner choices, across open-source and cloud-provider implementations
- What the new pg_plan_advice contrib module in Postgres 19 adds, and how it enables plan stability
Watch the Webinar Recording
Hundreds Of Companies Monitor Their Production PostgreSQL Databases With pganalyze
