Intermediate schema changes when upgrade Temporal server

Community Support
1

Hello,

We are planning to upgrade our Temporal server. According to the documentation, this needs to be done sequentially for each minor version, and that patch versions can be skipped, i.e. when upgrading, pick the next minor version at the latest patch.

We’ve come across a version where the latest patch has different schema migrations than an earlier patch on the same minor version. It’s not clear whether we should execute the schema migrations for both, or only the latest.

Fo instance, let’s say we’re currently on 1.23.x (with Postgres persistence) and we’d like to migrate to 1.24.x. 1.24.0 has a schema migration as follows:

  • Core:
    • PostgreSQL schema v1.12
  • Visibility:
    • PostgreSQL schema v1.5

However, 1.24.0 is not the latest patch. Moreover, there’s a warning that 1.24.0 should be skipped due to a bug in SQL visibility:

This release introduces a bug in SQL visibility. Please DO NOT use it if you are using SQL-based (PostgreSQL, MySQL, or sqlite) visibility. Elasticsearch based visibility is not affected. Update directly to v1.24.1.

The next patch, 1.24.1, also has schema migrations:

  • Visibility:
    • PostgreSQL schema v1.6

The patch after that 1.24.2 does not have schema migration, nor does the latest patch 1.24.3.

So if we want to upgrade from 1.23.x to 1.24.3, which schema migrations should we perform?

  1. Schema migration from 1.24.0 → Schema migration from 1.24.1 → DONE
  2. Schema migration from 1.24.1 → DONE
  3. Something else?