Select Language:
If your PostgreSQL upgrade from version 12.22 to 16.13 seems to be stuck, don’t worry—there are still steps you can take to get things moving again. Here’s a straightforward guide to help you troubleshoot and resolve the issue.
First, check the current status of the upgrade. Look at your RDS event logs and CloudWatch metrics to see what’s happening. Large database upgrades can take a long time—sometimes several hours—depending on how much data you have. Knowing where things stand will give you clues about whether the process is really stuck or just slow.
Next, review the upgrade prerequisites to confirm everything is in order. Make sure you have enough storage space—it’s best to have at least twice your current database size. Also, check that your parameter groups are compatible with PostgreSQL 16, and ensure you’ve removed any incompatible extensions or features from your current version.
If the upgrade appears to be truly stuck (not just slow), consider these points:
– Look for any long-running transactions or open connections that might be blocking the process.
– Check your CloudWatch logs for any error messages or warnings.
– Verify that your instance has sufficient resources like CPU, memory, and IOPS.
Keep in mind, upgrading from PostgreSQL 12 to 16 is a major update across multiple versions, which makes it more complex and can take a lot of time. The upgrade process creates a new instance, so once it’s started, it’s not easy to stop or restart without potential fallback plans.
If it really seems to be failed, not just taking a while, your best option is to restore from a backup taken before the upgrade. Having that snapshot ready will save you time if you need to revert.
If the upgrade has been running hours longer than expected or if you’re unsure, reaching out to AWS Support can be very helpful. They can guide you based on your specific situation.
Finally, think about your current RDS console. What does the status show? How long has the upgrade been running? These details will help you and support teams determine the next best steps.



