GitHub user oppenheimer01 added a comment to the discussion: [Proposal] Upgrade the PostgreSQL version from 14 to 16
Hi Ed, Thank you for helping to sort out the remaining issues. Here are my thoughts on these issues ### Release Lifecycle Policy: Unclear - Thanks for making it clearer. It makes sense to have a minimal versioning and support policy for Cloudberry. - This deserves a dedicated discussion thread, so we can gather more input. I’d suggest starting a new thread on the Dev mailing list (or GitHub discussion). Would you like to help initiate this discussion? Thanks! ### Upgrade Path for Users: Not Addressed We plan to upgrade using the same method as we did from Greenplum 7 to Cloudberry, using cbcopy. The upgrade steps are as follows： - Create a new cluster of Cloudberry 3.0 - Cdbcopy from old cluster to new cluster - Remove the old cluster The upgrade path will be discussed as a separate topic and will not be included in this upgrade work. ### Development Workflow and Branching: Needs Clarification - Merge operations are confined to a dedicated branch, ensuring the main branch remains fully operational for ongoing feature development and the 2.0 release cycle. - Following conflict resolution and mitigation of critical PANIC errors in test suites, a CI pipeline will be instantiated on the merge branch. This pipeline initially executes only baseline installcheck-parallel tests, with additional test suites progressively activated during remediation efforts until parity with the main branch's testing framework is achieved. - The merge branch undergoes periodic rebasing against main to maintain synchronization, mirroring standard development practices for seamless future integration. ### Test Plan: Needs Clarification A pipeline including the same test modules as the main branch will be initialized on merge branch. The upgrade should be considered as "complete" when all the tests passed. ### Extension and Component Coordination: Missing The goal of this kernel upgrade is to keep the extensions within the pipeline coverage available. Other in-core extensions will be discussed later. ### Downstream Ecosystem Impact: Private and Commercial Components Kernel upgrades can indeed have a significant impact on non-public extensions or downstream forks. The entire upgrade process will be conducted openly to ensure developers of non-public extensions or downstream forks can adapt their code in a timely manner. The release of new PostgreSQL versions similarly faces the same challenges. A more universal solution would involve maintaining older versions for an extended lifecycle, allowing downstream developers sufficient time to migrate and adapt to newer releases. ### Tracking and Transparency: Suggested A new project has been initialized to track merge progress. https://github.com/orgs/apache/projects/497/views/1 We should work on cbdb-postgres-merge branch in Cloudberry https://github.com/apache/cloudberry/tree/cbdb-postgres-merge GitHub link: https://github.com/apache/cloudberry/discussions/1095#discussioncomment-13192107 ---- 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
