Overview

Due to factors like deprecation or security vulnerabilities, we may need to occasionally update the version of PostgreSQL that is used by Redgate Clone for its backing database.

Due to the architecture of Redgate Clone this is a more involved process than a regular upgrade, and requires the user to perform a manual action.

Updating from PostgreSQL version 13 to PostgreSQL version 17

It is mandatory to perform the update to PostgreSQL 17 when upgrading to version 1.0.78609 (or higher). This only ever needs to be done once.

It is recommended that the update is completed before upgrading Redgate Clone, although it will also work post-upgrade.

Steps

1. Start a bash session (such as git-bash, WSL, or SSH on to the Redgate Clone VM if applicable).
2. Make sure you are connected to the cluster and can run kubectl commands.
3. Download the update script by clicking on this link.
4. Move the file to a location that is accessible to your bash session.
5. In your bash session, execute the script and wait for it to complete.
6. Your deployment should go green, and you can now upgrade Redgate Clone (if you haven't done so already).

About the update

Release 1.0.78609 includes an update to the version of PostgreSQL used by the backing database.

This release expects the backing database pod to run PostgreSQL v17. We provide a bash script that performs an update of the database to this version.

It works by scaling down the backing database pod, creating a temporary pod with both versions of PostgreSQL, updating the underlying database inside the temporary pod, then scaling the backing database pod back up.

The script can be run either before or after deploying the upgrade:

• Run the script before upgrading Redgate Clone to version 1.0.78609 or above (recommended) - this will update your backing database while still running on the down-level version, and bring the backing database pod back up using PostgreSQL 17. This will then allow an upgrade of Redgate Clone without loss of service. Please upgrade immediately after running the bash script, as a reboot or redeploy could cause the pod to revert back to version 13 and report a database mismatch. If this does happen, an upgrade will resolve it and restore service.
• Run the script after upgrading Redgate Clone to version 1.0.78609 or above - the deployment will report as 'unavailable' until the bash script is run following an upgrade. Running the script will update the backing database and result in restoration of service.