From 9e7981e190aa7531e1c2c49232e91c65e2bdbe54 Mon Sep 17 00:00:00 2001 From: Div Arora Date: Tue, 6 Feb 2024 14:31:55 +0800 Subject: [PATCH] chore: add note re: change in logical restore requirements (#20425) --- apps/docs/pages/guides/platform/backups.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/apps/docs/pages/guides/platform/backups.mdx b/apps/docs/pages/guides/platform/backups.mdx index b300662eaba..a0515b0d6fc 100644 --- a/apps/docs/pages/guides/platform/backups.mdx +++ b/apps/docs/pages/guides/platform/backups.mdx @@ -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