Take the guesswork out of PostgreSQL performance

Actionable advice, in plain English, to eliminate slow queries.

The trial includes ten queries, as well as our examples.

You need a fair amount of expertise to understand EXPLAIN ANALYZE output. PostgreSQL includes so much useful information, it can be easy to miss something important. EXPLAIN.D.C and PEV are great for adding a visual layer, but the same issue remains.

What’s the main problem here? Which detail is hiding the clue? Does everybody else just know how to spot it?

You don’t always want to ask for help, especially when time is not on your side…

We spent years making GUI tools for SQL Server, Oracle and MySQL at Redgate. We know that professional developers value tools that reduce mental overhead. Done well, they free up the time, energy, and focus needed to solve the actual problem.

After speaking with a bunch of friendly people (thank you!) we decided to build a product that could help you get from knowing which query is a problem to working out what can be done about it.


“Wow, I wish I had this tool last year when we were battling the Mysterious Minute-Long Query. It was a bad row estimate — this tool would have told us immediately, saving two dev days.”


Based on the query plan, pgMustard offers you tips to make your query faster.

We’ve sweated the details to give you plain english descriptions of operations, performance issues, and what can be done about them. When further reading makes sense, you get links to blog posts by us, or the wider community.

We wanted to make it quick and easy to understand each query plan, while staying focused on your main aim: making it faster.

Ever lost a day or two investigating a red herring? You wouldn’t be the first. Not only does pgMustard suggest what problems to investigate, it also tells you what isn’t an issue. For example, explaining when and why a sequential scan really is the best option.

All of this is presented in a fast (of course) and clear UI, that allows you to quickly hone in on what's important.

Want to see it in action?

The trial includes ten queries, as well as our examples.