If you have a support agreement with AWS, your best course of action in something like this is to open a support case for advise, especially since you got into a state you shouldn't have been able to trigger. Waiting for RDS Postgres engine 14.3 to be released may or may not help you given the undefined state you're in, and you have no way of knowing exactly that will happen. Aurora for Postgres supports 14.3 as of June 21st, in case you want to use that together with whatever glitch you hit as an indication, but you'll have to wait and see.
If you have a pre-upgrade snapshot, I'd suggest you restore your database from that if that's an option in terms of the potential data loss.
We have reached to you on your registered email with guidance. Please feel free to correspond with us over email. We are happy to schedule a call and provide additional help if needed.
- Accepted Answerasked 8 months ago
- How do I troubleshoot issues with major version upgrades in Amazon RDS for PostgreSQL and Aurora for PostgreSQL?AWS OFFICIALUpdated a year ago
- Why do I get an RDS-EVENT-0198 error when I create a custom engine version of my Amazon RDS Custom for Oracle DB instance?AWS OFFICIALUpdated 3 months ago
- Why did my Secrets Manager Lambda rotation function fail with a “Database engine must be set to 'postgres'/'mysql'” error?AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- EXPERTpublished 7 months ago
- EXPERTpublished 2 months ago