Add PostgreSQL 18 support#1120
Draft
shirkevich wants to merge 3 commits into
Draft
Conversation
Update the hardcoded version compatibility message to include PostgreSQL 18. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use Citus commit 803f0ac from release-14.0 branch (PG18 support) - Add libnuma-dev dependency required by PostgreSQL 18 Tested: single and multi standby tests pass (189 tests total) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on #1111 and adds one missing PG18 path:
pg_autoctl do tmux composestill rejectedPGVERSION=18because its local Postgres/Citus compatibility matrix stopped at 17.Changes:
803f0ac)PGVERSION=18in the tmux-compose range checkI could not retrieve the old Actions job logs for #1111 because GitHub returned HTTP 410 for the expired job logs, but the failed PG18 check annotations still point at the workflow commands exiting non-zero.