PIGSTY
A practical question is maintainability. All of this work is done by one person. I run a one-person company, and a one-person distribution called Pigsty. I've been doing this for about five years. It's getting easier these days, because of AI tooling. A year ago, every build spec was hand-written. After accumulating enough examples, adding new extensions has become straightforward. Last month I added 50 new extensions in two days. My friend Yurii Rashkovskii once described an idea called PGPM — URL in, RPM out. With Codex and Claude Code, that idea is becoming real. AI also lowers testing cost. We can drive sanity checks from extension documentation and catch behavior regressions earlier. AI may not be ready to commit Postgres core patches. But it's clearly qualified for this kind of work. I maintain a MinIO fork that fixes CVEs and bugs, almost entirely through Codex and Claude Code. It actually works in production. This is the only way a 511-extension matrix stays alive with one maintainer.