Database | Oldest supported version | Newest supported version |
---|---|---|
PostgreSQL | 9.2 | 17.0 |
MariadDB | 5.5 | 11.6 |
MYSQL | 5.7 | 9.0 |
MSSQL | 14.0 (from 2017) | 16.0 (from 2022) |
HSQL | NOT RELEVANT | NOT RELEVANT |
For optimal performance and compatibility of your database with Unimus you can find recommend DB settings it he following table.
In case your database use any other collation, please make sure to choose one that is always case-insensitive.
Database | Characters set | Collation |
---|---|---|
PostgreSQL | utf8 | C (equivalent to POSIX ) |
MariadDB | utf8mb4 | utf8mb4_unicode_ci |
MYSQL | utf8mb4 | utf8mb4_unicode_ci |
MSSQL | UCS-2 / UTF-16 | Latin1_General_CI SQL_Latin1_General_CP1_CI |
HSQL | NOT RELEVANT | NOT RELEVANT |
Using this combination ensures better global language support and consistent case-insensitive behavior in text comparisons.
Before you start with migration and for more information related to PostgreSQL we highly recommend to visit visit the official page: https://www.postgresql.org/docs/9.0/migration.html
Access PostgreSQL:
Log in to your old PostgreSQL 11 database and run the following commands:
ALTER TABLE backup SET WITHOUT OIDS;
ALTER TABLE push_output_group SET WITHOUT OIDS;
Pre-check the upgrade:
Run the following command to check if your system is ready for the upgrade:
pg_upgrade --check
pg_dump
command.Migrate the data:
pg_upgrade
Check Compatibility:
Ensure that both your old (PostgreSQL 12) and new (PostgreSQL 16) databases are compatible for migration. You can do this by running the following command:
pg_upgrade --check
Migrate the Data:
pg_upgrade