dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: update compute size descriptions (CPU column, pg_restore guidance) (#49996)

Browse Source 
## What kind of change does this PR introduce?

Docs update: aligns compute descriptions with the current compute
options.

Fixes PROD-655

## What is the new behavior?

- compute-and-disk: CPU column now shows "Shared" (Nano–Medium) and
"Dedicated · N vCPUs" (Large and above), matching the pricing page
- migrating-to-supabase/postgres: pg_restore -j guidance keyed to the
vCPU count per compute size
- which-version-of-postgres: uses show server_version;, which gives
simpler, architecture-agnostic output
- High-CPU troubleshooting guide: recommends upgrading compute size
instead of naming specific instance types
billing-on-supabase: "64 cores" → "64 vCPUs"
- Section anchors unchanged (deep-linked from other pages)

## Self-review

Content-only MDX change:

- pnpm lint:mdx: no findings in the changed files (all reported
errors/warnings are pre-existing in unrelated files)
- pnpm build:guides-markdown: builds clean; generated .md exports for
the changed pages verified
- All pages verified rendering in the local dev app on current master
- Swept apps/docs for remaining core-count / instance-type mentions in
compute descriptions

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Updated PostgreSQL version-checking instructions to use `show
server_version;` with simplified output.
* Clarified compute sizing terminology using shared and dedicated CPU
allocations and vCPU-based descriptions.
  * Updated billing guidance to describe scaling up to 64 vCPUs.
* Revised database restore guidance with current compute tiers and
recommended parallelization settings.
* Simplified high-CPU troubleshooting guidance to recommend temporarily
scaling CPU capacity.
* Added writing guidance to consistently use “vCPU” and “vCPUs” for
Supabase compute resources.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Lukas BernertandClaude Fable 5 authored and GitHub committed 2026-09-17 14:34:01 +02:00
1 parent be9ec25270
commit 459436e87f
6 files changed
+41 -29
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

apps/docs/content/guides/database/postgres/which-version-of-postgres.mdx
+3 -4
View File
@@ -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).
apps/docs/content/guides/platform/billing-on-supabase.mdx
+1 -1
View File
@@ -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
apps/docs/content/guides/platform/compute-and-disk.mdx
+14 -14
View File
@@ -16,20 +16,20 @@ In paid organizations, Nano Compute are billed at the same price as Micro Comput
</Admonition>
| Compute Size | Hourly Price USD | Monthly Price USD | CPU | Memory | Max DB Size (Recommended)[^2] |
| ------------ | ------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------- | ------------ | ----------------------------- |
| Nano[^3] | <Price price="0" /> | <Price price="0" /> | Shared | Up to 0.5 GB | 500 MB |
| Micro | <Price price="0.01344" /> | ~<Price price="10" /> | 2-core (shared) | 1 GB | 10 GB |
| Small | <Price price="0.0206" /> | ~<Price price="15" /> | 2-core (shared) | 2 GB | 50 GB |
| Medium | <Price price="0.0822" /> | ~<Price price="60" /> | 2-core (shared) | 4 GB | 100 GB |
| Large | <Price price="0.1517" /> | ~<Price price="110" /> | 2-core (dedicated) | 8 GB | 200 GB |
| XL | <Price price="0.2877" /> | ~<Price price="210" /> | 4-core (dedicated) | 16 GB | 500 GB |
| 2XL | <Price price="0.562" /> | ~<Price price="410" /> | 8-core (dedicated) | 32 GB | 1 TB |
| 4XL | <Price price="1.32" /> | ~<Price price="960" /> | 16-core (dedicated) | 64 GB | 2 TB |
| 8XL | <Price price="2.562" /> | ~<Price price="1" />,870 | 32-core (dedicated) | 128 GB | 4 TB |
| 12XL | <Price price="3.836" /> | ~<Price price="2" />,800 | 48-core (dedicated) | 192 GB | 6 TB |
| 16XL | <Price price="5.12" /> | ~<Price price="3" />,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] | <Price price="0" /> | <Price price="0" /> | Shared | Up to 0.5 GB | 500 MB |
| Micro | <Price price="0.01344" /> | ~<Price price="10" /> | Shared | 1 GB | 10 GB |
| Small | <Price price="0.0206" /> | ~<Price price="15" /> | Shared | 2 GB | 50 GB |
| Medium | <Price price="0.0822" /> | ~<Price price="60" /> | Shared | 4 GB | 100 GB |
| Large | <Price price="0.1517" /> | ~<Price price="110" /> | Dedicated · 2 vCPUs | 8 GB | 200 GB |
| XL | <Price price="0.2877" /> | ~<Price price="210" /> | Dedicated · 4 vCPUs | 16 GB | 500 GB |
| 2XL | <Price price="0.562" /> | ~<Price price="410" /> | Dedicated · 8 vCPUs | 32 GB | 1 TB |
| 4XL | <Price price="1.32" /> | ~<Price price="960" /> | Dedicated · 16 vCPUs | 64 GB | 2 TB |
| 8XL | <Price price="2.562" /> | ~<Price price="1" />,870 | Dedicated · 32 vCPUs | 128 GB | 4 TB |
| 12XL | <Price price="3.836" /> | ~<Price price="2" />,800 | Dedicated · 48 vCPUs | 192 GB | 6 TB |
| 16XL | <Price price="5.12" /> | ~<Price price="3" />,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.
apps/docs/content/guides/platform/migrating-to-supabase/postgres.mdx
+9 -8
View File
@@ -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
apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx
+2 -2
View File
@@ -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:**