Repository navigation
docs(prisma-postgres): v7 PostgreSQL import guide uses Supabase's direct connection for pg_dump, shared pooler as fallback - #8709
Conversation
…ect connection for pg_dump, shared pooler as fallback Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Findings
 |
| Layer / File(s) | Summary |
|---|---|
Connection URL guidance apps/docs/content/docs/(index)/v7/prisma-postgres/import-from-existing-database-postgresql.mdx |
The instructions recommend the direct connection URL for pg_dump and provide the shared pooler in session mode as an alternative when the network cannot reach the applicable address. They include example URLs and a date when the details were checked. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Suggested reviewers: ankur-arch
Merge Risk: 
ee9bf
-
Correct the fallback link anchor before merging so IPv4-only users reach the required connection guidance.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and specifically summarizes the main documentation change: using Supabase's direct connection for pg_dump and the shared pooler as a fallback. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
🍈 Lychee Link Check Report13 links: ✅ All links are working!Full Statistics Table
|
|
@coderabbitai review |
Action not completed
|
|
@coderabbitai full review |
Action not completed
|
|
@coderabbitai full review |
Action not completed
|
|
@coderabbitai full review |
Action performed
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This page is the Prisma ORM v7 version of the guide for importing an existing PostgreSQL database into Prisma Postgres.
Changes
pg_dump. Supabase's page lists a direct connection forpg_dumpand session mode as the alternative on IPv4-only networks, so the note now gives the direct connection first and session mode as the fallback, each with an example URL. This matches the Supabase migration guide in these docs.Sources checked 2026-11-02
pg_dump, backup and restore, or replication" lists "Direct connection"; "Direct connections are on IPv6, or on IPv4 if the project has the" IPv4 add-on; session mode, "Use it as an alternative to a direct connection when you connect from an IPv4-only network."id="direct-connection"andid="pooler-session-mode", and nosupavisor-session-modeanchor.Checks
git diff --check: clean.apps/docs:pnpm run lint:links: 0 errors. The new external URL returns 200.apps/docs:pnpm run test: 109 of 110 pass.src/lib/database-selection.test.tsfails with or without this change.🤖 Generated with Claude Code
Summary by CodeRabbit