Blog - pgMustard

Last updated: February 16, 2026 A lot of the time in database land, our queries are I/O constrained.

Cover photo credit: Diogo Nunes (nature draws indexes pretty well, huh?)

Photo by Elnaz Asadi Each year I go through the changes and additions to EXPLAIN in the upcoming PostgreSQL major version, to see what we need to add support for in pgMustard.

Cover photo by Luca Upper I recently saw a feature request for pg_stat_statements to be able to track percentile performance of queries, for example the p95 (95th percentile) or p99 (99th percentile).

When you’ve got a slow Postgres query, EXPLAIN and its parameters are incredibly useful for working out why.

Cover photo by Mayukh Karmakar An issue I often see folks missing when reviewing query plans, is that all of their scans involve indexes, so they think that the query is likely already as fast (or efficient) as it can be.

Photo credit: Kenrick Mills From time to time I need to check whether a managed Postgres provider supports auto_explain, and if so, which auto_explain parameters they support.

Photo from PGDay UK 2023, credit: Jimmy Angelakos This month’s PGSQL Phriday topic, proposed by Pavlo Golub, is Postgres Events.

This month’s PGSQL Phriday invitation from Tomasz Gintowt is on the topic of “Partitioning vs sharding in PostgreSQL“.

This month’s PGSQL Phriday topic is “database change management”, proposed by Dian Fay.

A couple of weeks ago, I invited folks to blog about pg_stat_statements, as I was hosting the eighth monthly PGSQL Phriday.

As my entry for PGSQL Phriday #008, I want to give some example queries you can use with pg_stat_statements as a starting point for different challenges!

I’m proud to be the host of this month’s PGSQL Phriday event, the eighth so far.

This month’s PGSQL Phriday topic is triggers, proposed by the mighty Lætitia Avrot.

Cover photo: Paul Teysen The PGSQL Phriday topic this month is non-relational data, proposed by the excellent Ryan Lambert of Rustproof Labs.

When doing query optimization work, it is natural to focus on timing data.

Over the past few years, like many of us, I’ve gotten pretty into podcasts.

Cover photo: Clark Young We all know that indexing is important, but it can be difficult to know where to start.

Cover photo: Emily Morter If you spend any amount of time working with Postgres, it’s likely that at some point you’re going to wonder why it is not using an index that you think it should be.

Cover photo: Avinash Kumar From time to time someone asks us where the name pgMustard came from, so I thought it might be fun to share more widely.