Conversation
oliverguenther
force-pushed
the
update-postgres-references
branch
from
fb0db32 to
43f91b0
Compare
|
Caution The provided work package version does not match the core version Details:
Please make sure that:
|
| echo "-----> Existing PostgreSQL cluster found in $PGDATA." | ||
|
|
||
| # Check for version mismatch: if Docker default is PG 17 but existing data is PG 13 | ||
| if [ "$PGVERSION" = "17" ] && [ "$EXISTING_PGVERSION" = "13" ]; then |
There was a problem hiding this comment.
@oliverguenther Should we perhaps not make this specific to 17 and 13 but show this warning in general if there is a mismatch between the set PGVERSION and the one found in the cluster?
I know coming from our own setups, this should be the only combination really, but it probably doesn't hurt to catch more potential issues here.
|
@oliverguenther Since we are now using Postgres 17 to generate the schema cache during the docker build, this failed due to missing permissions. I've pushed a commit that fixes that. With that this should look fine. I was wondering if the used postgres version has any bearing on the generated schema cache. But it doesn't seem to be a problem for our containers with the pg13-generated schema cache using more recent versions, so I suppose not. As soon as CI is green this can be merged as far as I'm concerned. |
3 participants
Extended from #19011
Solves this:
Not sure if this line for handling legacy configs could use some change too.
What are you trying to accomplish?
Merge checklist