Generate migrations between Postgres databases.
Use pgmig to compare the structure of two Postgres databases — a source and a target — and generate
the SQL that turns the source into the target.
pgmig connects read-only to both databases and never
runs the generated SQL for you: you review it and apply it yourself.
pgmig officially supports Postgres 14–18 — the majors currently maintained upstream — and is tested against each in CI. Other versions may work but are not tested.
Documentation: pgmig.readthedocs.io
Quick start
Say the current database has a users table, and the desired one adds an email column with a unique index:
-- current
CREATE TABLE users (id bigint PRIMARY KEY, name text NOT NULL);
-- desired
CREATE TABLE users (id bigint PRIMARY KEY, name text NOT NULL, email text NOT NULL);
CREATE UNIQUE INDEX users_email_idx ON users (email);
Print the migration SQL that makes current match desired, using uvx:
$ uvx pgmig generate \
--source postgresql://user:pass@localhost:5432/current \
--target postgresql://user:pass@localhost:5432/desired
ALTER TABLE "public"."users" ADD COLUMN "email" text NOT NULL;
CREATE UNIQUE INDEX users_email_idx ON public.users USING btree (email);
Or from Python:
import pgmig
sql = pgmig.generate(
source="postgresql://user:pass@localhost:5432/current",
target="postgresql://user:pass@localhost:5432/desired",
)
print(sql)
# ALTER TABLE "public"."users" ADD COLUMN "email" text NOT NULL;
# CREATE UNIQUE INDEX users_email_idx ON public.users USING btree (email);
Contributing
Contributions are welcome!
See CONTRIBUTING.md for details.
License
pgmig is distributed under the terms of the MIT license.
Metadata
Release files for pgmig 1.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pgmig-1.0.7.tar.gz | 761.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pgmig-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 898.8 kB
Release files / pgmig-1.0.7.tar.gz
| Download URL | pgmig-1.0.7.tar.gz |
|---|---|
| Size | 761.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d81d39a75439330d04bbb07e2563cef81af6f05fc92dc25f0d68b715fa295702
|
|
BLAKE2b-256 checksum How to use checksums |
08bf04a13f581bc184d66bb42f8e412e14e8dde9d1022ebfceb97a01674a1323
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pgmig-1.0.7-py3-none-any.whl
| Download URL | pgmig-1.0.7-py3-none-any.whl |
|---|---|
| Size | 137.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddb256884c636731a937855ec737a11f6d6f4ee1220975fe34ca245bf1c3f2c6
|
|
BLAKE2b-256 checksum How to use checksums |
4e519ba3e0705b2b574169f543317e2185aaeaafc7edc38ec8a593eee21028a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pgmig 1.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.