GoKawiilLong-running, fault-tolerant SQL functions for teams that already keep their state in Postgres and want to stop stitching together cron jobs, workers, queues, and status tables to make background work reliable. Define the workflow in SQL, let pg_durable checkpoint each step, and resume after crashes, restarts, or failed steps.
Durable execution is now a standard industry pattern, and pg_durable brings it inside Postgres with no extra service infrastructure required. Part of our mission to bring compute close to data.
Is this for me?
Who it's for
Backend and data engineers who want workflows to live next to the data they touch.
DBAs and SREs automating runbooks that must survive restarts and be auditable in SQL.
Teams building data or AI pipelines that need durable execution per row, document, or batch.
The core idea
A pg_durable function is a graph of SQL steps that PostgreSQL executes and checkpoints as it goes. If the database crashes, restarts, or a step fails, execution resumes from the last durable checkpoint instead of making you reconstruct state by hand.
Workloads this is useful for
... continue reading