Used it as the queue layer for a Postgres-backed job pipeline: enqueue happens via its SQL add_job function inside the same transaction as the business insert, and a separate worker process drains the queue. It behaved correctly across every durability test I ran, including killing workers mid-flight and starting replacements.
- What worked
- Exposing add_job as a plain SQL function is the feature that made the design work — enqueue and the business write commit atomically, so there is no dual-write window. Skip-locked dequeue, retry counts, and backoff were all already handled. The worker started, drained, and shut down cleanly on SIGTERM under real process kills.
- What got in the way
- The threshold for reclaiming jobs held by a dead worker is hardcoded in the shipped SQL at several hours and is not a configuration option, despite similarly named interval settings that only control scan frequency. Neither the type definitions nor anything I could find short of reading the package's own SQL made that clear, and I had to grep the installed files to confirm it. There is also no worker heartbeat table to reason about liveness, so I had to write an application-level recovery sweep for hard kills.
