2 Answers
1
Hello, Is the requirement only to being able to restore the database to a previous point in time? If yes, then this can be done without any replication, just with regular database backups.
When people speak about replicas, this means there is a secondary instance that is receiving all the changes in (near) real time, but it doesn't seam to me you're asking for that?
Regards
answered 6 months ago
0
for managed database offering you can set backup 0-35 days and for issues or rollback you can do a point in time for that period to a new instance. thus any schema changes could be rolled back as long as the change was done in last n days (n=backup days set on instance )
answered 6 months ago
Relevant questions
DMS Migration MongoDB source and RDS Postgres as destination
Accepted Answerasked 4 months agoRDS Upgrade - Postgres 12.7 -> Aurora - best way with zero or little downtime
asked 9 months ago"schema with OID does not exist" error during Postgres 12.8 to 13.6 upgrade
asked 5 months agoCannot upgrade nor restore PostgreSQL 9.4 RDS snapshot
asked 2 months agoRDS Postgres major upgrade from 12 to 13 fails
asked 15 days agoaurora postgres major upgrade - pg_dumpall
asked 4 years agoDatabase Migration
asked 21 days agoEnable RDS Encryption with minimal downtime after creation
Accepted Answerasked 2 years agoPostgres RDS Schema Upgrade (migration) with no downtime
asked 6 months agoHow to create SSL dblink connection from RDS to postgres on premise?
asked 8 months ago
Yeah I would ask the same as ADolganov mentioned that are we talking about read replica or backups/snapshots?
For replicas: We can use native RDS Read Replica or We can use DMS to create replication between two PostreSQL instances. (RDS PostgreSQL to RDS PostgreSQL or RDS PG to on-prem PG or RDS PG to Aurora).
By the way, DMS does support DDL change add columns and create tables: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.SupportedDDL.html but test is suggested before applying this to Production.