Open tkrzyzelewskiITRS opened 5 months ago
There is a version check using build_scripts/versions.yaml
, with min/max pg versions for each timescaledb release. When we build images we loop through all the combinations of PG_MAJOR from 12..16, with and without ALL_VERSIONS
, and it succeeds for all those cases. What's the build command and environment you're using, and what's the error?
Thanks for pointing me to the versions.yaml. I think the issue was I used 2.15.2 which is not listed there. Regarding the Makefile if statement it sets PG_VERSIONS to PG_MAJOR when ALL_VERSIONS is false. Should there be another check inside else? ifeq ($(ALL_VERSIONS),true) (...) else PG_VERSIONS := $(PG_MAJOR) endif
Testing with ALL_VERSIONS set to true and Timescale version 2.15.1 outputs:
It's definitely listed there in the master branch, but I see that somebody forgot to cut a release for the latest. Test with the master branch, or the latest release please! You could also use the latest builds as well, as they have timescale 2.15.2 already.
https://github.com/timescale/timescaledb-docker-ha/actions/runs/9560527979#summary-26355753602
Could this line of code be fixed to take into account PG_VERSIONS passed in as a parameter? PG_VERSIONS := $(PG_MAJOR)
PostgreSQL 12 is not supported by Timescale 2.12 and higher (https://docs.timescale.com/self-hosted/latest/upgrades/upgrade-pg/). This means Docker fails to build when I set ALL_VERSIONS to true while using new Timescale release. Even when I supply PG_VERSIONS they get set to PG_MAJOR in Makefile. Perhaps there should be another check for supplied PG_VERSIONS or version 12 removed from list when PG_MAJOR is 15 or 16?