From 6dd1b59d8a5cd890746bced8dd227a68afda8a1a Mon Sep 17 00:00:00 2001 From: Div Arora Date: Tue, 14 Feb 2023 14:17:23 +0800 Subject: [PATCH] chore: disk expansion restrictions apply to both manual and auto expansion --- apps/docs/pages/guides/platform/database-usage.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/platform/database-usage.mdx b/apps/docs/pages/guides/platform/database-usage.mdx index c6a734b4fac..6ce6385770d 100644 --- a/apps/docs/pages/guides/platform/database-usage.mdx +++ b/apps/docs/pages/guides/platform/database-usage.mdx @@ -24,7 +24,7 @@ This value is also reported in the [database settings page](https://app.supabase Supabase uses network-attached storage to balance performance with scalability. For Pro and Enterprise projects, disk size expands ~1.5x automatically (e.g., 8GB -> 12GB) when you reach 90% of the disk size. -Automatic disk size expansion can only occur once every six hours. +Disk size expansion can only occur once every six hours. Pro projects can store up to 1024TB. All projects enter read-only mode when you reach 95% of the disk size. In read-only mode, clients will encounter errors such as `cannot execute INSERT in a read-only transaction`.