Hi team, As in-place upgrade would be a preferred option for our cloud clients, I plan to add gpupgrade support from gp6 to cloudberry 2+ for in-place binary upgrades. There are a few bugs that should be fixed in our core code (pg_dump, pg_dumpall, pg_upgrade, etc) and lack of support in gpupgrade itself. For the former I'll be opening PRs shortly to fix some core dumps, add support of resgroup migration, etc. For the latter I wonder if I should move gpupgrade under cloudberry-contrib and rename it to cbupgrade, unless there are any strong objections. In cbupgrade there probably won't be many changes: mostly removal of recovery.conf and proper cloudbery versioning support to prevent version collisions with GP as we've started our versioning from 1 instead of 7 or something and at some point will catch up with GP4 and further.
-- Thank you! Smyatkin Maxim <https://www.linkedin.com/in/smyatkin>
