Content
Updated by Tizian Rößler 14 days ago
**The main goal is to make the update to OpenProject 16.2 as smooth as possible for users, with or without them upgrading their database.**
* on our [postgres 17 upgrade documentation page](https://www.openproject.org/docs/installation-and-operations/misc/migration-to-postgresql17/), for all cases except helm an in-place database upgrade is described/used to upgrade to postgres 17
* this can be relatively confusing and error-prone, so we shall change the worklfow to dump & restore
<br>
**Change the workflow to the following.**
1. backup current OpenProject (e.g. 13) database via `pg_dump` or via the OpenProject UI
2. install a new pg17 database with instructions for
* [x] [ ] ensuring that the new database accepts the same credentials as the old one
* [x] [ ] packager (installing new db via package and making it the default)
* [x] [ ] docker AIO (setting PGVERSION to 17, moving the mounted pgdata folder and re-initialising it)
* [x] [ ] docker compose (changing the tag of the pg container, turn it into a variable that can be changed to 17 via .env)
* [x] [ ] helm (this is already the case but make sure to double check)
3. restore dump to newly installed database
**Test the workflow by installing OpenProject 15 using the default postgres 13 and then upgrade it the current dev (e.g. openproject/openproject:dev for docker) with pg 17 using the new instructions.**
**Additional acceptance criteria**
* show the correct OpenProject version which will be switching to Postgres 17 by default (OP 16.2)
* point out to users that for the time being using an older postgres version is still possible but not recommended
* this requires the use of, e.g., PGVERSION=13 in the case of docker for instance
* point out that users are free to upgrade their databases in place if they so choose for which we won't provide instructions, though
* on our [postgres 17 upgrade documentation page](https://www.openproject.org/docs/installation-and-operations/misc/migration-to-postgresql17/), for all cases except helm an in-place database upgrade is described/used to upgrade to postgres 17
* this can be relatively confusing and error-prone, so we shall change the worklfow to dump & restore
<br>
**Change the workflow to the following.**
1. backup current OpenProject (e.g. 13) database via `pg_dump` or via the OpenProject UI
2. install a new pg17 database with instructions for
* [x]
* [x]
* [x]
* [x]
* [x]
3. restore dump to newly installed database
**Test the workflow by installing OpenProject 15 using the default postgres 13 and then upgrade it the current dev (e.g. openproject/openproject:dev for docker) with pg 17 using the new instructions.**
**Additional acceptance criteria**
* show the correct OpenProject version which will be switching to Postgres 17 by default (OP 16.2)
* point out to users that for the time being using an older postgres version is still possible but not recommended
* this requires the use of, e.g., PGVERSION=13 in the case of docker for instance
* point out that users are free to upgrade their databases in place if they so choose for which we won't provide instructions, though