Everyone says store money as numeric, not float. Fewer people can say what breaks if you don’t.

Your float SUM changes every run. Same rows, nothing touched, three different totals. That’s floats plus parallel aggregation.

Turn parallelism off and it’s stable. Still wrong.

https://boringsql.com/posts/same-rows-different-sum/

A single NULL turns NOT IN into a query that silently returns zero rows, and the planner couldn't optimize around it for as long as anyone can remember, until a PostgreSQL 19 patch fixed that.

https://boringsql.com/posts/not-in-null/

You trust #postgresql pg_stat_statements bit too much. That might be the problem. It's quietly bending what it reports, and none of it is a bug.

Part 1 - everything it tells you https://boringsql.com/posts/pg-stat-statements/

Part 2 - everything it can't https://boringsql.com/posts/pg-stat-statements-part-2/

boringSQL Live session #2 is now scheduled and we will go deep into and visually understand #postgresql storage internals.

Do you want to understand what bloat looks like? What VACUUM is really doing under the hood? And why it won't always save your indexes? Come find out.

🗓️ Wed, June 10 - 15:30 UTC (timezone specific time on the event page)

https://luma.com/g5bwwqfj

I'm honored for the opportunity to speak at @pgdata2026

🗓️ Thu, June 4, 1:40pm - Room 1 - Visualizing PostgreSQL Storage Internals

And on top of speaking, I now have a series of very interesting talks lined up that I want to attend. Plus I can't wait for all the hallway chats. That's the place where ideas are born. When you see my boringSQL t-shirt, come say hi 🙏