pgMustard

pgMustard Pro now includes 1,000 API credits 🎉 Bulk-analyse plans, plug into your LLM workflows, or build something we haven't thought of yet. Docs: #api" target="_blank" rel="nofollow noopener">pgmustard.com/docs#api

Michael Christofides (@pgMustard): Read efficiency issues in Postgres queries postgr.es/p/7tt

Our Read Efficiency tips are now more efficient to read! 📝 Better wording, mostly for clarity 🔬 More specific to the scan type, and therefore shorter in most cases 🌟 Improved scoring, especially for Bitmap Heap Scans More details: pgmustard.com/changelog

If you have any Postgres performance issues, I'd love to hear about them and try to help: pgmustard.com/office-hours

If pgMustard has made your life easier this year, we'd love a review on G2! It does take a few minutes, but we like that it is verified, and are already using the feedback to shape what we work on next. g2.com/products/pgmus…

Bad row count estimates are a common cause of slow queries. We've had a tip for them in pgMustard from the start, but we've just finished a revamp of it, mostly to make the advice in several common cases clearer. We also now report the ratios a little more naturally.

It was a very small sample size, but we were impressed with the number of people running newer Postgres versions in our recent poll 🙌

We've revamped our "Operation on Disk" tips ✨ * Made them clearer * Made them more succinct (in most cases) * Improved the scoring * Mention hash_mem_multiplier (when relevant) * Show "Operation in Memory" in more cases, with the memory used * Updated the linked blog post

Which major version of PostgreSQL are you (primarily) running in production?

We're in the process of updating our EXPLAIN glossary for Postgres 18. This change was particularly satisfying 🎉

New blog post: "What do the new Index Searches lines in EXPLAIN mean?" In Postgres 18 you'll start seeing things like "Index Searches: 1" on each of your index scans. We looked into what that means, and how it can be helpful. pgmustard.com/blog/what-do-i…

The next chapter in our 7-year battle with EXPLAIN formatting: new demo videos showing how to get nicely formatted query plans in your tool of choice. @pgMustard" target="_blank" rel="nofollow noopener">youtube.com/@pgMustard

We've added more info to our /score endpoint. This includes tips titles, tip explanations, and learn more links — much like you see when using pgMustard manually. The idea is to help folks prioritize better, and resolve issues quickly. Docs: pgmustard.com/docs/score-end…

News: PostgreSQL 18 Released! postgresql.org/about/news/pos…

The upcoming Postgres 18 is set to include some nice improvements to EXPLAIN: * BUFFERS on by default with ANALYZE 🎉 * Fractional "actual rows" (huge in some cases) * Quite a few new fields (including the very cool Index Searches) We've now added support for all of them. 💛

Michael Christofides (@pgMustard): "enable" parameters will work differently in Postgres 18 postgr.es/p/7aE

In case you didn't know, we have an API for saving or scoring query plans via pgMustard. Thanks to a (very reasonable) customer request, we recently added the ability to also delete saved plans via the API

The latest @PostgresFM is a discussion about multi-tenancy architectures — the various tradeoffs of different approaches, including some notes on performance, and a bonus benefit of the isolation model for LLM use cases (spoiler alert: smaller vector indexes)

Correction! The former has been moved to 17:00 UTC

There are a couple of online events today that look like they'll be great: 16:00 UTC — 10 Costly Database Performance Mistakes (and How to Fix Them) with Andy Atkinson meetup.com/postgres-meetu… 19:00 UTC — 12 years of Postgres Weekly with Peter Cooper aka.ms/TalkingPostgre…