The crunchy-upgrade container contains multiple versions of PostgreSQL in order
to perform a
pg_upgrade between major versions of PostgreSQL. This includes
the following combinations:
- PostgreSQL 9.5 / PostgreSQL 9.6
- PostgreSQL 9.6 / PostgreSQL 10
- PostgreSQL 10 / PostgreSQL 11
- PostgreSQL 11 / PostgreSQL 12
- PostgreSQL 12 / PostgreSQL 13
The following features are supported by the crunchy-upgrade container:
- Supports a pg_upgrade of the PostgreSQL database.
- Doesn’t alter the old database files.
- Creates the new database directory.
- Does not currently support a PostGIS upgrade.
- Supports upgrades from:
- 9.5 to 9.6
- 9.6 to 10
- 10 to 11
- 11 to 12
- 12 to 13
The crunchy-upgrade Docker image contains the following packages (versions vary depending on PostgreSQL version):
- PostgreSQL (13.11, 12.15, and 11.20)
- CentOS 7, UBI 8 - publicly available
- UBI 7, UBI 8 - customers only
|OLD_DATABASE_NAME||None||Refers to the database (pod) name that we want to convert.|
|NEW_DATABASE_NAME||None||Refers to the database (pod) name that is given to the upgraded database.|
|OLD_VERSION||None||The PostgreSQL version of the old database.|
|NEW_VERSION||None||The PostgreSQL version of the new database.|
|PG_LOCALE||Default locale||If set, the locale you want to create the database with.|
|XLOGDIR||None||If set, initdb will use the specified directory for WAL.|
|CRUNCHY_DEBUG||FALSE||Set this to true to enable debugging in logs. Note: this mode can reveal secrets in logs.|
data_checksumswere enabled on the database by running the following SQL: