EDB Postgres Database includes exciting new features with every new release and to take advantage of these features, we recommend upgrading to the latest EDB Postgres version. In addition, many of these upgrades may coincide with additional changes to the database setup, include moving to newly purchased server hardware, migrating to different storage architectures, changing the database character set, or even migrating to a completely different operating systems. This means that the upgrade process can be a long and complex one.
Due to the stringent high availability requirements for the databases that store mission critical data, database upgrades have become more challenging these days. Unfortunately, there are essential events that require application downtime, including modifying hardware or database software, upgrading applications, applying software patches, and migrating to different computing architectures. Because such events are not conceived via system or data failures, they are aptly classified as planned outages.
This best practice document explains how organizations can upgrade or migrate from older versions of the EDB Postgres Database to the latest version with or without downtime. The primary goal of this document is to increase awareness of a solution that eliminates downtime during a planned outage for database upgrades. Secondarily, to explain how to minimize the total time required by entire upgrade process.
Please refer to the attached document, on the right hand side under attachments, for the full upgrade methodology and best practice.