Deploy and Host Postgres Migrator on Railway

Postgres Migrator is a PostgreSQL database migration tool that uses native pg_dump and pg_restore commands. It provides parallel restore capabilities for faster migrations, automatic version compatibility checking, and pre-flight validation to ensure target databases are clean before migration begins.

About Hosting Postgres Migrator

Hosting Postgres Migrator on Railway allows you to run database migrations as a service without managing infrastructure. The tool requires PostgreSQL client tools (pg_dump/pg_restore) which are included in the Docker image via the PG_VERSION build argument. Simply configure your source and target database URLs via environment variables, and the service handles the entire migration pipeline - from validation and dumping to parallel restoration. This is ideal for scheduled migrations, backup operations, or one-time database transfers between environments.

Common Use Cases

Database Backups - Automated scheduled backups from production to backup databases
Environment Cloning - Copy production data to staging/development environments for testing
Database Migrations - Move databases between hosting providers (e.g., PlanetScale to Railway) or regions with minimal downtime
Data Recovery - Quick restoration from source database to recovery targets
Multi-tenant Migrations - Parallel processing for migrating multiple tenant databases efficiently

Dependencies for Postgres Migrator Hosting

PostgreSQL Client Tools - pg_dump and pg_restore are included in the Docker image, version controlled via the PG_VERSION build argument
Source PostgreSQL Database - The database you want to migrate from
Target PostgreSQL Database - The destination database (must be empty and same major version, unless SKIP_VERSION_CHECK is enabled)

Deployment Dependencies

Implementation Details

The tool executes:

Validates both database connections and version compatibility
Checks target database is empty (pre-flight validation)
Creates compressed custom-format dump using pg_dump
Restores to target using pg_restore with optional parallel jobs
Optionally validates row counts across all tables
Cleans up temporary files automatically

Environment Variables

Build Arguments

Variable	Required	Default	Description
`PG_VERSION`	Yes	`17`	PostgreSQL major version for client tools (15, 16, or 17). Must match your database version.

Required

Variable	Required	Default	Description
`SOURCE_DATABASE_URL`	Yes	-	Source database connection string
`TARGET_DATABASE_URL`	Yes	-	Target database connection string
`PARALLEL_JOBS`	Yes	`4`	Number of parallel jobs for restore

Optional

Variable	Required	Default	Description
`NO_ACL`	No	`true`	When `true`, skips restoration of access privileges (ACLs), such as GRANT/REVOKE commands for permissions on objects
`NO_OWNER`	No	`true`	When `true`, skips restoration of object ownership (e.g., who owns tables/schemas). This omits ALTER OWNER commands in the dump file
`VALIDATE_AFTER`	No	`true`	Run validation on all tables after migration completes (set to `false` to skip)
`EXCLUDE_SCHEMAS`	No	-	Comma-separated list of schemas to exclude from the dump (e.g., `pscale_extensions` when migrating from PlanetScale)
`SKIP_VERSION_CHECK`	No	`false`	When `true`, skips the PostgreSQL major version compatibility check between source and target databases, allowing migration across different versions (e.g., PG 16 to PG 17)
`DATA_ONLY`	No	`false`	When `true`, restores only data without schema. Use when the target database already has the schema in place

Why Deploy Postgres Migrator on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Postgres Migrator on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.