diff --git a/apps/docs/WORD_LIST.md b/apps/docs/WORD_LIST.md index e672d0882cb..549c89a3faf 100644 --- a/apps/docs/WORD_LIST.md +++ b/apps/docs/WORD_LIST.md @@ -815,6 +815,18 @@ Describe the concrete action. The linter suggests: Choose a different precise verb if the suggested replacement doesn't match the actual operation. +### vCPU + +Use _vCPU_ (plural _vCPUs_) for the CPU resources of Supabase compute sizes. +Don't describe Supabase compute in _cores_. + +_Core_ remains correct for hardware the reader owns or manages, such as +self-hosting requirements or a migration VM, and in general CPU discussion. + +- Recommended: The 16XL compute size has 64 vCPUs. +- Recommended: Run the migration from a VM with 8 CPU cores. +- Not recommended: The 16XL compute size has 64 cores. + ### versus Write _versus_ in prose, not _vs._ Use `vs` only when it is part of a literal name diff --git a/apps/docs/content/guides/database/postgres/which-version-of-postgres.mdx b/apps/docs/content/guides/database/postgres/which-version-of-postgres.mdx index f6516547146..c5655e0e563 100644 --- a/apps/docs/content/guides/database/postgres/which-version-of-postgres.mdx +++ b/apps/docs/content/guides/database/postgres/which-version-of-postgres.mdx @@ -9,14 +9,13 @@ It's important to know which version of Postgres you are running as each major v Run the following query using the [SQL Editor](/dashboard/project/_/sql) in the Supabase Dashboard: ```sql -select - version(); +show server_version; ``` Which should return something like: -```sql -PostgreSQL 15.1 on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0, 64-bit +``` +15.1 ``` This query can also be executed via `psql` or any other query editor if you prefer to [connect directly to the database](/docs/guides/database/connecting-to-postgres#direct-connection). diff --git a/apps/docs/content/guides/platform/billing-on-supabase.mdx b/apps/docs/content/guides/platform/billing-on-supabase.mdx index deb7484c30d..6db95a3c06b 100644 --- a/apps/docs/content/guides/platform/billing-on-supabase.mdx +++ b/apps/docs/content/guides/platform/billing-on-supabase.mdx @@ -81,7 +81,7 @@ You can find a detailed breakdown of all usage items and how they are billed on While your subscription plan applies to your entire organization and is charged only once, you can enhance individual projects by opting into various add-ons. -- [Compute](/docs/guides/platform/compute-and-disk#compute) to scale your database up to 64 cores and 256 GB RAM +- [Compute](/docs/guides/platform/compute-and-disk#compute) to scale your database up to 64 vCPUs and 256 GB RAM - [Read Replicas](/docs/guides/platform/read-replicas) to scale read operations and provide resiliency - [Disk](/docs/guides/platform/compute-and-disk#disk) to provision extra IOPS/throughput or use a high-performance SSD - [Log Drains](/docs/guides/observability/log-drains) to sync Supabase logs to a logging system of your choice diff --git a/apps/docs/content/guides/platform/compute-and-disk.mdx b/apps/docs/content/guides/platform/compute-and-disk.mdx index 6cc108d8f58..918ac7cab2c 100644 --- a/apps/docs/content/guides/platform/compute-and-disk.mdx +++ b/apps/docs/content/guides/platform/compute-and-disk.mdx @@ -16,20 +16,20 @@ In paid organizations, Nano Compute are billed at the same price as Micro Comput -| Compute Size | Hourly Price USD | Monthly Price USD | CPU | Memory | Max DB Size (Recommended)[^2] | -| ------------ | ------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------- | ------------ | ----------------------------- | -| Nano[^3] | | | Shared | Up to 0.5 GB | 500 MB | -| Micro | | ~ | 2-core (shared) | 1 GB | 10 GB | -| Small | | ~ | 2-core (shared) | 2 GB | 50 GB | -| Medium | | ~ | 2-core (shared) | 4 GB | 100 GB | -| Large | | ~ | 2-core (dedicated) | 8 GB | 200 GB | -| XL | | ~ | 4-core (dedicated) | 16 GB | 500 GB | -| 2XL | | ~ | 8-core (dedicated) | 32 GB | 1 TB | -| 4XL | | ~ | 16-core (dedicated) | 64 GB | 2 TB | -| 8XL | | ~,870 | 32-core (dedicated) | 128 GB | 4 TB | -| 12XL | | ~,800 | 48-core (dedicated) | 192 GB | 6 TB | -| 16XL | | ~,730 | 64-core (dedicated) | 256 GB | 10 TB | -| >16XL | - | [Contact Us](/dashboard/support/new?category=sales&subject=Enquiry%20about%20larger%20instance%20sizes) | Custom | Custom | Custom | +| Compute Size | Hourly Price USD | Monthly Price USD | CPU | Memory | Max DB Size (Recommended)[^2] | +| ------------ | ------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------- | ------------ | ----------------------------- | +| Nano[^3] | | | Shared | Up to 0.5 GB | 500 MB | +| Micro | | ~ | Shared | 1 GB | 10 GB | +| Small | | ~ | Shared | 2 GB | 50 GB | +| Medium | | ~ | Shared | 4 GB | 100 GB | +| Large | | ~ | Dedicated · 2 vCPUs | 8 GB | 200 GB | +| XL | | ~ | Dedicated · 4 vCPUs | 16 GB | 500 GB | +| 2XL | | ~ | Dedicated · 8 vCPUs | 32 GB | 1 TB | +| 4XL | | ~ | Dedicated · 16 vCPUs | 64 GB | 2 TB | +| 8XL | | ~,870 | Dedicated · 32 vCPUs | 128 GB | 4 TB | +| 12XL | | ~,800 | Dedicated · 48 vCPUs | 192 GB | 6 TB | +| 16XL | | ~,730 | Dedicated · 64 vCPUs | 256 GB | 10 TB | +| >16XL | - | [Contact Us](/dashboard/support/new?category=sales&subject=Enquiry%20about%20larger%20instance%20sizes) | Custom | Custom | Custom | [^1]: Database max connections are recommended values and can be [customized via `max_connections`](/docs/guides/database/custom-postgres-config) depending on your use case. Be aware of [these considerations](/docs/guides/troubleshooting/how-to-change-max-database-connections-_BQ8P5) before modifying. diff --git a/apps/docs/content/guides/platform/migrating-to-supabase/postgres.mdx b/apps/docs/content/guides/platform/migrating-to-supabase/postgres.mdx index 1698edc08f2..67593c1adb6 100644 --- a/apps/docs/content/guides/platform/migrating-to-supabase/postgres.mdx +++ b/apps/docs/content/guides/platform/migrating-to-supabase/postgres.mdx @@ -119,8 +119,8 @@ tmux a -t migration || tmux new -s migration - **Row Level Security (RLS) status on tables is not migrated** - You'll need to enable RLS for tables after migration. **Resource Requirements**: -| Database Size | Recommended Compute | Recommended VM | Action Required | -|--------------|-------------------|----------------|-----------------| +| Database Size | Recommended Compute | Recommended Migration VM | Action Required | +|--------------|-------------------|--------------------------|-----------------| | < 10 GB | Default | 2 vCPUs, 4 GB RAM | None | | 10-100 GB | Default-Small | 4 vCPUs, 8 GB RAM | Consider compute upgrade | | 100-500 GB | Large compute | 8 vCPUs, 16 GB RAM, NVMe | Upgrade compute before restore | @@ -203,13 +203,14 @@ Run `pg_dump --help` for a full list of options. export SUPABASE_DB_URL="Postgres://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres" # Determine restore parallelization based on your Supabase compute size: -# Free tier: 2 cores → use -j 2 -# Small compute: 2 cores → use -j 2 -# Medium compute: 4 cores → use -j 4 -# Large compute: 8 cores → use -j 8 -# XL compute: 16 cores → use -j 16 +# Micro–Medium (shared compute): use -j 2 +# Large: 2 vCPUs → use -j 2 +# XL: 4 vCPUs → use -j 4 +# 2XL: 8 vCPUs → use -j 8 +# 4XL: 16 vCPUs → use -j 16 +# (larger sizes: match -j to the vCPU count shown on the pricing page) -RESTORE_JOBS=8 # Adjust based on your Supabase compute size +RESTORE_JOBS=2 # Conservative starting point — adjust for your compute size and monitor CPU and disk IO # Restore the dump (parallel mode) # Note: -j cannot be used with --single-transaction diff --git a/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx b/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx index 4f7fbee362a..95a5ec2db0b 100644 --- a/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx +++ b/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx @@ -43,8 +43,8 @@ This situation often arises in large, high-write tables (e.g., `your_table`, whi Since the wraparound prevention autovacuum cannot be stopped, the best approach is to provide the database with sufficient resources to complete the operation as efficiently as possible. 1. **Upgrade your Database Compute Instance:** - - **Action:** Temporarily scale up your instance's CPU (e.g., from `m6g.4xlarge` to `m6g.8xlarge` or higher). - - **Why it helps:** More CPU cores and processing power will help the autovacuum operation run faster, reducing the overall time it impacts your database. + - **Action:** Temporarily scale up your instance's CPU. + - **Why it helps:** More processing power will help the autovacuum operation run faster, reducing the overall time it impacts your database. - **Considerations:** This usually causes a brief downtime (typically 1-2 minutes) as the instance restarts. However, the autovacuum process is designed to pause and resume automatically. 2. **Increase Disk Throughput/IOPS:**