Pushing boundaries with extensions, for extension
summary
Postgres extension limits are measured and patched: minor-version ABI changes break extensions, so an experiment warns on minor mismatches; native library reference updates are auto-fixed during alter extension to avoid stale symbols; dependency graphs and bulk installs run via Omni manifest; file-abstracting delivery and auto Python dependency provisioning use Omni VFS and Omni python; hook handling switches to a linear, transactional model and background workers start after commit using an atomic switchboard; the system proves usable (Omni powers hot reloads and reduced latency in practice).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:55What is Postgres API
- 7:27Types of extensions
- 13:49Managing migrations
- 23:21Background workers
- 26:54Hooks in Postgres
- 35:21Reflections on extensions
- 56:07Q&A
related talks
52mThe trouble with extensions
28mBeyond Postgres: Insights about the PostgreSQL Extensibility
47mWhat does it take to onboard an extension?
49mSupporting extensions, but really now
42mPostgreSQL Extensions: A Deep Dive
26mState of the Postgres Extension Ecosystem
27mEating an Elephant Converting PostgreSQL extensions to MySQL
30mDriving Innovation in MySQL with Extensions