dagster-postgres
A Dagster integration for postgres
Decision gist · record as of 2026-08-14
Yes, if you are already using Dagster and need persistent, production-grade state storage. The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe choice. Install only if you have a PostgreSQL instance available and require multi-user or persistent storage; Dagster's default storage is sufficient for local development.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later (up to 3.14).
- PostgreSQL server must be accessible and configured separately.
- Low friction install with two runtime dependencies (dagster and psycopg2-binary).
License · maintenance · safety
Apache-2.0 (permissive) — Apache 2.0 licensed, permissive terms allow commercial and private use with minimal restrictions.
last release 2026-08-07 (7 days) · last repo commit 2026-08-13 · 15,996 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 11,677,987 downloads/mo, #1,370 on PyPI
Alternatives
Verify before relying
pip install dagster-postgres
import dagster_postgres
from dagster import Definitions
# Configure PostgreSQL as Dagster's backend in your definitions
# See Dagster docs for storage configuration details- Specific PostgreSQL version compatibility requirements
- Whether this package handles schema migrations automatically or requires manual setup
- Performance characteristics for large-scale asset graphs or high-frequency runs
What it is and what it does
dagster-postgres is an integration layer that allows Dagster—a cloud-native data pipeline orchestrator—to use PostgreSQL as its backing database for storing asset definitions, run history, event logs, and execution state. Rather than using Dagster's default in-memory or SQLite storage, this package lets you connect to a production PostgreSQL instance, making it suitable for multi-user environments, persistent storage across restarts, and integration with existing database infrastructure.
The package depends on dagster (the core orchestration framework) and psycopg2-binary (the PostgreSQL driver). It's designed for teams running Dagster in production who need reliable, scalable state management backed by a dedicated relational database. Installation is straightforward with low friction, and the package is actively maintained with no known security vulnerabilities.
Use it for
- Store Dagster run history and asset lineage in a shared PostgreSQL database for multi-user team environments
- Persist pipeline state across application restarts without losing execution history or asset metadata
- Integrate Dagster with existing PostgreSQL infrastructure and monitoring tools already in place
- Enable audit trails and compliance reporting by centralizing all orchestration events in a queryable database
- Scale Dagster deployments beyond single-machine limits by offloading state to a dedicated database server
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are already using Dagster and need persistent, production-grade state storage.
The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe choice. Install only if you have a PostgreSQL instance available and require multi-user or persistent storage; Dagster's default storage is sufficient for local development.
Install
dagster-postgres on PyPI
Before you install
Low friction install with two runtime dependencies (dagster and psycopg2-binary). The package is actively maintained with a recent release and no known vulnerabilities.
Requires Python 3.10 or later (up to 3.14). PostgreSQL server must be accessible and configured separately.
License in practice
Apache 2.0 licensed, permissive terms allow commercial and private use with minimal restrictions.
Quickstart
pip install dagster-postgres
import dagster_postgres
from dagster import Definitions
# Configure PostgreSQL as Dagster's backend in your definitions
# See Dagster docs for storage configuration detailsVerify before relying
- Specific PostgreSQL version compatibility requirements
- Whether this package handles schema migrations automatically or requires manual setup
- Performance characteristics for large-scale asset graphs or high-frequency runs
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <3.15,>=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesdagsterpsycopg2-binary |
| Maintenance | Actively maintained 7 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 11,677,987 / month, #1,370 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: dagster_postgres-0.29.17-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “dagster postgres integration”
- dagster-postgresConnects Dagster data pipelines to PostgreSQL for asset storage,…
- dagster-prometheusIntegrates Prometheus metrics collection and export into Dagster data…
- dagster-slingIntegrates Sling ETL/ELT tasks into Dagster data pipelines, enabling…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also dagster · dagster-cloud-cli · dagster-webserver · dagster-docker · dagster-dg-core · dagster-rest-resources · dagster-gcp · dagster-graphql · dagster-pyspark · pipestat