1 Answer
- Newest
- Most votes
- Most comments
0
I understand your PostgreSQL upgrade from version 12.22 to 16.13 is stuck. Here are steps to help resolve this:
Immediate Actions:
-
Check the upgrade status - Monitor the RDS event log and CloudWatch metrics to understand where the upgrade is stuck. Major version upgrades can take several hours depending on database size.
-
Review prerequisites - Ensure you met all requirements before the upgrade:
- Sufficient storage space (at least 2x your current usage is recommended)
- Compatible parameter groups for PostgreSQL 16
- Removed any incompatible extensions or features from version 12
- If truly stuck (not just slow):
- Check if there are long-running transactions or connections that might be blocking the upgrade
- Review CloudWatch logs for any error messages
- Verify that the instance has adequate resources (CPU, memory, IOPS)
Important Considerations:
- Upgrading from PostgreSQL 12 to 16 is a major version upgrade spanning multiple versions, which is more complex and time-consuming
- The upgrade process involves creating a new instance, so it cannot be easily "unstuck" once started
- If the upgrade has genuinely failed (not just taking a long time), you may need to restore from your pre-upgrade snapshot
If you need to intervene:
- Contact AWS Support if the upgrade has been running for an unusually long time (many hours beyond expected)
- Have your pre-upgrade backup ready in case you need to roll back
What is the current status showing in your RDS console, and how long has the upgrade been running?
Relevant content
- asked 5 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
