Hello! I really like pg_stat_statements, then you can look into your queries by all sorts of metrics (eg for read heavy workloads, ordering by total_exec_time is a good starting point). Then I like to run EXPLAIN (ANALYZE, BUFFERS, etc) on the worst offender(s) to look for optimizations

I'm a bit out of date on the SQL Server side of things, but with Postgres have you already tried turning on track_io_timing and using more of the EXPLAIN parameters?

For example:

set track_io_timing = on;
explain (analyze, buffers, verbose, settings, wal) ...

Congrats Jimmy!

Is min short for minimum, or minutes?!!

Well I really like your framing, and other AI techniques like ML seem to mostly have almost the opposite characteristics (can get better than even the most specialised humans, but only at very narrow/highly constrained tasks!)

Very nicely put! It only strengthens your point, but I don’t think chess is even a counter example (other AI techniques sure, just not LLMs)

I actually didn’t, but enjoyed learning it from @raae.dev in the follow up blog post! 🥳