ALT A screenshot of two pgMustard windows, with an example query plan in each, and an arrow pointing from the old version to the new. Each has a Bitmap Heap Scan highlighted, and the Read Efficiency tip expanded.

ALT A screenshot of pgMustard, focused on a tip that reads: "Row Estimate: out by a factor of 120. The query planner estimated that this operation would produce 283,853 rows per iteration, but it actually produced 2,444 (out by a factor of 120). Bad row estimates can lead to suboptimal query plans. They can often be improved by running ANALYZE on the tables involved, by increasing column statistics, or by allowing Postgres to assess the correlation between columns (using multivariate statistics)."

ALT A chart showing 48% on 17 or 18, 42% on 15 or 16, 10% on 13 or 14, and nobody (admitting to being) on 12 or older

ALT A side my side comparison highlighting mostly how much more succinct a new version of the tip can be. The tip wording of the new version is as follows: This operation wrote out to disk to store temporary data. Disk space used: 282 MB Reducing the size of the operation would make it faster, especially if you can get it to fit into working memory. You can do this by reducing the number of rows, with a LIMIT clause, or reducing the size of each row, by operating on fewer columns. Another option is to increase the memory available, by adjusting work_mem. Learn more about working memory (underlined, as it's a link)

ALT Screenshots of the BUFFERS page before and after, with the following text highlighted: "And from Postgres 18, it is on by default with ANALYZE."

ALT A screenshot of the pgMustard YouTube channel, showing 8 new videos, one per tool. They range from 2 minutes to 10 minutes in length.

ALT A text heavy screenshot with an example response before and after this change. Specifically it is a markdown file, with the two responses in JSON, and the "New response" includes tip titles, tip explanations, and learn-more-links, which have been highlighted.

ALT A screenshot of the docs, reading: Deleting plans If you wish to programmatically delete a saved plan, you can do so by sending a DELETE request to: https://app.pgmustard.com/api/v1/plans/{id} For example, to delete the plan with id b8160762-5870-4ddd-800f-4a0b340d228e, you would send a DELETE request to https://app.pgmustard.com/api/v1/plans/b8160762-5870-4ddd-800f-4a0b340d228e For a successful deletion, you’ll get a 204 response. For a failed deletion, you will either get a 404 response (“Plan not found”) or 403 response (“Only the creator of a plan can delete it”).