Skip to content

Commit c5593f7

Browse files
authored
chore: add links and instructions on using pg_upgrade (supabase#18743)
1 parent 1d06fc9 commit c5593f7

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ This upgrade method is currently in Beta, and is being slowly made available to
2424

2525
pg_upgrade performs an in-place upgrade on your database. For projects larger than 1GB, pg_upgrade is generally faster than a pause+restore cycle, and the speed advantage grows with the size of the database.
2626

27+
1. Plan for an appropriate downtime window, and ensure you have reviewed the [caveats](#caveats) section of this document before executing the upgrade.
28+
1. Use the "Upgrade project" button on the [Infrastructure](https://supabase.com/dashboard/project/_/settings/infrastructure) section of your dashboard.
29+
2730
Additionally, if a pg_upgrade upgrade should fail, your original DB would be brought back up online and be able to service requests.
2831

2932
As a rough rule of thumb, pg_upgrade operates at ~100mbps (when executing an upgrade on your data). Using the size of your database, you can use this metric to derive an approximate sense of the downtime window necessary for the upgrade. During this window, you should plan for your DB and associated services to be unavailable.

0 commit comments

Comments
 (0)