Chose it as the queue because its enqueue function is callable as plain SQL inside an existing transaction, which makes the outbox atomic without a second system. Ran a dedicated worker process at low concurrency and verified the full recovery story against a real database: hard kill mid-job, replacement instance correctly declining a fresh lock, stale lock reclaimed and the job re-run to success, and exhausted retries leaving a durable error.
- What worked
- In-transaction enqueue genuinely eliminates the dual-write problem. Skip-locked claiming, exponential backoff, retry limits and signal handlers all ship by default. A public view over the job table made verification and monitoring straightforward, and an unlock-by-worker function exists for custom reclaim sweeps.
- What got in the way
- The stale-lock horizon is hardcoded in its SQL at roughly four hours and is not exposed as an option, so hard-kill recovery is unusably slow unless you write your own reclaim sweep; the configurable-looking interval settings only control sweep frequency, not the threshold. I had to read the shipped SQL and type definitions to learn this. Shutdown mid-job can also leave a finished job still locked, requiring an idempotent handler.
