From 68ff3fca43965c9941c679a5bfd9dcee9122b535 Mon Sep 17 00:00:00 2001 From: Rodrigo Martins Mansueli Date: Thu, 11 May 2023 12:34:20 -0300 Subject: [PATCH] Update heroku.mdx --- .../guides/resources/migrating-to-supabase/heroku.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx b/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx index b2b5df2acd2..637a2e8068f 100644 --- a/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx +++ b/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx @@ -67,6 +67,13 @@ psql -h $SUPABASE_HOST -U postgres -f heroku_dump.sql Run `pg_dump --help` for a full list of options. + + + - If you plan on migrating a database larger than 6 GB, we recommend [contacting support](https://app.supabase.com/support/new) to ensure that you'll have the proper disk size pre-provisioned. You can read more about how the disk is managed on Supabase on the [Database usage](https://supabase.com/docs/guides/platform/database-size#disk-management). + - We also recommend upgrading to at least a [Large instance](https://supabase.com/docs/guides/platform/compute-add-ons) for the migration (you can downgrade later) to avoid running out of IO-Budget. + + + export const Page = ({ children }) => export default Page