You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/guides/platform/read-replicas.mdx
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,10 +51,11 @@ A project needs to satisfy these requirements to deploy a Read Replica:
51
51
- Support for projects on Fly.io is coming.
52
52
1. Running on at least a [Small compute add-on](/docs/guides/platform/compute-add-ons).
53
53
- 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)
56
54
1. Running on Postgres 15.
57
55
- 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.
0 commit comments