Yes, we definitely should have a 2.1 release with all bug fixes and improvements except those related to catalog changes, since the branch associated with the 2.0.0 version is sort of too old.
Best, Lirong Dianjin Wang <[email protected]> 于2025年10月21日周二 15:58写道： > On Mon, Oct 20, 2025 at 11:50 PM Leonid Borchuk <[email protected]> > wrote: > > > > 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 ? > > Yes, the main branch catalog has been changed. The version has been > bumped to 3.0.0 in the main. > > Additionally, I believe that one goal of the 2.1 release is to allow > users to upgrade their 2.0 simply by swapping the binary, without > requiring data migration. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
