lukas.fittl.com
@lukas.fittl.com
Thanks! Some more stabilizing still to be done, but I'm excited about the premise of getting this type of data more widely available. Plan IDs are also a potential building block to improve the plan management story for Postgres.
June 3, 2025 at 8:12 PM
Thanks! And yes, I think that change will finally make effective_io_concurrency live up to its name and expectations :)
May 12, 2025 at 1:13 AM
Hooray for getting it committed! Here is to not finding any (more) odd untested parts of Postgres that want to get in the way ;)
March 31, 2025 at 6:13 AM
Besides the usability going down the more fields we add, I do wonder if there is performance overhead with the internal struct getting bigger and bigger? Probably not significant compared to the query text handling I suppose. It does seem useful to have this tracked though..
March 5, 2025 at 9:52 PM
Looks like that link 404s - I assume you meant to link to www.pgmustard.com/blog/postgre... - and agreed, finding the balance with posts that talk about one's own product is hard when you want to stay fair, but I think you did a good
job :)
Postgres query plan visualization tools - pgMustard
When you’ve got a slow Postgres query, EXPLAIN and its parameters are incredibly useful for working out why. However, the information returned can be difficult (and time-consuming) to interpret, espe...
www.pgmustard.com
March 5, 2025 at 4:43 PM