Ross ROSS = Recommend OSS · open-source software intelligence for agents

microsoft/pg_durable

PostgreSQL in-database durable execution observed · 2026-08-28

github.com/microsoft/pg_durable · homepage · Rust · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

82/100

  • Activity 99
  • Release rhythm 99
  • Longevity 14

Flags: no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 15.5
  • age_days: 201
  • days_rel: 10
  • days_push: 7
  • n_releases_24m: 5

Full methodology

Adoption not part of the score

2788 stars · 75 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

pg_durable is a PostgreSQL extension that provides durable execution for long-running, fault-tolerant SQL functions directly inside the database. It lets teams define workflows as graphs of SQL steps that are automatically checkpointed and resumed after crashes, restarts, or failed steps, eliminating the need for external orchestrators, cron jobs, or custom job-queue plumbing.

Use cases

  • run crash-proof background workflows directly in postgres without external orchestrators
  • build vector embedding pipelines that chunk documents and upsert into pgvector
  • replace pg_cron plus job queue tables and polling workers with durable sql functions
  • schedule maintenance runbooks that survive database restarts and are auditable in sql
  • fan out parallel sql queries and join results with automatic checkpointing
  • orchestrate external api calls like enrichment and classification from sql workflows
  • resume failed multi-step data ingestion pipelines from the last checkpoint
  • add retries and conditional branching to long-running sql jobs

When to choose

  • your state already lives in postgres and you want workflows next to the data
  • you are stitching together cron jobs, workers, queues, and status tables for background work
  • you need durable execution without deploying extra service infrastructure like containers or external orchestrators
  • you are building data or ai pipelines that need per-row, per-document, or per-batch durability
  • you are a dba or sre automating runbooks that must survive restarts and be auditable in sql

When to avoid

  • you need workflows spanning multiple heterogeneous systems beyond postgres
  • you prefer a general-purpose orchestrator with a rich ui like airflow or temporal
  • your postgres version is older than 17
  • you need language-level workflow code rather than a sql dsl

Facets

library · maturity active

database workflow-automation scheduling message-queue concurrency databases backend artificial-intelligence developer-tools windows self-hosted cloud durable-execution durable-functions durable-workflows postgresql-extension sql-dsl checkpointing crash-recovery background-worker ai-pipelines vector-embedding-pipelines pgvector workflow-orchestration retry-logic fan-out-aggregation scheduled-maintenance no-external-services azure-horizondb rust postgres-17 postgres-18 data-engineering automation postgresql linux macos docker

2 sources

Member repositories

RepositoryRoleHealth v2
microsoft/pg_durablemain82

For agents

markdown · JSON · MCP: product_card(name="microsoft/pg_durable")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem