Catalog changes between minor releases?

[reshke]

Cloudberry Database version

after this PR #531

recompiling CBDB binaries leads to restart error:

20240820:09:38:31:004650 gpstart:yezzey-bionic:reshke-[INFO]:-Catalog Version of coordinator directory incompatible with binaries
20240820:09:38:31:004650 gpstart:yezzey-bionic:reshke-[ERROR]:-gpstart error: Catalog Versions are incompatible

I want to know the policy for catalog changes in CBDB. How do existing client handle changes like this?

What happened

What you think should happen instead

No response

How to reproduce

gpstop -a -i && gpstart -a

Operating System

any

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[avamingli]

Yes, see #560 (comment)
Another reason is Cherry-pick project.
The catalog is changed even across path versions.
We can't guarantee catalog compatible or binary swap until we are ready for a stable version.
You may need to re-config/re-import data if there were such problems.

[reshke]

Yes, see #560 (comment) Another reason is Cherry-pick project. The catalog is changed even across path versions. We can't guarantee catalog compatible or binary swap until we are ready for a stable version. You may need to re-config/re-import data if there were such problems.

So, releases published in repo are not stable? When we can expect stable version (would in happen in 2025 for example)?
re-importing data is very long process for big deployments. Im thinking of starting support for pg_upgrade for CBDB by myself...

[avamingli]

So, releases published in repo are not stable? When we can expect stable version (would in happen in 2025 for example)?

Not sure, CBDB is iterating fast, there will be many features requiring catalog change.
And we're working on cherry-pick internal codes to CBDB that another round of catalog changes will come soon.

[tuhaihe]

@reshke could you join the community slack channel #cbdb-release-plan via the iniviation link? We're talking about the new release policy here, welcome to have your feedback.