Hi! I tried to create cluster for 2.0.0-incubating and then upgrade to current HEAD version and failed.
``` 20251020:14:33:07:194282 gpstart:klg-2flvgt56m5id154r:gpadmin-[INFO]:-Cloudberry Catalog Version: '302509031' 20251020:14:33:07:194282 gpstart:klg-2flvgt56m5id154r:gpadmin-[INFO]:-COORDINATOR_DIRECTORY Catalog Version: '302502091' 20251020:14:33:07:194282 gpstart:klg-2flvgt56m5id154r:gpadmin-[INFO]:-Catalog Version of coordinator directory incompatible with binaries 20251020:14:33:07:194282 gpstart:klg-2flvgt56m5id154r:gpadmin-[ERROR]:-gpstart error: Catalog Versions are incompatible ``` Indeed, ./postgres --catalog-version for 2.0.0-incubating takes us Catalog version number: 302502091 while current HEAD - 302509031 So it's impossible to migrate from 2.0.0 to the current HEAD. Users should create a new cluster and then use cbcopy to move all data. Which is not a minor change. Maybe we should create 2.1 without changes in catalog and then merge all our fixes and release version 3.0 ? WBW, Leonid On Fri, Oct 17, 2025 at 12:36 PM Dianjin Wang <[email protected]> wrote: > Hi, > > On Thu, Oct 16, 2025 at 3:42 PM Ed Espino <[email protected]> wrote: > > > > Since these are separate Apache project repositories, each will require > its > > own release process, including votes and corresponding artifacts. > > Coordinating these component releases alongside or shortly after 2.1.0 > > would help provide a version-aligned ecosystem for downstream users. > > Agreed. Either way, it looks good to me. However, I suggest we > schedule these component releases after version 2.1.0. Currently, > gpbackup requires more testing, and the PXF codebase needs additional > updates. We can prioritize Cloudberry 2.1.0 instead. > > > Happy to help drive discussion around scope, testing, and coordination > for > > these component releases as well. > > Awesome! Glad to see you help drive the upcoming releases. Your > valuable experience will be a great help. I’m also willing to help if > you need support. > > Best, > Dianjin Wang > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
