Declared postgres visibility-schema-version does not match the actual version
Description
The currently declared version of the postgres-visibility database mismatches with the actual version.
The schema-version is declared as: https://github.com/cadence-workflow/cadence/blob/3410187d214d4b6bc19fd74e34b8cb11d112f93c/schema/postgres/version.go#L29-L31
However the actual visibility db contains migrations up to 0.9: https://github.com/cadence-workflow/cadence/tree/v1.4.1/schema/postgres/visibility/versioned
This doesn't seem to be an issue when running cadence as-is, but when running through the cadence helm-chart: https://github.com/cadence-workflow/cadence-charts there is a wait-for-schema init-container that check the schema/postgres/version.go file for the visibility version and ensures the current schema is the same (https://github.com/cadence-workflow/cadence-charts/issues/93).
Steps to Reproduce / How to Trigger
Try to run cadence with the helm-chart using the postgres database.
Expected Behavior
The pods starts normally.
Actual Behavior
All the pods waits forever on the init-container as schema-version mismatches.
Logs / Screenshots
Relevant logs, stack traces, workflow history, or screenshots.
Environment
- Cadence server version: 1.4.1
- Cadence SDK language and version (if applicable): -
- Cadence web version (if applicable): -
- DB & version: Postgres 17
- Scale: -
Source: cadence-workflow/cadence