mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Nik RichersandNik Richers
0405b31b26
## I have read the CONTRIBUTING.md file. YES ## What kind of change does this PR introduce? Re-add. Reapplies the Multigres Private Alpha docs section removed in #50662, ready to merge once Sugu gives the go-ahead. Do not merge until then. Linear: MUL-1621 (follow-up to MUL-452). ## What is the current behavior? Multigres docs section is down (per #50662): no overview/compatibility pages, no sidebar entry, no features-table row, no "What you get" cards. ## What is the new behavior? Exact reapply of #49020 (with Multigres marked Private Alpha): overview guide at `/docs/guides/database/multigres`, compatibility stub, Database sidebar entry, features-table row, "What you get" cards, and the `ContentListings` optional-`href` support they rely on. Base branch is the revert PR (#50662) so the diff here is legible now; retarget to `master` once #50662 merges. ## Additional context - `pnpm --filter docs exec vitest run lib/content-listings.test.ts` — 22 passed - Blocked on Sugu's go-ahead — `do-not-merge` label applied --------- Co-authored-by: Nik Richers <nik@validmind.ai>
61 lines
3.2 KiB
Plaintext
61 lines
3.2 KiB
Plaintext
---
|
|
id: 'multigres'
|
|
title: 'Multigres'
|
|
subtitle: 'Horizontally scalable Postgres for high availability'
|
|
description: 'Run high availability Postgres across multiple nodes with automatic failover, using Multigres.'
|
|
---
|
|
|
|
<Admonition type="caution">
|
|
|
|
Multigres is in [Private Alpha](/docs/guides/getting-started/features#feature-status). It's free during the Alpha for organizations on a paid plan, for up to two projects, but pricing may change once it leaves Alpha. It isn't covered by the [uptime SLA](/sla), and Supabase isn't targeting production or mission-critical workloads with it during this stage.
|
|
|
|
</Admonition>
|
|
|
|
Multigres gives your project high availability by running Postgres across multiple nodes instead of one, so reads and writes continue if a node fails. It is Supabase's integration of [Multigres](https://multigres.com), an open-source project that brings the same distributed-systems approach Vitess brought to MySQL to Postgres.
|
|
|
|
<ContentListings id="database-multigres-what-you-get" />
|
|
|
|
## Eligibility
|
|
|
|
During the Private Alpha:
|
|
|
|
- Multigres is available to organizations on a paid plan. It isn't available on the Free plan.
|
|
- Availability is being rolled out gradually, so the option to enable it may not yet appear for every eligible organization.
|
|
- Up to two projects per eligible organization can use Multigres for free during the Alpha.
|
|
|
|
## Enabling Multigres
|
|
|
|
In the Dashboard, Multigres appears as **High availability** during project creation:
|
|
|
|
1. Open [Create a new project](/dashboard/new/_) in the Dashboard.
|
|
2. Under **High availability**, turn on **Enable high availability**.
|
|
3. Finish the remaining fields such as database password, region, and compute size, if shown.
|
|
4. Click **Create new project**.
|
|
|
|
If your organization isn't eligible or hasn't been rolled out yet, **High availability** won't appear.
|
|
|
|
## What's not included in the alpha
|
|
|
|
Some Supabase features and project operations aren't yet available on Multigres-backed projects:
|
|
|
|
- **Realtime.** Multigres doesn't yet support the logical replication that Realtime depends on, so Realtime is unavailable.
|
|
- **Point-in-Time Recovery.** Only the standard daily backups are available.
|
|
- **Cross-region read replicas.** Multigres projects run in a single region during the Alpha.
|
|
- **OrioleDB.** A project can use Multigres or [OrioleDB](/docs/guides/database/orioledb), not both.
|
|
- **Resizing after creation.** Compute size, disk, and the number of replicas can't be changed after a Multigres project is created.
|
|
- **Sharding and custom durability policies.** These are on the longer-term roadmap but aren't part of the Alpha.
|
|
|
|
<Admonition type="caution">
|
|
|
|
Enabling Multigres migrates your project's database to run on Multigres. There's currently no managed path to move it back to a standard Postgres project.
|
|
|
|
</Admonition>
|
|
|
|
## Compatibility
|
|
|
|
Multigres aims for full compatibility with standard Postgres, but there are some differences to be aware of. See [Multigres compatibility](/docs/guides/database/multigres/compatibility) for details.
|
|
|
|
## Resources
|
|
|
|
[Multigres documentation](https://multigres.com/docs) — architecture, self-hosted deployment, and other technical depth that goes beyond the hosted Supabase integration covered on this page.
|