I think that, as Committers, we can directly push changes to the work branch. Given the fast-iteration nature of the kernel upgrade work, following a traditional `Review then Commit` workflow would slow things down quite a bit.
If any issue is found later, we can always revert or fix the changes promptly, so direct commits should be fine for this phase. Best, Dianjin Wang On Sat, Dec 6, 2025 at 9:30 AM Lirong Jian <[email protected]> wrote: > > In my opinion, PostgreSQL kernel upgrades are a critically important > feature, and anyone's contributions are both welcome and > necessary—particularly for verifying, after the code merge is complete, > that each key PostgreSQL 16 feature (compared to PostgreSQL 14) has truly > been implemented and incorporated into Cloudberry in the correct manner. > > Lirong > > > Kirill Reshke <[email protected]> 于2025年12月6日周六 00:50写道： > > > Hi again. > > I did quick pass over several commits in rebase branch, and created some PR > > about issues I did find. There are a lot more issue, and given complexity > > of rebase process, this is completely OK. Rebases usually takes enormous > > amount of time and effort from many people. > > > > I think, this will be a very noisy for community, if I will make one PR > > per my fix. Not to mention I prefer doing small atomic changes, so PRs will > > be frequent. > > > > I propose a scheme, where I will push my changes to rebase branch directly > > (without any review). If any issue with my patch, I will instantly revert > > and re-propose using standard process. > > > > I also want to mention that I do not have a whole lot of time for this, so > > input from me would not be that much, so I don't think my commits will be > > in conflict with others.... > > > > > > WDYT? Also, do you really need contributions from me in this area? > > > > > > Best regards, > > Kirill Reshke > > > > On Fri, 5 Dec 2025, 19:06 Dianjin Wang, <[email protected]> wrote: > > > > > Great job! > > > > > > > > > Best, > > > Dianjin Wang > > > > > > On Fri, Dec 5, 2025 at 11:58 AM Jinbao Chen <[email protected]> > > > wrote: > > > > > > > > Hi all, > > > > I would like to share a new update on our ongoing PostgreSQL kernel > > > upgrade > > > > effort for Apache Cloudberry. Over the past 2 months, we have made > > steady > > > > progress and successfully completed several key phases of the > > > integration. > > > > Here is the latest status: > > > > ~> Merge New Kernel into Work Branch (Done) > > > > ~> Resolve Conflicts (Done) > > > > ~> Fix Compile Errors (Done) > > > > ~> Init Database (Done) > > > > ~> Start the cluster (Done) > > > > ~> Pass the Postgres parallel schedule tests (Done) > > > > ～> Pass the Cloudberry schedule tests (Will start) > > > > At this stage, most of the core enablement work for PostgreSQL 16.9 has > > > > been completed. Next, we will start to try to pass the Cloudberry > > > schedule > > > > tests. > > > > You can track our latest progress here: > > > > - Work Branch: > > > https://github.com/apache/cloudberry/tree/cbdb-postgres-merge > > > > - GitHub Project: https://github.com/orgs/apache/projects/497 > > > > Hope we can achive the milestone earlier! Thanks again! > > > > > > > > Best, > > > > Jinbao > > > > > > > > On Fri, Sep 19, 2025 at 3:42 PM Jinbao Chen <[email protected]> > > > > wrote: > > > > > > > > > Hi team, > > > > > I wanted to provide an update on our PostgreSQL kernel upgrade > > progress > > > > > for Apache Cloudberry. We've made significant progress across > > multiple > > > > > phases of this complex integration. > > > > > Now the first phases have been done: > > > > > ~> ~Merge New Kernel into Work Branch (Done) > > > > > ~> Resolve Conflicts (Done) > > > > > ~> Fix Compile Errors (WIP) (~20% complete) > > > > > - We are currently working through compilation issues that emerged > > from > > > > > the kernel integration. This phase focuses on ensuring all PostgreSQL > > > > > kernel changes are properly integrated with Cloudberry's codebase. > > > Progress > > > > > is steady at 20%~ completion. > > > > > Thanks to all community developers participating in this kernel > > upgrade > > > > > effort! > > > > > You can track our latest progress at: > > > > > - Work Branch: > > > > > https://github.com/apache/cloudberry/tree/cbdb-postgres-merge > > > > > - GitHub Project: https://github.com/orgs/apache/projects/497 > > > > > > > > > > Best, > > > > > Jinbao > > > > > > > > > > On Fri, Aug 1, 2025 at 2:33 PM Lirong Jian <[email protected]> > > > wrote: > > > > > > > > > >> Thanks a lot for the update, Dianjin. > > > > >> > > > > >> Wow, this is a major progress regarding upgrading Cloudberry's > > > PostgreSQL > > > > >> kernel. We've taken a big step closer to our goal of continuously > > > > >> approaching the latest stable version of PostgreSQL. > > > > >> > > > > >> Best, > > > > >> Lirong > > > > >> > > > > >> > > > > >> Dianjin Wang <[email protected]> 于2025年8月1日周五 13:53写道： > > > > >> > > > > >> > Hi all, > > > > >> > > > > > >> > I would like to share an update on the ongoing effort to upgrade > > the > > > > >> > Cloudberry kernel from PostgreSQL 14.4 to 16.9. This work is being > > > > >> > tracked per the proposal discussed in GitHub Discussion #1095. > > > > >> > > > > > >> > ## Overall Progress > > > > >> > > > > > >> > For the kernel upgrade, we will have a few major milestones, > > > including: > > > > >> > > > > > >> > ``` > > > > >> > -> Merge new Kernel into work branch (Done) > > > > >> > -> Resolve conflicts (WIP) > > > > >> > -> Fix the compile errors > > > > >> > -> Init database > > > > >> > -> Check the new pgstat codes and make it work on MPP > > > > >> > -> Pass the PG parallel schedule tests > > > > >> > -> Pass the Cloudberry schedule tests > > > > >> > -> Fix the extensions > > > > >> > -> Enable ORCA > > > > >> > -> Tests and validation > > > > >> > -> Create a PR to push the changes to the main branch > > > > >> > ``` > > > > >> > > > > > >> > The upgrade work began with commit > > > > >> > [0959648e]( > > > > >> > > > > > >> > > > > > https://github.com/apache/cloudberry/commit/0959648e12a6db95fd370b5584a170937bde3ab7 > > > > >> > ), > > > > >> > which merged PostgreSQL 16.9 into our work branch > > > > >> > `cbdb-postgres-merge` on June 1, 2025. Since then, we have been > > > > >> > resolving conflicts after merging the new kernel. > > > > >> > > > > > >> > As of the current HEAD commit, we have successfully processed 50~ > > > > >> > commits that address conflicts and compatibility issues. All of > > > these > > > > >> > commits focus on resolving merge conflicts across the subsystems > > of > > > > >> > the database engine. You can see the progress in issue #1232 - > > 93%~ > > > > >> > conflicts have been resolved. > > > > >> > > > > > >> > ## Next Steps > > > > >> > > > > > >> > We will continue to resolve the conflicts across the whole repo. > > > Once > > > > >> > all conflicts are resolved, we will start to fix the compile > > errors. > > > > >> > > > > > >> > I will share the updates monthly. If any questions, welcome to > > reply > > > > >> > to this thread. Also, you can follow the work branch > > > > >> > `cbdb-postgres-merge` and the GitHub project to catch up on the > > > latest > > > > >> > progress. > > > > >> > > > > > >> > Thanks to the community developer @Jinbao for driving this great > > > work! > > > > >> > > > > > >> > - Work Branch: > > > > >> > https://github.com/apache/cloudberry/tree/cbdb-postgres-merge > > > > >> > - GitHub Project: https://github.com/orgs/apache/projects/497 > > > > >> > - Issue for resolving conflicts: > > > > >> > https://github.com/apache/cloudberry/issues/1232 > > > > >> > - Proposal #1095: > > > https://github.com/apache/cloudberry/discussions/1095 > > > > >> > > > > > >> > Best, > > > > >> > Dianjin Wang > > > > >> > > > > > >> > > > > --------------------------------------------------------------------- > > > > >> > To unsubscribe, e-mail: [email protected] > > > > >> > For additional commands, e-mail: [email protected] > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
