Skip to content

docs: add steps for moving data from dev to prod branch#4940

Open
dhanushreddy291 wants to merge 2 commits into
neondatabase:mainfrom
dhanushreddy291:update-docs/misc
Open

docs: add steps for moving data from dev to prod branch#4940
dhanushreddy291 wants to merge 2 commits into
neondatabase:mainfrom
dhanushreddy291:update-docs/misc

Conversation

@dhanushreddy291

@dhanushreddy291 dhanushreddy291 commented May 20, 2026

Copy link
Copy Markdown
Contributor

@vercel

vercel Bot commented May 20, 2026

Copy link
Copy Markdown

@dhanushreddy291 is attempting to deploy a commit to the neondatabase Team on Vercel.

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented May 20, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
neon-next Ready Ready Preview, Comment May 20, 2026 1:06pm

Request Review

@danieltprice danieltprice marked this pull request as ready for review May 21, 2026 21:51
@danieltprice danieltprice self-requested a review as a code owner May 21, 2026 21:51

1. Export selected tables from the development branch
2. Review or modify the exported data
3. Import the data into production with a conflict strategy, such as `INSERT ... ON CONFLICT`

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if this should reference --inserts --on-conflict-do-nothing or how to clarify the upsert advice since it's near the pg_dump example that doesn't allow generating it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @philip, have updated it

Previously, the main focus was on non-collision cases / smaller datasets, so I thought this check wasn’t necessary and only a simple note sentence would suffice.

Since adding it doesn’t affect the existing SQL code, I’ve included it now.

@philip philip force-pushed the update-docs/misc branch from 5761da6 to 0de610a Compare June 4, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants