mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 19:05:06 +03:00
chore: add note re: change in logical restore requirements (#20425)
This commit is contained in:
1 parent
a4f86bce8f
commit
9e7981e190
1 file changed
+2
@@ -68,6 +68,8 @@ When selecting a backup to restore to, select the closest available one made bef
|
||||
|
||||
The Dashboard will then prompt for a confirmation before proceeding with the restoration. The project will be inaccessible following this. As such, do ensure to allot downtime beforehand. This is dependent on the size of the database. The larger it is, the longer the downtime will be. Once the confirmation has been given, the underlying SQL of the chosen backup is then run against the project. The PostgreSQL utility [psql](https://www.postgresql.org/docs/current/app-psql.html) is used to facilitate the restoration. The Dashboard will display a notification once the restoration completes.
|
||||
|
||||
If your project is using subscriptions or replication slots, you will need to drop them prior to the restoration, and re-create them afterwards. The slot used by Realtime is exempted from this, and will be handled automatically.
|
||||
|
||||
{/* screenshot of the Dashboard of the project completing restoration */}
|
||||
|
||||
## Point-in-Time recovery
|
||||
|
||||
Reference in new issue
Block a user