Hi xanadu-dev, Thank you for testing the 2.0.0 prerelease and for raising this important question.
The behavior you're seeing — a CRC checksum mismatch from pg_controldata after replacing a 1.6.0 installation with 2.0.0 binaries — is expected. Cloudberry 2.0.0 introduces *catalog and control file format changes* that are *not backward-compatible* with 1.x clusters. As a result, a *drop-in binary replacement is not supported between 1.6.0 and 2.0.0*. You’ll need to *export your data from the 1.6.0 cluster and import it into a freshly initialized 2.0.0 cluster*. Tools like pg_dump/pg_restore, gpbackup/gprestore, or our upcoming cbcopy utility (designed to simplify cluster-to-cluster migrations) can help facilitate this. ------------------------------ *Going Forward: Semantic Versioning (SemVer)* Starting with 2.0.0, Cloudberry is officially adopting Semantic Versioning <https://semver.org/> to govern compatibility: - *Patch and minor releases* (e.g., 2.0.1, 2.1.0) will maintain catalog and on-disk format compatibility with earlier 2.x versions. In-place upgrades will be supported without requiring data export/import. - *Major version releases* (e.g., 3.0.0) may introduce breaking changes, such as catalog or storage format updates, and could require initializing a new cluster and migrating data. Any such breaking changes will be clearly communicated in our release notes and documentation. In short: once you're on 2.0.0, *future upgrades within the 2.x series should not require full cluster reinitialization*. We appreciate your early engagement with the 2.0.0 prerelease—please don’t hesitate to reach out with further questions or feedback. Your input is helping shape a better Cloudberry experience for all users. Best regards, -=e On Thu, Jun 19, 2025 at 8:04 AM xanadu-dev (via GitHub) <g...@apache.org> wrote: > > GitHub user xanadu-dev added a comment to the discussion: Upgrade from > Cloudberry 1.6.0 to 2.0.0 > > Would this also been needed for further releases or will everything > maintain compatibility after apache-cloudberry:2.0.0 ? > > GitHub link: > https://github.com/apache/cloudberry/discussions/1175#discussioncomment-13521395 > > ---- > This is an automatically sent email for dev@cloudberry.apache.org. > To unsubscribe, please send an email to: > dev-unsubscr...@cloudberry.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org > For additional commands, e-mail: dev-h...@cloudberry.apache.org > > -- Ed Espino Apache Cloudberry (Incubating) & MADlib
