Upgrading Babelfish to a new minor version - Amazon Aurora

Upgrading Babelfish to a new minor version

A new minor version includes only changes that are backward compatible. A patch version includes important fixes for a minor version after its release. For example, the version label for the first release of Aurora PostgreSQL 13.4 was Aurora PostgreSQL 13.4.0. Several patches for that minor version have been released to date, including Aurora PostgreSQL 13.4.1, 13.4.2, and 13.4.4. You can find the patches available for each Aurora PostgreSQL version in the Patch releases list at the top of the Aurora PostgreSQL release notes for that version. For an example, see PostgreSQL 14.3 in the Release Notes for Aurora PostgreSQL.

If your Aurora PostgreSQL DB cluster is configured with the Auto minor version upgrade option, your Babelfish for Aurora PostgreSQL DB cluster is upgraded automatically during the cluster's maintenance window. To learn more about auto minor version upgrade (AmVU) and how to use it, see Automatic minor version upgrades for Aurora DB clusters. If your cluster isn't using AmVU, you can manually upgrade your Babelfish for Aurora PostgreSQL DB cluster to new minor versions either by responding to maintenance tasks, or by modifying the cluster to use the new version.

When you choose an Aurora PostgreSQL version to install and when you view an existing Aurora PostgreSQL DB cluster in the AWS Management Console, the version displays the major.minor digits only. For example, the following image from the Console for an existing Babelfish for Aurora PostgreSQL DB cluster with Aurora PostgreSQL 13.4 recommends upgrading the cluster to version 13.7, a new minor release of Aurora PostgreSQL.

Minor version upgrade available for an Aurora PostgreSQL DB cluster with Babelfish.

To get complete version details, including the patch level, you can query the Aurora PostgreSQL DB cluster using the aurora_version Aurora PostgreSQL function. For more information, see aurora_version in the Aurora PostgreSQL functions reference. You can find an example of using the function in the To use the PostgreSQL port to query for version information procedure in Identifying your version of Babelfish.

The following table shows Aurora PostgreSQL and Babelfish version and the available target versions that can support the minor version upgrade process.

Current source versions

Newest upgrade targets

Aurora PostgreSQL (Babelfish) Aurora PostgreSQL (Babelfish)

16.3 (4.2.0)

16.4 (4.3.0)

16.2 (4.1.0)

16.4 (4.3.0), 16.3 (4.2.0)

16.1 (4.0.0)

16.4 (4.3.0), 16.3 (4.2.0), 16.2 (4.1.0)

15.7 (3.6.0)

15.8 (3.7.0)

15.6 (3.5.0)

15.8 (3.7.0), 15.7 (3.6.0)

15.5 (3.4.0)

15.8 (3.7.0), 15.7 (3.6.0), 15.6 (3.5.0)

15.4 (3.3.0)

15.8 (3.7.0), 15.7 (3.6.0), 15.6 (3.5.0), 15.5 (3.4.0)

15.3 (3.2.0)

15.8 (3.7.0), 15.7 (3.6.0), 15.6 (3.5.0), 15.5 (3.4.0), 15.4 (3.3.0)

15.2 (3.1.0)

15.8 (3.7.0), 15.7 (3.6.0), 15.6 (3.5.0), 15.5 (3.4.0), 15.4 (3.3.0), 15.3 (3.2.0)

14.12 (2.9.0)

14.13 (2.10.0)

14.11 (2.8.0)

14.13 (2.10.0), 14.12 (2.9.0)

14.10 (2.7.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0)

14.9 (2.6.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0), 14.10 (2.7.0)

14.8 (2.5.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0), 14.10 (2.7.0), 14.9 (2.6.0)

14.7 (2.4.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0), 14.10 (2.7.0), 14.9 (2.6.0), 14.8 (2.5.0)

14.6 (2.3.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0), 14.10 (2.7.0), 14.9 (2.6.0), 14.8 (2.5.0), 14.7 (2.4.0)

14.5 (2.2.0)

14.13 (2.10.0), 14.12 (2.9.0), 14.11 (2.8.0), 14.10 (2.7.0), 14.9 (2.6.0), 14.8 (2.5.0), 14.7 (2.4.0), 14.6 (2.3.0)

14.3 (2.1.0)

14.6 (2.3.0)

13.8 (1.4.0)

13.9 (1.5.0)

13.7 (1.3.0)

13.9 (1.5.0), 13.8 (1.4.0)