cancel
Showing results for 
Search instead for 
Did you mean: 

EDB Postgres Upgrade Methodology and Best Practices

 

EDB Postgres Database includes exciting new features with every new release and to take advantage of these features it often requires upgrading the databases from older version to latest EDB Postgres version. In addition, many of these upgrades will also 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.

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 version to latest version of EDB Postgres Database 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 attached document for full upgrade methodology and best practice.

Version history
Revision #:
1 of 1
Last update:
a month ago
Updated by:
 
Contributors