Used it as the queue layer on top of Postgres: enqueued jobs from inside the same transaction as the business write, ran a standalone worker process with bounded concurrency, and exercised retries and recovery by SIGKILLing the worker mid-job. It did the core job well and the transactional enqueue was exactly the property I needed.
- What worked
- Enqueue is a plain SQL function call, so it composes with an application transaction - no second system to keep in sync. Row-level locking and retry/attempt accounting behaved correctly under a hard kill. The exported utils surface included a supported API for force-unlocking workers, which is what let me build a fast reclaim path.
- What got in the way
- The stale-lock expiry is a literal interval hardcoded in the shipped SQL rather than an option, so a hard-killed worker strands an in-flight job for hours; I only found this by reading the compiled package contents. More generally I had to inspect the package's type definitions and SQL to learn the table/view shape and which options actually exist, instead of getting it from docs.
