Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 17.1 images #159

Merged
merged 6 commits into from
Dec 24, 2024
Merged

Add 17.1 images #159

merged 6 commits into from
Dec 24, 2024

Conversation

naisila
Copy link
Member

@naisila naisila commented Jul 23, 2024

PG17: Bison and Flex are now hard build requirements in configure
postgres/postgres@721856f

Sister PR citusdata/citus#7661

@naisila naisila force-pushed the naisila/pg17beta2 branch from 822d697 to 16d4616 Compare July 23, 2024 14:55
@naisila naisila changed the title Add 17beta2 images Add 17.0 images Oct 6, 2024
@naisila naisila changed the title Add 17.0 images Add 17.2 images Dec 5, 2024
@naisila naisila changed the title Add 17.2 images Add 17.1 images Dec 23, 2024
@naisila naisila marked this pull request as ready for review December 24, 2024 09:30
@naisila naisila requested a review from onurctirtir December 24, 2024 09:45
@naisila naisila merged commit 84c0cf8 into master Dec 24, 2024
18 checks passed
@naisila naisila deleted the naisila/pg17beta2 branch December 24, 2024 13:39
naisila added a commit to citusdata/citus that referenced this pull request Dec 24, 2024
This is the final commit that adds
PG17 compatibility with Citus's current capabilities.

You can use Citus community, release-13.0 branch, with PG17.1.

---------

Specifically, this commit:

- Enables PG17 in the configure script.

- Adds PG17 tests to CI using test images that have 17.1

- Fixes an upgrade test: see below for details
In `citus_prepare_upgrade()`, don't drop any_value when upgrading from
PG16+, because PG16+ has its own any_value function. Attempting to do so
results in the error seen in [pg16-pg17
upgrade](https://github.com/citusdata/citus/actions/runs/11768444117/job/32778340003?pr=7661):
```
ERROR:  cannot drop function any_value(anyelement) because it is required by the database system
CONTEXT:  SQL statement "DROP AGGREGATE IF EXISTS pg_catalog.any_value(anyelement)"
```
When 16 becomes the minimum supported Postgres version, the drop
statements can be removed.

---------

Several PG17 Compatibility commits have been merged before this final one.
All these subtasks are done #7653

See the list below:

Compilation PR: #7699
Ruleutils PR: #7725
Sister PR for tests: citusdata/the-process#159

Helpful smaller PRs:
- #7714
- #7726
- #7731
- #7732
- #7733
- #7738
- #7745
- #7747
- #7748
- #7749
- #7752
- #7755
- #7757
- #7759
- #7760
- #7761
- #7762
- #7765
- #7766
- #7768
- #7769
- #7771
- #7774
- #7776
- #7780
- #7781
- #7785
- #7788
- #7793
- #7796

---------

Co-authored-by: Colm <colmmchugh@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants