pgpm — a Postgres Package Manager

A modern CLI for modular PostgreSQL development.

pgpm is a focused command-line tool for PostgreSQL database migrations and package management. It provides the core functionality for managing database schemas, migrations, and module dependencies.

✨ Features

- 📦 Postgres Module System — Reusable, composable database packages with dependency management, per-module plans, and versioned releases
- 🔄 Deterministic Migration Engine — Version-controlled, plan-driven deployments with rollback support and idempotent execution enforced by dependency and validation safeguards.
- 📊 Recursive Module Resolution — Recursively resolves database package dependencies (just like npm) from plan files or SQL headers, producing a reproducible cross-module migration graph.
- 🏷️ Tag-Aware Versioning - Deploy to @tags, resolve tags to changes, and reference tags across modules for coordinated releases
- 🐘 Portable Postgres Development — Rely on standard SQL migrations for a workflow that runs anywhere Postgres does.
- 🚀 Turnkey Module-First Workspaces — pgpm init delivers a ready-to-code Postgres workspace with CI/CD, Docker, end-to-end testing, and modern TS tooling.

🚀 Quick Start

$3

``bash


Install pgpm globally

npm install -g pgpm

Start local Postgres (via Docker) and export env vars

pgpm docker start
eval "$(pgpm env)"
`

> Tip: Already running Postgres? Skip the Docker step and just export your PG* vars.

---

$3

`bash


1. Create a workspace

pgpm init workspace
cd my-app

2. Create your first module

pgpm init
cd packages/your-module

3. Install a package

pgpm install @pgpm/faker

4. Deploy everything

pgpm deploy --createdb --database mydb1
psql -d mydb1 -c "SELECT faker.city('MI');"
> Ann Arbor
`

🛠️ Commands

$3

- pgpm init - Initialize a new module
- pgpm init workspace - Initialize a new workspace

$3

- pgpm docker start - Start PostgreSQL container (via Docker)
- pgpm docker stop - Stop PostgreSQL container
- pgpm env - Print PostgreSQL environment variables for shell export

$3

- pgpm deploy - Deploy database changes and migrations
- pgpm verify - Verify database state matches expected migrations
- pgpm revert - Safely revert database changes

$3

- pgpm migrate - Comprehensive migration management
- pgpm migrate init - Initialize migration tracking
- pgpm migrate status - Check migration status
- pgpm migrate list - List all changes
- pgpm migrate deps - Show change dependencies

$3

- pgpm install - Install database modules as dependencies
- pgpm extension - Interactively manage module dependencies
- pgpm tag - Version your changes with tags

$3

- pgpm plan - Generate deployment plans for your modules
- pgpm package - Package your module for distribution

$3

- pgpm add - Add a new database change
- pgpm remove - Remove a database change
- pgpm export - Export migrations from existing databases
- pgpm clear - Clear database state
- pgpm kill - Clean up database connections
- pgpm analyze - Analyze database structure
- pgpm rename - Rename database changes
- pgpm admin-users - Manage admin users
- pgpm cache clean - Clear cached template repos used by pgpm init
- pgpm update - Install the latest pgpm version from npm

💡 Common Workflows

$3

`bash


1. Create workspace

pgpm init workspace
cd my-app

2. Create your first module

pgpm init
cd packages/new-module

3. Add some SQL migrations to sql/ directory

pgpm add some_change

4. Deploy to database

pgpm deploy --createdb
`

🧰 Templates, Caching, and Updates

- pgpm init now scaffolds workspaces/modules from https://github.com/constructive-io/pgpm-boilerplates.git using create-gen-app with a one-week cache (stored under ~/.pgpm/cache/repos). Override with --repo, --from-branch, and --template-path, or use a local template path.
- Run pgpm cache clean to wipe the cached boilerplates if you need a fresh pull.
- The CLI performs a lightweight npm version check at most once per week (skipped in CI or when PGPM_SKIP_UPDATE_CHECK is set). Use pgpm update to upgrade to the latest release.

$3

`bash


1. Navigate to your module

cd packages/your-module

2. Install a package

pgpm install @pgpm/faker

3. Deploy all installed modules

pgpm deploy --createdb --database mydb1
psql -d mydb1 -c "SELECT faker.city('MI');"
> Ann Arbor
`

$3

`bash


1. Install workspace dependencies

pnpm install

2. Enter the packages/

cd packages/yourmodule

3. Test the module in watch mode

pnpm test:watch
`

$3

#### pgpm deploy

Deploy your database changes and migrations.

`bash


Deploy to selected database

pgpm deploy

Create database if it doesn't exist

pgpm deploy --createdb

Deploy specific package to a tag

pgpm deploy --package mypackage --to @v1.0.0

Fast deployment without transactions

pgpm deploy --fast --no-tx
`

#### pgpm verify

Verify your database state matches expected migrations.

`bash


Verify current state

pgpm verify

Verify specific package

pgpm verify --package mypackage
`

#### pgpm revert

Safely revert database changes.

`bash


Revert latest changes

pgpm revert

Revert to specific tag

pgpm revert --to @v1.0.0
`

$3

#### pgpm migrate

Comprehensive migration management.

`bash


Initialize migration tracking

pgpm migrate init

Check migration status

pgpm migrate status

List all changes

pgpm migrate list

Show change dependencies

pgpm migrate deps
`

$3

#### pgpm install

Install pgpm modules as dependencies.

`bash


Install single package

pgpm install @pgpm/base32

Install multiple packages

pgpm install @pgpm/base32 @pgpm/faker
`

#### pgpm extension

Interactively manage module dependencies.

`bash
pgpm extension
`

#### pgpm tag

Version your changes with tags.

`bash


Tag latest change

pgpm tag v1.0.0

Tag with comment

pgpm tag v1.0.0 --comment "Initial release"

Tag specific change

pgpm tag v1.1.0 --package mypackage --changeName my-change
`

$3

#### pgpm plan

Generate deployment plans for your modules.

`bash
pgpm plan
`

#### pgpm package

Package your module for distribution.

`bash


Package with defaults

pgpm package

Package without deployment plan

pgpm package --no-plan
`

$3

#### pgpm export

Export migrations from existing databases.

`bash
pgpm export
`

#### pgpm kill

Clean up database connections and optionally drop databases.

`bash


Kill connections and drop databases

pgpm kill

Only kill connections

pgpm kill --no-drop
`

⚙️ Configuration

$3

pgpm uses standard PostgreSQL environment variables (PGHOST, PGPORT, PGDATABASE, PGUSER, PGPASSWORD).

Quick setup (recommended):
`bash
eval "$(pgpm env)"
`

Manual setup (if you prefer):
`bash
export PGHOST=localhost
export PGPORT=5432
export PGDATABASE=myapp
export PGUSER=postgres
export PGPASSWORD=password
`

Supabase local development:
`bash
eval "$(pgpm env --supabase)"
`

Getting Help

$3

`bash


Global help

pgpm --help

Command-specific help

pgpm deploy --help
pgpm tag -h
`

$3

Most commands support these global options:

- --help, -h - Show help information
- --version, -v - Show version information
- --cwd

- Set working directory

---

Education and Tutorials

1. 🚀 Quickstart: Getting Up and Running
Get started with modular databases in minutes. Install prerequisites and deploy your first module.

2. 📦 Modular PostgreSQL Development with Database Packages
Learn to organize PostgreSQL projects with pgpm workspaces and reusable database modules.

3. ✏️ Authoring Database Changes
Master the workflow for adding, organizing, and managing database changes with pgpm.

4. 🧪 End-to-End PostgreSQL Testing with TypeScript
Master end-to-end PostgreSQL testing with ephemeral databases, RLS testing, and CI/CD automation.

5. ⚡ Supabase Testing
Use TypeScript-first tools to test Supabase projects with realistic RLS, policies, and auth contexts.

6. 💧 Drizzle ORM Testing
Run full-stack tests with Drizzle ORM, including database setup, teardown, and RLS enforcement.

7. 🔧 Troubleshooting
Common issues and solutions for pgpm, PostgreSQL, and testing.

Related Constructive Tooling

$3

* pgsql-test: 📊 Isolated testing environments with per-test transaction rollbacks—ideal for integration tests, complex migrations, and RLS simulation.
* supabase-test: 🧪 Supabase-native test harness preconfigured for the local Supabase stack—per-test rollbacks, JWT/role context helpers, and CI/GitHub Actions ready.
* graphile-test: 🔐 Authentication mocking for Graphile-focused test helpers and emulating row-level security contexts.
* pg-query-context: 🔒 Session context injection to add session-local context (e.g., SET LOCAL) into queries—ideal for setting role, jwt.claims, and other session settings.

$3

* pgsql-parser: 🔄 SQL conversion engine that interprets and converts PostgreSQL syntax.
* libpg-query-node: 🌉 Node.js bindings for libpg_query, converting SQL into parse trees.
* pg-proto-parser: 📦 Protobuf parser for parsing PostgreSQL Protocol Buffers definitions to generate TypeScript interfaces, utility functions, and JSON mappings for enums.
* @pgsql/enums: 🏷️ TypeScript enums for PostgreSQL AST for safe and ergonomic parsing logic.
* @pgsql/types: 📝 Type definitions for PostgreSQL AST nodes in TypeScript.
* @pgsql/utils: 🛠️ AST utilities for constructing and transforming PostgreSQL syntax trees.
* pg-ast: 🔍 Low-level AST tools and transformations for Postgres query structures.

$3

* launchql/server: ⚡ Express-based API server powered by PostGraphile to expose a secure, scalable GraphQL API over your Postgres database.
* launchql/explorer: 🔎 Visual API explorer with GraphiQL for browsing across all databases and schemas—useful for debugging, documentation, and API prototyping.

$3

* launchql/s3-streamer: 📤 Direct S3 streaming for large files with support for metadata injection and content validation.
* launchql/etag-hash: 🏷️ S3-compatible ETags created by streaming and hashing file uploads in chunks.
* launchql/etag-stream: 🔄 ETag computation via Node stream transformer during upload or transfer.
* launchql/uuid-hash: 🆔 Deterministic UUIDs generated from hashed content, great for deduplication and asset referencing.
* launchql/uuid-stream: 🌊 Streaming UUID generation based on piped file content—ideal for upload pipelines.
* launchql/upload-names: 📂 Collision-resistant filenames utility for structured and unique file names for uploads.

$3

* pgpm: 🖥️ PostgreSQL Package Manager for modular Postgres development. Works with database workspaces, scaffolding, migrations, seeding, and installing database packages.
* @launchql/cli: 🖥️ Command-line toolkit for managing LaunchQL projects—supports database scaffolding, migrations, seeding, code generation, and automation.
* constructive-io/constructive-gen: ✨ Auto-generated GraphQL mutations and queries dynamically built from introspected schema data.
* @launchql/query-builder: 🏗️ SQL constructor providing a robust TypeScript-based query builder for dynamic generation of SELECT, INSERT, UPDATE, DELETE, and stored procedure calls—supports advanced SQL features like JOIN, GROUP BY`, and schema-qualified queries.
* @launchql/query: 🧩 Fluent GraphQL builder for PostGraphile schemas. ⚡ Schema-aware via introspection, 🧩 composable and ergonomic for building deeply nested queries.

Credits

🛠 Built by the Constructive team — creators of modular Postgres tooling for secure, composable backends. If you like our work, contribute on GitHub.

Disclaimer

AS DESCRIBED IN THE LICENSES, THE SOFTWARE IS PROVIDED "AS IS", AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND.

No developer or entity involved in creating this software will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of the code, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value.