Re: Review Request - Upgrade Doc

2025-06-23 Thread Alwin Tang
Hi all, Just wanted to follow up on the recent discussions about the cloudberry 2.0 upgrade. To close the loop, the migration and upgrade documentation has been approved and published. It’s available here: https://cloudberry.apache.org/docs/sys-admin/migration-and-upgrade/ Thanks to @tuhaihe and

Re: [VOTE] Release Apache Cloudberry (Incubating) 2.0.0-rc1

2025-06-23 Thread Dianjin Wang
For issue #1148, one PR needs review and approval: https://github.com/apache/cloudberry/pull/1151. Best, Dianjin Wang On Mon, Jun 9, 2025 at 10:06 AM Ed Espino wrote: > > -1 (binding) — from the Release Manager > > As the release manager for Apache Cloudberry (Incubating) 2.0.0 RC1, I am > casti

[D] [PR] Improve Postgres Binary Performance by Static Linking (PR #1064)

2025-06-23 Thread Xun Gong
Hi all, I would like to share some context regarding PR #1064 : “chore: compile postgres statically to reduce the PLT function call”. Background and Motivation During recent TPC-DS benchmark tests on CloudberryDB, we observed that linking the po

Blog Post: Apache Cloudberry 2.0 Preview

2025-06-23 Thread Dianjin Wang
Hi all, We’re preparing to publish a blog post later this week to introduce and highlight the key features and improvements in the upcoming Apache Cloudberry 2.0 (Incubating) release. As our first release since joining the Apache Incubator, this version brings major updates in codebase cleanup, br

[DISCUSS] Phased plan for renaming “greenplum_*” scripts in Cloudberry

2025-06-23 Thread Dianjin Wang
Hi all, Our ongoing discussion about renaming the filenames `greenplum_path.sh` & `generate-greenplum-path` files (GitHub Issue #1149[1], PR #1156[2]) has revealed important legal and community considerations worth summarizing and discussing before proceeding. ## Background Here’s an updated sum

Re: [DISCUSS] Phased plan for renaming “greenplum_*” scripts in Cloudberry

2025-06-23 Thread Ed Espino
+1 Thanks, Dianjin, for the clear summary and thoughtful proposal. I support the phased approach for the following reasons: - It addresses ASF legal guidance while minimizing disruption to users familiar with the legacy tooling. - The runtime warning and blog post provide transparency and early