FileWave Server upgrade paths and PostgreSQL migrations

This article explains how to plan FileWave Server upgrades when the upgrade includes a PostgreSQL database migration. The important rule is not the FileWave version number by itself. The upgrade path has to move through releases that share at least one PostgreSQL version with the release before or after it.

Do not skip the PostgreSQL overlap point.
If the next FileWave release does not support the PostgreSQL version used by your current release, the database migration cannot be completed safely in a single jump.

How the overlap works

Some FileWave Server releases include support for two PostgreSQL versions. Those releases are the bridge between database generations. This does not mean the server runs two production databases at the same time. It means the release includes the pieces needed to migrate from one PostgreSQL version to the next.

The overlap points for the 16.x upgrade path are:

• FileWave 13.3.1 through 14.7.2 include PostgreSQL 12.
• FileWave 16.0.x through 16.2.x include PostgreSQL 12 and PostgreSQL 17.
• FileWave 16.3.x and 16.4.x include PostgreSQL 17 and PostgreSQL 18.

Recommended path

For older servers, use this path:

13.3.1–14.7.2 → 16.0.x–16.2.x → 16.3.x or 16.4.x

This works because each step has PostgreSQL overlap with the next one. The older releases can move into the 16.0.x through 16.2.x range through PostgreSQL 12. From there, FileWave 16.3.x and 16.4.x are reachable through PostgreSQL 17.

Common examples

• If your server is running FileWave 13.3.1 through 14.7.2, upgrade first to a 16.0.x, 16.1.x, or 16.2.x release. Then upgrade to 16.3.x or 16.4.x.
• If your server is already running FileWave 16.0.x, 16.1.x, or 16.2.x, you can upgrade directly to 16.3.x or 16.4.x because both sides overlap on PostgreSQL 17.
• If your server is already running FileWave 16.3.x, you can upgrade to 16.4.x without an additional PostgreSQL staging release because both releases include PostgreSQL 17 and PostgreSQL 18.

Choosing a release inside an overlap range

When several releases are available in the same overlap range, choose the latest available maintenance release unless FileWave Support has given you a different path. For example, a 16.2.x maintenance release is usually a better staging choice than an earlier 16.0.x release, but the PostgreSQL overlap is the same for the 16.0.x through 16.2.x range.

When to contact Support

If your server is older than the versions shown here, or if the server has already had a failed upgrade attempt, contact FileWave Support before continuing. The same applies if you are unsure which PostgreSQL version your current server is using.