Restore data for an RDS for PostgreSQL instance in scenarios such as accidental release, data deletion, or cross-region recovery.
Scenario 1: Restore a released instance
Recycle Bin: Go to the Recycle Bin page, select the region, and rebuild the instance if found.
-
An RDS for PostgreSQL instance enters the recycle bin after manual release, expiration, or refund, except in the following cases:
-
The instance is refunded or manually released within 7 days of creation.
-
The pay-as-you-go instance is automatically released due to overdue payment.
-
The instance is a read-only instance.
-
-
RDS for PostgreSQL 9.4 instances cannot be rebuilt because they are no longer available for purchase.
Scenario 2: Restore accidentally deleted or modified data
|
Solution |
Restoration point in time |
Restoration scope |
Restoration destination |
Restoration speed |
|||||
|
Any point in time |
Point in time of the backup set |
All databases and tables |
Partial Databases |
Partial tables |
To a new RDS instance |
Restore to the original RDS instance |
Restore to another existing RDS instance |
||
|
✔️ |
✔️ |
✔️ |
❌ |
❌ |
✔️ |
❌ |
❌ |
Slow |
|
|
✔️ |
✔️ |
✔️ |
✔️ |
❌ |
❌ |
✔️ |
✔️ |
Fast |
|
-
Restoring to a new RDS instance: Restore data to a temporary pay-as-you-go instance, migrate the data back to the original instance, then release the temporary instance to reduce costs.
-
Restoring to the original RDS instance: This method does not overwrite existing data on the original instance.
-
To restore specific tables, use Restore data from a logical backup file using pg_restore.
Other scenarios
-
Restore data across regions with Cross-region data restoration.
-
Restore data to a self-managed database with Restore data from a CSV or SQL file of an RDS for PostgreSQL instance to a self-managed database.