Several customers have been wanting to upgrade their PostgreSQL database server installations, that their EPP services are currently using. Common motivators can be related to concerns with reported vulnerabilities in older PostgreSQL versions OR to meet EPP 10 requirements based on certified PostgreSQL versions with the intended EPP 10 build release.
EPP 10 installations use a PostgreSQL database to store the majority of the configuration settings, label objects, and printing activities in the PostgreSQL DB tables.
Helping perform, validate or troubleshoot any PostgreSQL installations or upgrades fall outside the scope of our standard Software Support Agreement. If you would like any help performing these upgrades or installations, then we recommend working with your Cloud Inventory Account Executive to schedule a consultation OR project with our Infrastructure Team experts.
Product Release Relevancy
EPP 10.0.0.0 - 10.2.0.0
PostgreSQL 12 - 17
EPP 10.0.0.0 - 10.0.1.4 System Specifications - PostgreSQL 12.1 - 13
EPP 10.1.0.0 - 10.1.1.5 System Specifications - PostgreSQL 13 - 15
EPP 10.2 System Specifications - PostgreSQL 13 - 16
**NOTE: **EPP 10.1.0.0 and later versions, installed on Linux systems, will now require an additional PostgreSQL library, due to an encryption feature that has been implemented for some EPP PostgreSQL db tables. Prior to install or upgrade, you must install the ‘postresql-contrib’ library.
E.g. If you are using Postgres 15, then postresql15-contrib would need to be installed.
-
For RPM based distribution:
sudo yum install postgresql15-contrib -
For Debian based distribution:
sudo apt install postgresql15-contrib
Identify Current PostgreSQL Version
In order to determine the exact PostgreSQL build version, you can run this quick query from pgAdmin or the PSQL console.
SELECT VERSION();
Downloading PostgreSQL Installers
The current PostgreSQL release versions can be found published on their site. PostgreSQL maintains minor updates for each of their recent major release versions. E.g. 13.22, 14.19, 15.14, 16.10, and 17.6 versions, as of publishing this article.
EDB: Open-Source, Enterprise Postgres Database Management
Upgrading PostgreSQL Databases
Admins may choose to upgrade the existing PostgreSQL database OR opt to migrate the EPP database in a brand new PostgreSQL database server installation.
Upgrading PostgreSQL Install Minor Version
It should be relatively easy to apply a minor version upgrade directly to the existing PostgreSQL installation. For example, if you’re running PostgreSQL 15.x, you should be able to apply the latest PostgreSQL 15.14 installation as a direct upgrade.
Of course, it would be recommended that you create a VM snapshot before performing PostgreSQL upgrades.
-
(Recommended) Create a VM snapshot
-
Stop the EPP DSIPrint services
-
(Optional) Create backup of EPP PostgreSQL database, from pgAdmin
-
Run the latest PostgreSQL installer as an upgrade, for the currently installed major version (13.x, 14.x, 15.x, etc)
-
Start the EPP DSIPrint services
-
Test EPP login, label templates, printing, etc.
Migrating an EPP Database to New PostgreSQL Database Server
Sometimes, customers may want to install a different major version of PostgreSQL, but the PostgreSQL installers don’t usually allow directly upgrading from an older major version, like upgrading a PostgreSQL 13 installation to PostgreSQL 15.
The below steps are just general guidelines and not intended to cover every possible detail or scenario. Any issues resulting from performing an EPP database migration fall outside the scope of the Support agreement. We would highly recommend a consultation with our Infrastructure team for guidance or direct help performing this process.
-
List item
-
(Recommended) Create a VM snapshot
-
Stop the EPP DSIPrint services
-
Create backup of EPP PostgreSQL database, from pgAdmin
-
(optional) remove old PostgreSQL DB server install
-
Install new PostgreSQL DB server
Using a different port will be required if not removing the old PostgreSQL DB installation. Default port is 5432.
-
Create new EPP database
-
Restore the old EPP DB backup to the new EPP database
-
Update the EPP ..\DSIPrint\config\application.properties file
* Update the ‘app.datasource.url’ to use the new PostgreSQL database name AND postgresql DB server port, if different. Example below.
-
Start the EPP DSIPrint services
-
Test EPP login, label templates, printing, etc.