Supported operations

Capabilities

Twelve supported PostgreSQL schema operations plus whole-database migration, each evaluated against its own risk profile.

Back to product overview

Supported operations

Twelve schema operations. One trust model.

From everyday DDL needs to table partitioning and major type conversions, each operation is evaluated against its own risk profile and routed through the same strategy engine.

Explore the source code
01Verified
ADD_COLUMN

Add a column

02Verified
DROP_COLUMN

Drop a column

03Verified
ALTER_COLUMN_TYPE

Change a column type

04Verified
ADD_INDEX

Add an index

05Verified
DROP_INDEX

Drop an index

06Verified
SET_NOT_NULL

Apply NOT NULL

07Verified
ADD_CONSTRAINT

Add a constraint

08Verified
RENAME_COLUMN

Rename a column

09Verified
RENAME_TABLE

Rename a table

10Verified
ADD_FOREIGN_KEY

Add a foreign key

11Verified
ADD_GENERATED_COLUMN

Add a generated column

12Verified
PARTITION_TABLE

Partition a table

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.

SOURCE SCHEMA/CHANGE REQUEST/SAFE TARGET
S1

Direct DDL

Direct execution for PostgreSQL metadata operations that are fast and safe.

Safe path

S2

Expand & Backfill

Controlled, batched, and observable progress across large data sets.

Safe path

S3

Shadow Table

A logical-replication shadow-table path for the most disruptive changes.

Safe path

New in v2.0.0

Move a whole database, not just a schema.

Database Migration is a second mode next to zero-downtime schema migration: it moves schema and data to a different host, a different cloud provider or a newer PostgreSQL version, built on PostgreSQL's own native logical replication.

D1

Structured connections

Host, port, username, password and database as separate fields instead of a raw connection string.

D2

Schema and table picker

Real schemas and tables listed from the source, with a read-only check against the target before anything starts.

D3

Row-for-row validation

A job only reports itself ready after its data is validated row for row against the source.

D4

Retry with review

Retrying a failed job shows exactly what will be reused, with an editable replication address and no password re-exposed.

Cutover stays yours: pgArchiMigrator prepares and validates the target, but repointing application traffic remains a separate, deliberate step.

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