DMS Support for Postgres 17

0

Hi,

I need to set up a replication task on DMS. My source DB is on-premise (Postgres 17.2), and the target DB is on AWS (Also Postgres 17.2).

I tested the two endpoints using a replication instance, and while the AWS Postgres 17.2 is reporting "successful", the on-premise one displays this error message:

"Source database version number is not supported: 170002 PostgreSQL 17.2 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit"

I'm a bit confused as this link doesn't show support for Postgres 17.x: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html however the connection the AWS Postgres 17.2 works well.

So, does anyone know if Postgres 17.2 is supported and the issue is with my on-premise DB, or if Postgres 17.2 is not supported and AWS DMS wrongly reported success on my AWS 17.2 instance?

If this is the latter, does anyone know if there is an ETA for supporting 17.2 in AWS DMS?

Many thanks!

1 Answer
1

Based on the information available, it appears that PostgreSQL 17.2 is not currently supported by AWS Database Migration Service (DMS) as a source database. The error message you received for your on-premise PostgreSQL 17.2 database clearly indicates that this version is not supported.

The fact that your AWS PostgreSQL 17.2 target database connection test was reported as successful is interesting, but it's important to note that DMS often has different support levels for source and target databases. It's possible that PostgreSQL 17.2 is supported as a target but not as a source in the current version of DMS.

AWS DMS typically supports PostgreSQL versions that are widely adopted and have been available for some time. As PostgreSQL 17.2 is a very recent release, it's not surprising that it's not yet supported as a source database in DMS.

Unfortunately, there isn't any publicly available information about an ETA for supporting PostgreSQL 17.2 in AWS DMS. AWS typically updates their services to support new database versions over time, but they don't usually provide specific timelines for these updates.

In the meantime, you might consider the following options:

  1. Use an earlier version of PostgreSQL that is supported by DMS for your source database.
  2. Wait for AWS to update DMS to support PostgreSQL 17.2 as a source.
  3. Explore alternative migration methods, such as logical replication or third-party tools that might support PostgreSQL 17.2.

It's recommended to keep an eye on AWS DMS documentation for updates on supported PostgreSQL versions. You could also reach out to AWS Support for more specific information about future plans for PostgreSQL 17.2 support in DMS.
Sources
Using a PostgreSQL database as an AWS DMS source - AWS Database Migration Service
Using a PostgreSQL database as a source for homogeneous data migrations in AWS DMS - AWS Database Migration Service

profile picture
answered 4 days ago
profile picture
EXPERT
reviewed 3 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions