Workflow
How it works
Preview, strategy selection, controlled execution and verification — the four steps behind every pgArchiMigrator change.
Back to product overviewWorkflow
Define the change. Make risk visible.
A single schema request becomes a traceable operation that moves through preview, strategy selection, controlled execution, and verification.
Trust layer Every step is visible and traceable
01 / CONNECT
Connect
Define your PostgreSQL environment with secure connectivity and minimum-privilege checks.
02 / PREVIEW
Preview
Inspect the SQL, selected strategy, and pre-flight warnings before any database write.
03 / ROUTE
Route
Let operation type, table size, and type compatibility determine the lowest-cost safe strategy.
04 / VERIFY
Execute and verify
Follow lock signals, checkpoints, and the audit trail in one operational flow.
Automatic strategy selection
It does not use the same method for every change.
pgArchiMigrator selects the safest, lowest-cost path from three execution strategies based on the nature of the change.
Direct DDL
Direct execution for PostgreSQL metadata operations that are fast and safe.
Safe path
Expand & Backfill
Controlled, batched, and observable progress across large data sets.
Safe path
Shadow Table
A logical-replication shadow-table path for the most disruptive changes.
Safe path
Downloadable resources
See the decision engine at a glance.
An infographic on how the decision engine routes every schema change, plus the v2.0 quick reference cheatsheet.
Quick reference cheatsheet
Quick reference cheatsheet
Install commands, CLI commands, the operation-to-strategy table, roles and dashboard shortcuts on one page.
Download cheatsheet (PNG)
Free and open source
See your next schema change before it happens.
Review the source, try v2.0.0 with Docker or a one-line installer, and bring pgArchiMigrator into your PostgreSQL operations workflow.
Download free from GitHub