Beyond Postgres: Insights about the PostgreSQL Extensibility
summary
Explains how PostgreSQL extensions actually get built and deployed, showing an immediate demo that creates a SQL-only extension by dropping control and SQL files into share/extension and a C-based extension compiled with PGXS, installed and invoked successfully. Notes the ecosystem size: contrib bundle ~49 extensions vs PGXN ~430 listings. Points out operational specifics: where files live, pg_available_extensions, ALTER/UPDATE extension commands, cluster-restart needs for some settings, and the maintenance/support risk when upstream projects go inactive.
AI-written summary · about
chapters (11)
- 0:00Introduction and motivation
- 3:15Why Postgres extensions matter
- 7:33Sources and challenges of extensions
- 11:45Demo: Creating SQL and C extensions
- 16:44Managing and updating extensions
- 17:47Challenges in production environments
- 21:18Conclusion and future outlook
- 23:03Q&A: Extension API stability
- 24:09Q&A: Observability limitations
- 26:17Q&A: Makefile confusion
- 26:38Q&A: Server-side application code in extensions
related talks
26mState of the Postgres Extension Ecosystem
42mPostgreSQL Extensions: A Deep Dive
52mAnarchy in the Database: A Survey and Evaluation of Database Management System Extensibility
05mpgextensions org Your Guide to PostgreSQL Extensions Comparision on the Cloud
49mSupporting extensions, but really now
29mPostgres Extensions in Kubernetes
26mCan We Use Rust to Develop Extensions for PostgreSQL?
52mThe trouble with extensions