Hi Maxim, Thanks for driving this forward — this would be valuable for Cloudberry adoption.
Putting this under `cloudberry-contrib` sounds good to me. I assume you should have permissions to create a new repository there; if not, feel free to reach out and I’m happy to help get that set up. One question I want to get your confirmation: Is your work based on `greenplum-db/gpupgrade-archive`? >From a quick look, it seems to be under Apache License 2.0. Would there be any interest in eventually hosting this under the Apache GitHub org (for example, something like `apache/cloudberry-upgrade`), rather than keeping it as a contrib-style project? Looking ahead, this could also potentially support future upgrade paths, such as Cloudberry 2.x ~> 3.x, especially if we move to a PG16-based 3.x release. FYI. Best, Dianjin Wang On Tue, Apr 7, 2026 at 5:19 PM Maxim Smyatkin <[email protected]> wrote: > > 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> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
