The breakdown and prioritization by estimated time-saving potential is great. We run a multi-service application with several PostgreSQL databases, and as our data has grown, query performance has become more important. As a non-expert in DB optimization, pgMustard has done a great job boiling down the large amount of info Postgres gives you into genuinely useful visualizations.

The smart filtering that collapses fast operations helps a lot—our queries often involve multiple joins across tables, and the tool surfaces what's actually slow. The built-in explanations have also taught the team about PostgreSQL internals, which helps us write smart SQL going forward. Review collected by and hosted on G2.com.

Not much. Since pgMustard is so great at visualizing and annotating slow section of queries I’d be curious if there’s a way to bring it into our codebase more optimistically and scan potentially slow queries during CI/CD or something like that. Basically just more ways to use pgMustard :) Review collected by and hosted on G2.com.