We are working on a goal to upgrade the PostgreSQL version for our Timescale DB from 13 to 15. Currently, we are trying to fork a service in the TimeScale cloud, which has approximately 94 GB of data, so we can do a PostgreSQL version update in the forked service first to check if everything is working as expected before running the actual upgrade directly on the live service. This process has already been stated in one of the TimeScale documents.
The issue we are facing while forking the service is that, after 3 hours, it is still running and auto-retrying.
Can anyone faced similar problem in the past?
I am also more curious now: what will happen if we get success in the service fork and if we try to upgrade the PostgreSQL version on the forked service that has such a large amount of data?