Supporting extensions, but really now
summary
Argues that PostgreSQL’s extension ecosystem is under-resourced and vulnerable, citing concrete numbers: 44% solo maintainers, 58% considered quitting, 22% quit, and ecosystem-wide license forks (Redis, Elastic, OpenTofu) that force forking or new projects. Describes interventions already tried: an extension ecosystem summit, company-backed bounties for two extensions, and Hacktoberfest participation (≈98k contributors on labeled issues) to attract contributors. Recommends governance, shared CI/testing, packaging/branding help, and an annual “State of the Extensions” to measure progress.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker welcome
- 2:26Why Postgres extensions matter
- 7:23Open source funding challenges
- 16:36License changes and corporate conflicts
- 23:21Extension ecosystem struggles
- 26:49Cyber Resilience Act impact
- 30:18Extension developers need recognition
- 33:27Extension ecosystem Summit
- 36:37Community effort for sustainability
- 37:21Q&A and closing discussion
related talks
28mBeyond Postgres: Insights about the PostgreSQL Extensibility
26mState of the Postgres Extension Ecosystem
05mLong Live Sustainability
52mAnarchy in the Database: A Survey and Evaluation of Database Management System Extensibility
54mThe future of the extension ecosystem
27mExtensions Are Dead, Long Live Extensions!
23mConsumption Is Fractal: Open Source...
47mThe Next 20 Years