[gregory-boch-prisma]

The two PostgreSQL guides touched here teach readers to run PostgreSQL on their own computer and to connect to it with psql; neither tells them where to go when that database needs to be reachable from somewhere else.

Changes

• content/04-postgresql/04-setting-up-a-local-postgresql-database.mdx: one paragraph added at the end of the existing PrismaOutlinks block in "Creating a role and a database for your application", pointing to the Prisma docs page on moving a local PostgreSQL database to Prisma Postgres with pg_dump and pg_restore. Because this guide installs PostgreSQL 18, the paragraph also says that the import needs the PostgreSQL 17 versions of those tools, works from version 17 or older, and that moving from 18 takes a separate, downgrade-compatible process, as the import guide states.
• content/04-postgresql/06-connecting-to-postgresql-databases.mdx: the same pointer added at the end of the existing PrismaOutlinks block after the conclusion, with the PostgreSQL 17 tools and version 17 or older requirement.

Both additions are plain paragraphs inside the existing PrismaOutlinks blocks, like the other blocks in content/, so they stay removable promotional material as CONTRIBUTING.md describes. Because the Markdown exporter drops PrismaOutlinks, the pointer appears on the HTML pages only, not in the .md pages or llms.txt. No other text, front matter or lastUpdated date changed; nothing was re-tested, so this PR does not edit content-verification.json.

Sources checked 2026-10-16

• https://www.prisma.io/docs/postgres/import-from-existing-database (the link target): create the database, pg_dump the source, pg_restore the file; Prisma Postgres runs PostgreSQL 17, so pg_dump --version and pg_restore --version must report 17.x, and a PostgreSQL 17 pg_dump cannot dump a PostgreSQL 18 server.
• https://www.prisma.io/docs/prisma-postgres/import-from-existing-database-postgresql#prerequisites: "Moving from PostgreSQL 18 or later into Prisma Postgres requires a separate downgrade-compatible migration process."

Checks

• Prettier 3.9.9 with the repo's .prettierrc, with prettier-plugin-prisma 5.0.0 loaded from a separate install because this checkout has no dependencies installed: both files pass.
• Both files compile with @mdx-js/mdx 2.3.0 and remark-gfm.
• node scripts/verification.mjs passes.
• npm run build was not run locally; the external links are not covered by the internal link check.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dataguide	Ready	Preview	Oct 16, 2026 10:04am UTC

[prisma-gizmo]

✅ Gizmo reviewed db59b08 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR adds a pointer to Prisma's PostgreSQL import guide at the end of the PrismaOutlinks block in two PostgreSQL guides, so readers who set up a local PostgreSQL server learn how to move it to Prisma Postgres when it needs to be reachable elsewhere.

What changed

• 04-setting-up-a-local-postgresql-database.mdx:593 — a paragraph after the existing Prisma ORM outlink in the "Creating a role and a database" section, linking to importing an existing database into Prisma Postgres and noting the PostgreSQL 17 tool requirement and the separate path for PostgreSQL 18 servers, which this guide installs.
• 06-connecting-to-postgresql-databases.mdx:120 — the same pointer after the conclusion, framed for readers whose local development database moves to a hosted server.

How it fits the codebase

• Both additions are plain paragraphs inside the existing PrismaOutlinks blocks, matching how the other ~70 blocks in content/ handle Prisma-docs pointers. The exporter treats PrismaOutlinks as removable promotional material (mdx-to-markdown.mjs lists it in DROPPED), so the paragraphs appear on the HTML pages only, not in the .md exports, llms.txt, or the search index — the intended behavior for this component.
• The version caveats are accurate: the linked import page requires PostgreSQL 17 pg_dump/pg_restore, and the Prisma Postgres import prerequisites state that moving from PostgreSQL 18 or later needs a separate downgrade-compatible process. The 04 guide indeed installs PostgreSQL 18, so the qualification is placed where it matters.
• Per CONTRIBUTING.md, lastUpdated is only for re-tested articles; these additions add no runnable commands, so leaving content-verification.json and frontmatter untouched is correct.

[github-actions]

This PR changes the following pages (Vercel Preview Deploy links):

• /dataguide/postgresql/setting-up-a-local-postgresql-database (currently)
• /dataguide/postgresql/connecting-to-postgresql-databases (currently)

(Note that links will only be valid after Vercel preview deploy succeeded)

[gregory-boch-prisma]

@prisma-gizmo review

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No Gizmo finding is open and the head commit has been reviewed. Approving.