feat(postgres): add doc on branching, link migration gist#6347
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
Amogh-Bharadwaj
changed the title
Blargian
reviewed
Jun 4, 2026
|
|
||
| ## Migrating from Supabase {#supabase} | ||
|
|
||
| If you're migrating from Supabase, see the [Supabase to Managed Postgres migration guide](https://github.com/iskakaushik/supa-auth-migrate/blob/main/MIGRATION.md) for a step-by-step walkthrough. |
Contributor
Author
There was a problem hiding this comment.
Sure @Blargian that would be great! Maybe in a separate PR then :)
I can take it up too
Blargian
reviewed
Jun 5, 2026
Co-authored-by: Shaun Struwig <41984034+Blargian@users.noreply.github.com>
Amogh-Bharadwaj
force-pushed
the
pg-branching
branch
from
8da0c25 to
193ea02
Compare
Blargian
approved these changes
Jun 8, 2026
|
Docs PR opened: ClickHouse/mintlify-docs-dev#135 Added a Managed Postgres branching guide and a Supabase migration link to the migrations overview. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds doc on branching (PITR) for Managed Postgres and a link to migrating off of Supabase
Checklist
Note
Low Risk
Documentation-only changes (new page, sidebar entry, style exception, external link); no application or infrastructure code.
Overview
Adds Managed Postgres branching documentation and wires it into the docs site, plus a Supabase migration pointer on the migrations overview.
The new Branching guide explains PITR-based branches as independent PostgreSQL deployments (backup restore + WAL replay, not copy-on-write), with sections on use cases, separate branch sizing, expected creation time, guidance to prefer local dev over per-developer production branches, and a recommended workflow diagram linking to local development.
The Data migration overview gains a Migrating from Supabase section that links to an external step-by-step guide on GitHub. Navigation adds
cloud/managed-postgres/branchingafter backup-and-restore, and Supabase is added to heading capitalization exceptions.Reviewed by Cursor Bugbot for commit 193ea02. Bugbot is set up for automated code reviews on this repo. Configure here.