pglifecycle 2.0 puts PostgreSQL schema plans into pull requests

pglifecycle 2.0 beta stores PostgreSQL objects as separate YAML files, compares them with a live database and generates SQL to reconcile differences. Its GitHub Action can post drift and deployment plans without applying them. Destructive changes are withheld unless explicitly allowed. This Rust rewrite builds on a tool used at AWeber for seven years, but version 2 itself is still beta.

Gavin M. Roy / PostgreSQL · Oct 14, 2026

Why it matters

A reviewable desired schema can be easier to inspect than reconstructing state from years of migrations.

More context

Try importing a disposable database and reviewing the generated plan. The tool can also build a pg_restore archive; validate object coverage and convergence on your own schema before adopting it.

Keep in mind

The predecessor’s production history does not establish equivalent maturity for the beta rewrite.

Original read