[BUG] - Upgrade from 2.2.2 to 2.3.1 breaks postgresql

[cghislai]

Describe the bug Postgres fails with:

postgresql 11:04:29.98 INFO  ==> ** Starting PostgreSQL **
2025-09-01 11:04:29.996 GMT [1] FATAL:  database files are incompatible with server
2025-09-01 11:04:29.996 GMT [1] DETAIL:  The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 17.6.

In 2.2.2, the postgres chart is postgresql-11.* from https://charts.bitnami.com/bitnami bitnami chart postgressql 11.9.13 uses postgres image 14.5.0

In 2.3.1, the postgres chart is postgresql-16.7.27 from https://charts.bitnami.com/bitnami bitnami chart postgressql 16.7.27 uses postgres image 17.6.0

To Reproduce Steps to reproduce the behavior (include specific Helm or Kubernetes commands if applicable):

1. Deploy v2.2.2, with postgresl.enabled=true
2. Deploy v2.3.1, keeping postgresl.enabled=true
3. Observe output pasted above in potgres pod

** Workaround **

Before upgrading to the new chart version, lock the postrges image version:

postgresql:
  image:
    tag: 14.5.0

• Consider upgrading to postgres 17 see https://github.com/bitnami/charts/issues/14926#issuecomment-2551470705 for instructions using a dump

Expected behavior mailu minor version upgrades do not cause outage

Environment (please complete the following information):

• Helm Chart Version: 2.3.1

Values.yaml Configuration

## PostgreSQL chart configuration
## for more options see https://github.com/bitnami/charts/tree/master/bitnami/postgresql
postgresql:
  enabled: true
  architecture: standalone
  auth:
    enablePostgresUser: true
    username: mailu
    database: mailu
    existingSecret: "mailu-postgres-secrets"
    secretKeys:
      adminPasswordKey: postgres-password
      userPasswordKey: password
      replicationPasswordKey: replication-password

  primary:
    persistence:
      enabled: true
      size: 8Gi

  ...

**Additional information**
Add any other context about the problem here, such as logs, error messages, or configurations.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[fastlorenzo]

Thank you for your submission, this is indeed an annoying side effect of the recent changes to the chart dependencies due to bitnami's (Broadcom) new policies... We'll try to find a solution in the future for the embedded postgres/redis/mariadb deployments for this chart, in the meanwhile I'll keep your issue opened and pinned in case others encounter this.