The Go team has published A new Go API for JSON, announcing that the encoding/json/v2 and encoding/json/jsontext packages are stable as of Go 1.27. It’s the first time Go’s standard library ships a version 2 …
A couple of days ago I wrote that Postgres 19 is late and that three big features were dropped along the way. Fortunately, among what does make it there’s something many people who run Postgres have been waiting …
DELETE has a bad reputation in Postgres. Many performance-sensitive systems avoid deleting rows and prefer to empty whole tables with TRUNCATE or drop entire partitions by date. Peter Kraft and Qian Li, from DBOS, have …
The Go blog has published Better HTTP/1 connection reuse, a short post explaining a Go 1.27 change that looks small but can make many programs noticeably faster without touching a line. It starts with this function: func …
This blog has been hosted on Netlify since 2019, although only as static HTML: Hugo generates the pages and Netlify serves them, with no functions or anything running on the server. Even so, the latest article on their …
Anyone who has taken Postgres to production under some load has been through the same thing: you put PgBouncer or PgCat in front, configure transaction pooling, cap the real server connections so it doesn’t run out …
After several days writing about agents escaping their sandboxes, I felt like coming back to something more down to earth. And the GitHub team has just published exactly the kind of article I like reading on a Sunday: …
Every query starts with a plan. Every slow query probably starts with a bad one. And more often than not, the statistics are to blame. But how does it really work? PostgreSQL doesn’t run the query to find out — it …
Lately I’ve been working quite a bit with DuckDB, and one of the things that interests me most is understanding how to optimize performance according to the file format we’re using. It’s not the same …
