You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been upgrading spilo image from 3.3-p3 to 4.0-p2 and also postgres from 16 to 17.
I upgraded postgres-operator from 1.12.0 to 1.14.0 and after that i update the spilo image from 3.3-p3 to 4.0-p2 without upgrading PG Version(16) but Time Scale DB won't work as with 3.3-p3 highest Time Scale DB version was 1.14.2 but with 4.0-p2, Time Scale DB version is 1.19.
So obviously, the operator is not able to find Time Scale DB version 1.14.2 with new spilo image and also not able to upgrade to version 1.19.0. This just makes existing TimeScale DBs froze and they do not work. can't connect to it.
I am planning to install TimeScaleDB version 1.19.0 explicitly to spilo 3.0-p3 pos and then try upgrading it to 4.0-p2 and then to Postgres 17.
Suggest if that's a good workaround or is there another way to do this?
Thanks,
Pramod
The text was updated successfully, but these errors were encountered:
I upgraded TimeScaleDB version to 1.19 and also updated the timescaleDB database version to 1.19.0. Then i started upgrading postgres version from 16 to 17. The non TimescaleDB databases go well in recreating all the databases butTimeScaleDBs fail.
Because of that even postgres upgrade also fails.
I received a generic error in log which says
ERROR: function with OID 20226 does not exist
when converting TimeScaleDB database even though the timescaledb database does not need to be recreated as i already upgraded the version to 1.19.0.
Hi Team,
I have been upgrading spilo image from 3.3-p3 to 4.0-p2 and also postgres from 16 to 17.
I upgraded postgres-operator from 1.12.0 to 1.14.0 and after that i update the spilo image from 3.3-p3 to 4.0-p2 without upgrading PG Version(16) but Time Scale DB won't work as with 3.3-p3 highest Time Scale DB version was 1.14.2 but with 4.0-p2, Time Scale DB version is 1.19.
So obviously, the operator is not able to find Time Scale DB version 1.14.2 with new spilo image and also not able to upgrade to version 1.19.0. This just makes existing TimeScale DBs froze and they do not work. can't connect to it.
I am planning to install TimeScaleDB version 1.19.0 explicitly to spilo 3.0-p3 pos and then try upgrading it to 4.0-p2 and then to Postgres 17.
Suggest if that's a good workaround or is there another way to do this?
Thanks,
Pramod
The text was updated successfully, but these errors were encountered: