Hi! Sounds wise. How long are we going to support 2.X and future 3.X branches before migrating all users to rebased to PG16 (4.X?) branch?
If the answer is more than 2-3 years (it seems to me that it is), the answer to upgrade is yes, it would be great to upgrade to PG 14.20 The only objection I can think of is that the EOL for PG14 is this year, November 12, 2026. See https://www.postgresql.org/support/versioning/. But maybe it's not aт objection at all, we could backport the most important CVE's. The stability is more important than a fast switch to a new PG kernel. On Thu, Feb 5, 2026 at 8:50 AM tuhaihe (via GitHub) <[email protected]> wrote: > > GitHub user tuhaihe created a discussion: [Ideas] Upgrade PostgreSQL 14 > base from 14.4 to 14.20 for Cloudberry main branch > > ### Description > > Currently Apache Cloudberry is based on PostgreSQL 14.4. Meanwhile, > PostgreSQL has released multiple minor updates and the latest version in > the 14.x series is 14.20 (released on Nov 11, 2025). > > While the community is working on the major upgrade from PostgreSQL 14 to > PostgreSQL 16 (which is a large and challenging effort), I would like to > propose upgrading the PostgreSQL 14 base version from 14.4 to 14.20 in > Cloudberry main branch. > > This proposal is not intended to replace the PostgreSQL 16 upgrade > roadmap, but to provide an incremental and low-risk improvement path for > users in the meantime. > > ### Use case/motivation > > **Motivation** > > - PostgreSQL 14.20 contains numerous bug fixes, stability improvements, > and security patches compared to 14.4. > - Between 14.4 and 14.20, there are more than 1,000+ (1352) commits, many > of which address correctness and security issues that Cloudberry users may > benefit from. > - Currently, some fixes are being cherry-picked manually, which is helpful > but does not scale well and may miss important patches. > > **Expected Benefits** > > - Provide Cloudberry users with a more secure and stable PostgreSQL 14 > base. > - Reduce the maintenance burden of manually cherry-picking upstream > patches. > - Deliver improvements earlier, without waiting for the PostgreSQL 16 > migration to complete. > - Maintain a relatively low-risk upgrade path, as this is still within the > PostgreSQL 14 major version. > > ### Related issues > > There is ongoing work and discussion about upgrading Cloudberry from > PostgreSQL 14 to PostgreSQL 16. This proposal is complementary and aims to > improve the current PostgreSQL 14-based branch while the major upgrade is > in progress. > > ### Are you willing to submit a PR? > > - [ ] Yes I am willing to submit a PR! > > GitHub link: https://github.com/apache/cloudberry/discussions/1565 > > ---- > This is an automatically sent email for [email protected]. > To unsubscribe, please send an email to: > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
