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.
| Website | https://www.pgmustard.com |
| Status | https://status.pgmustard.com |
pgMustard
@pgmustard
- 26 Followers
- 1 Following
- 40 Posts
A visualisation tool for PostgreSQL explain analyze, that also gives performance advice. Posts by @michristofides
New blog post: Read efficiency issues in Postgres queries
If you've got a query that's slowly degrading in performance over time, you might have a read efficiency issue. The root cause could be table bloat, index bloat, or data locality degradation. In this new post we go through how this can happen, how to mitigate the issue, and the options for preventing it happening again.
https://www.pgmustard.com/blog/read-efficiency-issues-in-postgres-queries
Read efficiency issues in Postgres queries - pgMustard
A lot of the time in database land, our queries are I/O constrained. As such, performance work often involves reducing the number of page reads. Indexes are a prime example, but they don’t solve every issue (a couple of which we’ll now explore).
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: https://www.pgmustard.com/changelog
Michael ChristofidesIf you have any Postgres performance issues, I'd love to hear about them and try to help: https://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.
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?
17 or 18
15 or 16
13 or 14
12 or older
Poll ended at .
