Skip to content

Commit 410da54

Browse files
authored
chore: update RR setup requirements re: PITR (supabase#22421)
1 parent 51d9b69 commit 410da54

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

apps/docs/content/guides/platform/read-replicas.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,11 @@ A project needs to satisfy these requirements to deploy a Read Replica:
5151
- Support for projects on Fly.io is coming.
5252
1. Running on at least a [Small compute add-on](/docs/guides/platform/compute-add-ons).
5353
- Read Replicas are currently placed on the same compute instance as the database to make sure they can keep up with the Primary's activities.
54-
1. Using [physical backups](/docs/guides/platform/backups#point-in-time-recovery)
55-
- Physical backups are automatically enabled if using [PITR](/docs/guides/platform/backups#point-in-time-recovery)
5654
1. Running on Postgres 15.
5755
- For projects running on older versions of PostgreSQL, you will need to [upgrade to the latest platform version](/docs/guides/platform/migrating-and-upgrading-projects#pgupgrade).
56+
1. Using [physical backups](/docs/guides/platform/backups#point-in-time-recovery)
57+
- Physical backups are automatically enabled if using [PITR](/docs/guides/platform/backups#point-in-time-recovery)
58+
- If you're not using PITR, you'll be able to switch to physical backups as part of the Read Replica setup process. Note that physical backups can't be downloaded from the dashboard in the way logical backups can.
5859

5960
## Getting started
6061

0 commit comments

Comments
 (0)