Add Cloudberry Database Support in Yezzey?

[tuhaihe]

Dear Yezzey Dev Team,

I am Dianjin Wang, the Community Manager for the Cloudberry Database [1], a derivative of the Greenplum Database.

As you may know, Greenplum’s source code repository has recently been archived, and it goes closed-source, which raised concerns around global users[2]. Many users are now considering Cloudberry as an open-source alternative to Greenplum and working on the migration from Greenplum to Cloudberry. Cloudberry has a newer Postgres kernel and keeps most of the compatibility with Greenplum.

I'm not sure if Yezzey can add support for Cloudberry like supporting Greenplum. That would greatly benefit both projects and the original Greenplum users.

I would like to explore the possibility of this with your team. Our engineers can provide technical support if you need it.

Please let me know if you’re interested in discussing this further.

[1] https://github.com/cloudberrydb/cloudberrydb
[2] https://github.com/greenplum-db/gpdb-archive

[reshke]

WFM in my branch https://github.com/yezzey-gp/yezzey/commits/v1.8-cbdb/
but this is really-really WIP
also requires https://github.com/yezzey-gp/ygp/tree/yezzey_cbdb_7_1 this branch to actually work

[tuhaihe]

Hi @reshke thanks for your great work! If you need any help on the integration, feel free to ask for help from @my-ship-it. cc @jianlirong

By the way, would you like to join Cloudberry Slack? We can create one focus channel on the work.

[tuhaihe]

Hi @reshke, if the yezzey for Cloudberry works now, feel free to submit a proposal to start a discussion thread about it and call for more community members to help test. Just my thoughts for your information. Thanks!

[reshke]

Hi @reshke, if the yezzey for Cloudberry works now, feel free to submit a proposal to start a discussion thread about it and call for more community members to help test. Just my thoughts for your information. Thanks!

Sure will. My plan is to make yezzey pure extension, compatible with Cloudberry without any kernel patches (which are needed now).

So, firstly I plan to cherry-pick some gpdb patches, to reduce Yezzey-related patches size.
Then, I plan to provide some AO/AOCS extendable SMGR patches, which are clear improvement and non-invasive.
Next step will be portion of more invasive patches, which allocates some system oid for Yezzey internals.

This way, yezzey will be fully compatible with cloudberry, resulting in native AO/AOCS compute/storage separation too l.