Supporting a New PostgreSQL Version in Your Extension...
summary
Citus follows the Postgres release timeline and works through three concrete steps: make it build, fix failing tests and crashes, then integrate new Postgres features. Practical fixes include adding compat functions for changed function signatures, updating configure scripts, and a specific perm_infos fix that copies permission info into generated PlanStmt to repair the fast-path planner hook. Work tracking shows e.g. 12/175 tests failing during triage; policy is support latest three majors and target full PG17 support by end of 2024.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 1:52Key terms and outline
- 3:19PostgreSQL release schedule
- 8:03Planning extension support
- 12:21Following release timeline
- 18:00Ensuring successful compilation
- 19:47Extension sanity checks
- 29:27Debugging and fixing issues
- 32:43Integrating new PostgreSQL features
- 42:05Progress on Citus for PG17
- 43:08Final strategy recap
- 43:54Q&A session
related talks
39mAdding PG15 Support to Citus Extension
32m8 keys to the growth of Citus & Distributed PostgreSQL
27mHow Do We Get Postgres to the Next Level?
28mBeyond Postgres: Insights about the PostgreSQL Extensibility
19mPostgreSQL Challenges
16mKeynote – Umur Cubukcu
23mFuture Postgres Challenges
08mFoundations of Distributed PostgreSQL with Citus