citus/src
Colm 83e73716ab PG17 compatibility: fix pg16 to pg17 upgrade (#7788)
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.
2024-12-24 11:44:47 +03:00
..
backend PG17 compatibility: fix pg16 to pg17 upgrade (#7788) 2024-12-24 11:44:47 +03:00
include PG17 Compatibility: Support MERGE features in Citus with clean exceptions (#7781) 2024-12-19 14:02:24 +03:00
test Enable configure and add PG17 CI tests 2024-12-24 11:44:46 +03:00