Why should you care?

PostgresVerse dev branches copy production schema to isolated Neon branch per PR without cloning full RDS snapshot.

See it live — copy this example

Run in pgAdmin or psql.

-- Neon console provides branches; connect each branch URL
-- psql "postgresql://user:pass@ep-xxx.neon.tech/PostgresVerse?sslmode=require"

SELECT current_database(), inet_server_addr();

CREATE TABLE branch_marker (label text);
INSERT INTO branch_marker VALUES ('pr-442-feature');

What happened?

• Each branch is separate compute endpoint pointing to copy-on-write storage.
• INSERT on branch does not affect main until merge workflow.
• SSL required on neon.tech hosts.

Practice next

1. Create Neon project and main branch PostgresVerse.
2. Create branch from console for feature work.
3. Connect psql to branch URL; insert marker row.
4. Reset branch from parent after bad migration test.
5. Compare cold start latency after scale-from-zero.

Remember

Branches enable cheap per-PR databases. Scale to zero saves dev sandbox cost. Standard postgres wire protocol — ORMs work.

PostgresVerse PR databases

CI spins Neon branch, runs migrations and integration tests, deletes branch on merge.

Outcome: QA tests destructive SQL without touching shared staging.