To close, extensions are the collective treasure of the Postgres ecosystem. I hope this work helps users, authors, vendors, and Postgres hackers build a better Postgres. I want to leave this room with three questions: First โ€” what catalog metrics would actually be useful? Pageviews, downloads, package availability, build failures, last release date, object conflicts. Which of these should be visible, and which are noise? Second โ€” can extension build coverage help patch review? Is it useful as an early warning signal for API, ABI, and behavior changes? Third โ€” should some of this metadata live closer to PostgreSQL community infrastructure? Under postgresql.org, alongside PGDG, or somewhere else? Extensions are collective infrastructure. Delivery is part of extensibility. If we improve delivery, PostgreSQL's superpower reaches more people.

Part IV Maintenance in the Wild

Three Questions

PIGSTY

1What metrics matter?

2Useful for patch review?

3Closer to Postgres Infra?