This is excellent, one of my favorite long-form pieces on agentic engineering - includes several non-obvious ways in which leaning on coding agents can catch you out
Posts by
Thank you to @pganalyze for sponsoring pgconf.dev 2026! 🐘❤️
Sponsors make this conference possible. The venue, the hallway conversations, the community that gathers every year. We couldn't do it without them.
See you in Vancouver! 🇨🇦
New chapter for Agentic Engineering Patterns: I tried to distill key details of how coding agents work under the hood that are most useful to understand in order to use them effectively simonwillison.net/guides/agent...
Your weekend watch is “Postgres New Extension Party: pg_stat_plans” with Lukas Fittl:
www.youtube.com/watch?v=26co...
#PostgreSQL #postgres
PGConf.dev 2026 schedule is live! We have a packed program this year. And we'll continue to add Community Discussion Sessions to Tuesday through April. https://2026.pgconf
The Wikimedia Foundation’s chief technology and product officer explains how she helps manage one of the most visited sites in the world in the age of generative AI.
🎉Early Bird Registration is NOW OPEN for PG DATA 2026!
Early Bird Tickets: Just $30 (first 100 registrations)
Student Early Bird Tickets: Only $20 (first 50 students)
🔗Register now: www.eventzilla.net/e/pg-data-20...
#PGDATA2026 #PostgreSQL #EarlyBird #TechConference
Tracking Plan Shapes with Lukas Fittl of pganalyze
#pgconfeu #postgresql #database #riga
Check out the interview with Platinum sponsor pganalyze just posted at https://2025.pgconf
#postgres #pgconfeu #riga #opensource #database
Tom stamped PG 18. Just a few more days for the official release....
git.postgresql.org/cgit/postgre...
We received reports of a phishing campaign targeting crates.io users. Do not click on links asking to authenticate to protect your account. More information: blog.rust-lang.org/2025/09/12/c...
Reminder: code review is not "to catch mistakes", it is a tool for understanding to limit bus/lottery factor first and foremost. When code is written (if you're lucky) by one human, having the second human abdicate their judgment to the machine is actively harmful to your team's code understanding.
New small blog post
"Measuring SELECT ... FOR UPDATE Latency in #PostgreSQL"
> Are queries slow because they’re waiting to acquire locks, or because they’re taking a long time to find the actual rows? :)
benoittgt.github.io/blog/postgre...
New longform @inkandswitch.com essay! 📜
Malleable Software: Restoring user agency in a world of locked-down apps
by me, @joshuahhh.com, @pvh.ca and @seaofclouds.com
inkandswitch.com/essay/mallea...
It's about why people need agency over their software tools, and how to make that happen.
👁️ Watch Lukas Fittl at #PosetteConf Livestream 1 as he explores best practices for tuning slow Postgres queries. ⁉️
posetteconf.com
lukas.fittl.com
#postgresql #databases #OpenSource #analytics
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.
We’re delighted to announce pganalyze as a Gold sponsor for PGConf NYC 2025!
pganalyze.com
@pganalyze #postgres #conference
Awesome post:
Root Cause Analysis: PostgreSQL MultiXact member exhaustion incidents (May 2025)
metronome.com/blog/root-ca...
Voting for unconference sessions here on Day 4 of #PGConfdev had some predictable winners (e.g. scaling PG development, multithreaded #PostgreSQL) & a few surprises too. And now the collaboration begins!
Live now at #PGConfdev in Montreal Lukas Fittl is on stage, diving into “Tracking plan shapes over time with Plan IDs & a new pg_stat_plans”—discover how core plan‑ID tracking, partition‑aware metrics, and an extensible pg_stat_plans can revolutionize your #PostgreSQL query analy
Thanks! And yes, I think that change will finally make effective_io_concurrency live up to its name and expectations :)
Nice explanation of the asynchronous I/O work that has been happening for Postgres: pganalyze.com/blog/postgre... Also interesting to see poor little effective_io_concurrency become a lot more useful! #postgres #postgresql #planetpg
Our CFP is open through May 25th! But don’t delay, send us your talk proposal today!
2025.pgconf.nyc/callforpapers/
@PostgreSQL #postgres #conference
🚨 The RailsConf 2025 schedule is now LIVE!
This will be the FINAL RailsConf—a landmark event celebrating the past, present, and future of Rails.
See what's in store... 👀 railsconf.org/schedule/
Over the last few weeks I've been incrementally merging infrastructure for AIO into postgres. Just now I finally merged the first actual user of AIO ("streaming reads" now can use AIO).
It's been a long long road. I've been, with a lot of help along the way, working on this since some time in 2019.
Hooray for getting it committed! Here is to not finding any (more) odd untested parts of Postgres that want to get in the way ;)
🎶 "Best practices for tuning #PostgresQL queries" will be presented by Lukas Fittl @PosetteConf 2025 (Livestream 1 on Tue Jun 10th @ 11:00am PDT (UTC-7)). 🐘
Find out more: posetteconf.com/speakers/luk...
#postgres #databases #OpenSource #community
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..