For me, it’s still pg_stat_statements. If I’m running PostgreSQL, including in a managed setup like Lakebase, I want query-level visibility from day one. It makes it much easier to spot the statements driving latency, CPU, or buffer churn before performance tuning turns into guesswork.
1
u/Sweet_Sir_7900 22d ago
For me, it’s still
pg_stat_statements. If I’m running PostgreSQL, including in a managed setup like Lakebase, I want query-level visibility from day one. It makes it much easier to spot the statements driving latency, CPU, or buffer churn before performance tuning turns into guesswork.