apgdiff vs dbdiff

apgdiff is a free command-line tool that compares two PostgreSQL schema dump files and generates DDL statements to update an older schema or show differences. It takes an original dump and a new dump as inputs; generated SQL can be printed in the terminal or redirected to a file. The project says it can be called from batch jobs or web applications. It is written in Java and requires Java 1.6 or newer. Listed systems include Windows, Linux, Mac OS X, Solaris, and BSD, as well as other systems where Java is available. Version 2.4 is identified as the latest stable release, with binary and source ZIP downloads. Support covers selected ALTER SEQUENCE, ALTER TABLE, ALTER VIEW, COMMENT, CREATE FUNCTION, CREATE INDEX, CREATE SCHEMA, CREATE SEQUENCE, CREATE TABLE, CREATE TRIGGER, CREATE VIEW, and SET search_path statements. Other SQL statements are ignored, and an option reports ignored DDL. For CREATE TABLE column constraints, only NULL and NOT NULL are supported. The project uses the MIT License and recommends reviewing generated upgrade SQL before applying it.

DBDiff is a free, MIT-licensed tool for comparing local or remote MySQL, PostgreSQL, and SQLite databases and generating migrations from schema or data differences. It can produce SQL migrations with up and down changes, using native SQL, Flyway, Liquibase, Laravel, or custom templates. The migration runner can create, apply, roll back, check, validate, repair, and baseline migrations. Listed comparison targets include tables, views, triggers, routines, types, sequences, row-level security policies, and data. Its configuration file can specify connections, drivers, diff scope, included or ignored tables and fields, and row filters. Installation options include pre-built Windows, macOS, and Linux binaries, npm, PHAR, Docker or Podman images, and Composer source. For PostgreSQL, DBDiff also compares row-level security policies and table security flags. By default, generation stops when a migration would drop a table or column, though an option permits those changes. One documented PostgreSQL limitation is that removing or reordering enum labels may leave dependent objects that prevent an automatically generated migration from applying.