Repository navigation
Integrate PostgreSQL 19 features to Citus #8782
Copy link
Copy link
Open
4 / 104 of 10 issues completedLabels
pg19_featuresPostgreSQL 19 feature integration work in CitusPostgreSQL 19 feature integration work in Citus
Description
Activity
- addedpg19_featuresPostgreSQL 19 feature integration work in CitusPostgreSQL 19 feature integration work in Citus
on Aug 19, 2026 - added a parent issue
on Aug 19, 2026 - added sub-issues
on Aug 19, 2026 - removed a parent issue
on Aug 19, 2026 ihalatci commented
on Sep 28, 2026 ContributorAuthorMore actionsPostgreSQL 19 Beta 4 alignment is complete on
mainvia #8870 and #8881.Beta 4 feature handoff:
- Reject FOR PORTION OF distributed modifications #8763 is obsolete for Beta 4 because PostgreSQL reverted
FOR PORTION OFsupport. Do not merge it as-is. - PG19: use ShareUpdateExclusiveLock for REPACK CONCURRENTLY #8805 remains relevant because
REPACK CONCURRENTLYremains in PostgreSQL 19 Beta 4. - PG19: contain eager aggregation in join restriction hook #8806 remains queued for separate Beta 4 feature review; it is stacked on PG19: use ShareUpdateExclusiveLock for REPACK CONCURRENTLY #8805.
- PG19: propagate EXPLAIN IO to worker nodes #8807 remains queued for separate Beta 4 feature review; it is stacked on PG19: contain eager aggregation in join restriction hook #8806.
Validation evidence:
- Post-merge Build & Test: https://github.com/citusdata/citus/actions/runs/36406613062
- Post-merge Nightly cassert: https://github.com/citusdata/citus/actions/runs/36406742370
- Both completed successfully on merge commit
b4faf35da326cad31edb36f37cd7d689a6104b01, including all PG19 suites, arbitrary-config shards, and PG17/18-to-PG19 upgrade jobs.
- Reject FOR PORTION OF distributed modifications #8763 is obsolete for Beta 4 because PostgreSQL reverted
Metadata
Metadata
Assignees
Labels
pg19_featuresPostgreSQL 19 feature integration work in CitusPostgreSQL 19 feature integration work in Citus
Umbrella for PostgreSQL 19 feature integration in Citus. Build, compatibility, packaging, and CI stabilization are tracked separately in #8597 and are complete for Beta 4.
PostgreSQL 19 Beta 4 baseline
Beta 4 retained REPACK, JSON COPY, EXPLAIN IO, eager aggregation, constraint enforceability, and asynchronous I/O/read streams. It reverted
FOR PORTION OFand partition MERGE/SPLIT.Compatibility landed through #8870 and #8881. Post-merge validation is green:
Active Beta 4 integration work
main; refresh Beta 4 second-session lock regression; review and merge independentlyALTER CONSTRAINTenforceability guardrailmain; remove closed #8806 ancestry; refresh Beta 4 expected output; reviewCompleted
mainGRANTED BYpropagation merged and present onmain; remaining #8766 work is version-neutral and tracked outside this umbrellaDeferred design
REPACK CONCURRENTLYremains deferred pending a nontransactional placement execution model, per-node admission control, rebalancer exclusion, and explicit partial-failure/retry semanticsRemoved or reclassified after Beta 4
FOR PORTION OFpg_stat_ioalready observes columnar reads and measured AIO benefit did not justify integration; the version-neutral buffer-cache pollution finding is tracked separatelypg19_featureslabel and should land independentlypg19_featureslabel and should be implemented/backported as a general deparser correctness fixCompletion rule
This umbrella is complete when the three active guardrail/adoption PRs are resolved and the deferred REPACK design has an explicit product disposition. Version-neutral bugs and future-major features do not block PostgreSQL 19 feature integration.