team/docs/main/administration-guide/upgrade/upgrading-postgres.mdx

---
title: "Upgrade PostgreSQL"
---
<PlanAvailability slug="all-commercial" />

Mattermost follows the [PostgreSQL community versioning policy](https://www.postgresql.org/support/versioning/), which provides 5 years of support per major version. When a PostgreSQL version reaches end-of-life, Mattermost drops support for it in a subsequent release. See the [software and hardware requirements](/deployment-guide/software-hardware-requirements) documentation for the currently supported PostgreSQL versions.

When upgrading PostgreSQL, refer to the [official PostgreSQL upgrade documentation](https://www.postgresql.org/docs/current/upgrading.html) for comprehensive guidance. This page covers the steps specific to Mattermost deployments.

## Before you begin

1.  **Back up your database.** Always take a full database backup before upgrading. See the [backup and disaster recovery](/deployment-guide/backup-disaster-recovery) documentation.
2.  **Check supported versions.** Confirm the target PostgreSQL version is supported by your Mattermost release. See [software and hardware requirements](/deployment-guide/software-hardware-requirements).
3.  **Stop Mattermost.** Shut down the Mattermost server before starting the database upgrade to prevent data writes during the process.

## Upgrade a bare-metal PostgreSQL server

There are two main approaches for upgrading PostgreSQL on a bare-metal or virtual machine:

- **pg_upgrade** (in-place): Faster; upgrades the data directory without a full dump/restore cycle. Recommended for large databases.
- **pg_dump / pg_restore** (logical): Simpler and safer for cross-machine migrations or when in-place upgrade is not possible.

### Using pg_upgrade

`pg_upgrade` allows you to upgrade between major PostgreSQL versions without a full export. Both the old and new PostgreSQL versions must be installed side-by-side.

1.  Install the new PostgreSQL version alongside the existing one using your package manager.

2.  Stop the existing PostgreSQL service:

    ``` sh
    sudo systemctl stop postgresql
    ```

3.  Run `pg_upgrade` as the `postgres` user, specifying the binary and data directories for both versions. Replace `<old_version>` and `<new_version>` with the appropriate version numbers (e.g. `15` and `16`):

    ``` sh
    sudo -u postgres /usr/lib/postgresql/<new_version>/bin/pg_upgrade \
      --old-datadir /var/lib/postgresql/<old_version>/main \
      --new-datadir /var/lib/postgresql/<new_version>/main \
      --old-bindir /usr/lib/postgresql/<old_version>/bin \
      --new-bindir /usr/lib/postgresql/<new_version>/bin
    ```

4.  Update your system to start the new PostgreSQL version by default, then start the service:

    ``` sh
    sudo systemctl start postgresql
    ```

For full `pg_upgrade` reference, see the [official pg_upgrade documentation](https://www.postgresql.org/docs/current/pgupgrade.html).

### Using pg_dump and pg_restore

This approach exports the entire database, installs the new PostgreSQL version, and restores the data. It is simpler but requires downtime proportional to database size.

1.  Export the Mattermost database (replace `mattermost` with your database name and `mmuser` with your database user):

    ``` sh
    pg_dump -U mmuser -Fc mattermost > mattermost_backup.dump
    ```

2.  Install the new PostgreSQL version and create the database user and database:

    ``` sh
    sudo -u postgres psql -c "CREATE USER mmuser WITH PASSWORD 'your_password';"
    sudo -u postgres psql -c "CREATE DATABASE mattermost OWNER mmuser;"
    ```

3.  Restore the database into the new PostgreSQL instance:

    ``` sh
    pg_restore -U mmuser -d mattermost mattermost_backup.dump
    ```

## Upgrade PostgreSQL in Docker

<Note>

The steps below are written for the official [Mattermost Docker deployment](https://github.com/mattermost/docker). If you are using a custom Docker setup, adapt the container and volume names accordingly.

</Note>

When running PostgreSQL in Docker, `pg_dump`/`pg_restore` is the recommended upgrade approach. In-place `pg_upgrade` is complex in containers because it requires both old and new binaries in the same container.

1.  Stop the Mattermost container:

    ``` sh
    docker stop mattermost
    ```

2.  Dump the database from the running PostgreSQL container (replace `mattermost`, `mmuser`, and `db` with your database name, user, and container name):

    ``` sh
    docker exec postgres pg_dump -U mmuser -Fc mattermost > mattermost_backup.dump
    ```

3.  Stop the existing PostgreSQL container:

    ``` sh
    docker stop postgres
    ```

4.  Update `POSTGRES_IMAGE_TAG` in your `.env` file to the new version. For example:

    ``` text
    POSTGRES_IMAGE_TAG=16-alpine
    ```

5.  Recreate the PostgreSQL container so the new image tag from `.env` is applied:

    ``` sh
    docker compose up -d --force-recreate postgres
    ```

    <div class="note">

    <div class="title">

    Note

    </div>

    If your volume already contains data from the old major version, PostgreSQL will refuse to start. In that case, create a new named volume for the new container, then restore from the dump in the next step.

    </div>

6.  Recreate the database user and database in the new container, then restore:

    ``` sh
    docker exec -i postgres psql -U postgres -c "CREATE USER mmuser WITH PASSWORD 'your_password';"
    docker exec -i postgres psql -U postgres -c "CREATE DATABASE mattermost OWNER mmuser;"
    docker exec -i postgres pg_restore -U mmuser -d mattermost < mattermost_backup.dump
    ```

## After the upgrade

After upgrading PostgreSQL, run `ANALYZE VERBOSE` on the Mattermost database. This re-populates the `pg_statistic` table used by PostgreSQL to generate optimal query plans. Skipping this step can result in degraded database performance.

``` sh
sudo -u postgres psql -d mattermost -c "ANALYZE VERBOSE;"
```

Once complete, restart Mattermost:

``` sh
sudo systemctl start mattermost
```