Support more robust major version Database upgrade mechanism
As a DevOps Engineer,
I want to be able to do in-place major version upgrade for Postgresql while maintaining ability to rollback to previous version in case there's apps error with the minimal data loss.
So that I can reduce effort for major version upgrade, which currently we need to fork and do logical replication (with other necessary stuff to do) for keeping the data in-sync with the master if we want the ability to rollback.
In addition, we have done the fork and logical replication with ability to rollback to old version while keeping the data in-sync between the forked and master database and it is doable. However since we are using Aiven Managed Database, we'd like to reduce those kind of work from our operational side.