# PostgreSQL as a Workflow Engine: Building Reliable … | Percona Community

**URL:** <https://forums.percona.com/t/postgresql-as-a-workflow-engine-building-reliable-percona-community/41269>\
**Category:** Community website\
**Created:** [September 16, 2026, 5:04pm UTC](https://forums.percona.com/t/postgresql-as-a-workflow-engine-building-reliable-percona-community/41269 "2026-09-16T17:04:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [September 16, 2026, 5:04pm UTC](https://forums.percona.com/t/postgresql-as-a-workflow-engine-building-reliable-percona-community/41269/1 "2026-09-16T17:04:26Z")

</div>

Every document-processing system I have worked on arrives at the same shape. Something uploads a file, something else has to read it, run it through an extraction or inference step that takes seconds to minutes, and store a result. The work is slow, it fails sometimes, and the answer has to be auditable afterwards.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/09/16/postgresql-workflow-engine-long-running-jobs/](https://percona.community/blog/2026/09/16/postgresql-workflow-engine-long-running-jobs/)