There are currently some points that should be taken into consideration when using PostgreSQL as a source database in DMS. For the moment, when a partitioned table is detected, the following occurs:
- The endpoint reports a list of parent and child tables.
- AWS DMS creates the table on the target as a regular table with the same properties as the selected tables.
- If the parent table in the source database has the same primary key value as its child tables, a "duplicate key" error is generated.
You can find the full list of limitations when using PostgreSQL as a DMS source on https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html#CHAP_Source.PostgreSQL.Limitations
DMS - How to retain non-ASCII values when running DMS task from MySQL source to Redshift targetasked 8 months ago
Redshift varchar(max) not enough to store json data type column from Postgresasked 9 months ago
Migrating partitioned table from postgres to Redshift with pglogicalasked 3 months ago
Oracle materialized view replication to postgres using DMS CDCasked 4 months ago
Migrating Aurora Postgres to RDS Postgresasked 16 days ago
Trying to copy a postgres instance from a local postgres server to an RDS instance via DMSasked 3 months ago
Using DMS CDC for Oracle to Postgresasked 5 months ago
AWS DMS Source MongoDB and Target RDS Postgres Full load not happening but ongoing replication happensAccepted Answerasked 5 months ago
Does DMS support updating value of sequences in the target for postgres to postgres data migration?asked 6 months ago
Database Migration Service - CDC with pglogicalasked a month ago