Adding PG15 Support to Citus Extension
summary
Citus gains PostgreSQL 15 compatibility by updating build logic and about a dozen internals, including replacing the removed ValueNode, adapting relation_create_storage signatures, and switching to the new shared-memory request hook. Ruleutils is ported incrementally and hundreds of regression tests catch behavioral breaks; a broken partition-trigger assumption becomes a one-line fix checking parent ID that restores "add node" functionality. Development tracks git betas/RCs, uses release notes and community writeups, and runs daily regression runs after an updated configure script to validate releases.
AI-written summary · about
chapters (10)
- 0:00Introduction and overview
- 2:11What is Citus and why maintain it
- 4:42Methodology for PG-15 support
- 9:13Compiling and fixing structural changes
- 13:54Updating internal logic and tests
- 17:12Tracking new PG-15 features
- 24:05Beta and RC testing process
- 28:24Feature support levels in PG-15
- 33:48Next steps for PG-16 support
- 35:16Q&A session
related talks
52mSupporting a New PostgreSQL Version in Your Extension...
32m8 keys to the growth of Citus & Distributed PostgreSQL
16mKeynote – Umur Cubukcu
28mCitus on Kubernetes
44mDistributed Postgres with Citus
52mA look at the Elephants Trunk - PostgreSQL 15
08mFoundations of Distributed PostgreSQL with Citus
33mCitus & Patroni: The Key to Scalable and Fault-Tolerant PostgreSQL