Debugging active queries...
summary
A patch logs instrumented EXPLAIN ANALYZE plans mid-flight to a catalog view (pg_explain_activity) at a configurable interval (default track_explain_interval = 10ms), cloning instrumentation state in a temporary memory context to avoid corrupting running queries. Demo prints the plan 2,231 times with ~9ms total logging overhead, and a local single‑page app visualizes per‑node rows and timing in real time. Works only for instrumented executions and requires enabling the track flag; proposed as experimental, not yet upstream.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:01Query analysis challenges
- 11:01Existing troubleshooting features
- 16:59Analyzing running queries
- 26:40Experimental patch demo
- 43:44Patch limitations and Q&A
related talks
52mUnderstanding PostgreSQL Query Plans (aka EXPLAIN)
50mPostgreSQL Query Performance Insights
51mPostgreSQL Query Performance Insights
47mIdentifying Slow Queries and Fixing Them!
18mApparently, you can "debug" your SQL queries
26mBe Good Friends with Query Planner
31mpg_stat_advisor: Optimizing PostgreSQL Planner with Insights
44mDebugging your PL/pgSQL code
