- 最新
- 投票最多
- 评论最多
Hi,
Currently replication slots must be explicitly dropped before a major version upgrade in Aurora Postgres.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.html has some additional information that may be helpful, but let me know if you have other questions/concerns.
We have more than 20 databases in the instance, and we use DMS to sync data between services. Do you have any suggestions for doing a major version upgrade?
We have already tried the DMS approach. Create a new 11.11 instance, and sync data from the old instance to the new one via DMS. this approach has limitations, I have to manually migrate some data, and change some table schemas. It's far too complicated.
Hello,
Sorry this response took so long. I was doing my own testing to reproduce the issue.
Unfortunately you will have to either delete the DMS replication tasks so the slots get dropped, or you can stop them and manually drop the replication slots and then perform the major version upgrade.
After upgrading, if your task is an ongoing replication task vs. a full load and ongoing replication, you can restart and not resume it. DMS will begin replicating new changes over. If you deleted the task before the upgrade, you will need to create a new one. Note that if there were writes that happened on the source replicated databases/tables in between dropping the replication slots and starting the task again, those will not be replicated over. The safer choice would be to do another full load (truncating or dropping the target table) + ongoing replication if that's feasible with your data set size.
I've created a feature request to support replication slots across major version upgrades that we will try to prioritize. Thank you for the question and input on the feature.
相关内容
- AWS 官方已更新 10 个月前