14.6 -> 14.7

[reshke]

Cherry-pick postgres/postgres@2e4229691c6 to postgres/postgres@dfb5ad7cf0d

[my-ship-it]

Hi @reshke,

Thanks for opening this issue! Just want to make sure we're on the same page here. 😊

It looks like you're proposing to cherry-pick the range of PostgreSQL commits from 2e4229691c6 (doc fix in 14.6) through dfb5ad7cf0d (14.7 release notes / CVE-2022-41862) into Cloudberry. That's a great idea — keeping up with upstream security and bug fixes is really valuable for the project.

A few things worth noting as context:

• Cloudberry is currently based on PostgreSQL 14.4. So far, the approach has been to selectively cherry-pick individual fixes from later 14.x releases (e.g., the PG 14.5 stats privilege fix in Cherry-pick pg14.5 commit: Fix incorrect permissions-checking code for extended statistics. #1550/Cherry-pick of CVE fix: Fix privilege checks in pg_stats_ext and pg_s… #1551) rather than doing bulk merges.
• A range like 14.6 → 14.7 could include a significant number of commits, some of which may conflict with Cloudberry/Greenplum-specific changes in areas like the planner, executor, or catalog.

It would be really helpful if you could provide a bit more detail on the scope and motivation:

1. Are there specific fixes or CVEs within this range that you're particularly interested in?
2. Would you be interested in contributing this work, or is this more of a feature request for the community to pick up?
3. Have you had a chance to assess potential conflicts with CBDB-specific code?

Would love to discuss further and figure out the best way to approach this. Thanks again for bringing it up! 🙏

[reshke]

Hi @reshke,

Thanks for opening this issue! Just want to make sure we're on the same page here. 😊

It looks like you're proposing to cherry-pick the range of PostgreSQL commits from 2e4229691c6 (doc fix in 14.6) through dfb5ad7cf0d (14.7 release notes / CVE-2022-41862) into Cloudberry. That's a great idea — keeping up with upstream security and bug fixes is really valuable for the project.

A few things worth noting as context:

• Cloudberry is currently based on PostgreSQL 14.4. So far, the approach has been to selectively cherry-pick individual fixes from later 14.x releases (e.g., the PG 14.5 stats privilege fix in Cherry-pick pg14.5 commit: Fix incorrect permissions-checking code for extended statistics. #1550/Cherry-pick of CVE fix: Fix privilege checks in pg_stats_ext and pg_s… #1551) rather than doing bulk merges.
• A range like 14.6 → 14.7 could include a significant number of commits, some of which may conflict with Cloudberry/Greenplum-specific changes in areas like the planner, executor, or catalog.

It would be really helpful if you could provide a bit more detail on the scope and motivation:

1. Are there specific fixes or CVEs within this range that you're particularly interested in?
2. Would you be interested in contributing this work, or is this more of a feature request for the community to pick up?
3. Have you had a chance to assess potential conflicts with CBDB-specific code?

Would love to discuss further and figure out the best way to approach this. Thanks again for bringing it up! 🙏

Hi! This issue is merely a part of Kernel Upgrade: PG 14.4 ~> 14.22, targeting REL_2_STABLE branch of CBDB, which is currently based of 14.6. See #1636 #1621 etc

As for CVE fixes - we have almost all of 14.4-14.20 CVE fixes in main. Few are still in work