Umbrella issue. Tracks the work to bring Citus up to the latest PG
major.
1. Background
PostgreSQL 19 (currently pg19devel) is the next major. Per Citus'
"three most recent PG majors" support window, the next Citus major must
add PG19 alongside PG17 and PG18 (Citus 14.x: PG16/17/18 → Citus 15.x:
PG17/18/19).
The work splits into three top-level phases:
- Build & runtime correctness — Citus must compile cleanly on
PG19, the extension must load, basic DDL/DML must not crash, and
columnar must operate.
- Regression test parity — the full
make check suite must pass
on PG19 with the same passing tests as on PG17/PG18. This requires
both real fixes (PG19-only crashes that only surface in the regress
harness) and cosmetic / framework adjustments (normalize.sed,
GUCs to pin plan shape).
- Feature integration — opt-in to / interoperate with new PG19
capabilities where doing so makes sense for Citus.
All PRs land on the pg19-support development branch and that branch
is merged to main once the matrix below is green.
2. Sub-tasks
Build & runtime correctness:
Regression test parity:
3. Feature integration
This section will track which PG19 features Citus should adopt or
integrate with (e.g. Eager Aggregation, parallel index build hooks,
changes in EXPLAIN, new TupleDesc cache, the new pg_stat_io knobs,
async I/O, etc.), and which we explicitly choose to disable or ignore.
Verification status
1. Background
PostgreSQL 19 (currently
pg19devel) is the next major. Per Citus'"three most recent PG majors" support window, the next Citus major must
add PG19 alongside PG17 and PG18 (Citus 14.x: PG16/17/18 → Citus 15.x:
PG17/18/19).
The work splits into three top-level phases:
PG19, the extension must load, basic DDL/DML must not crash, and
columnar must operate.
make checksuite must passon PG19 with the same passing tests as on PG17/PG18. This requires
both real fixes (PG19-only crashes that only surface in the regress
harness) and cosmetic / framework adjustments (
normalize.sed,GUCs to pin plan shape).
capabilities where doing so makes sense for Citus.
All PRs land on the
pg19-supportdevelopment branch and that branchis merged to
mainonce the matrix below is green.2. Sub-tasks
Build & runtime correctness:
Regression test parity:
3. Feature integration
This section will track which PG19 features Citus should adopt or
integrate with (e.g. Eager Aggregation, parallel index build hooks,
changes in EXPLAIN, new TupleDesc cache, the new
pg_stat_ioknobs,async I/O, etc.), and which we explicitly choose to disable or ignore.
Verification status