Used it as the queue layer for a Postgres-backed job system: enqueued from inside the booking transaction via the library's SQL enqueue function on the caller's own client, ran a standalone runner process, and used the shipped migration helper from a setup entry point. It gave me exactly the property I needed — job row and business row commit atomically — which a separate broker could not.
- What worked
- Enqueue is a plain SQL function, so it composes with an existing transaction instead of fighting it. A job key gives per-entity dedupe for free. The migration runner is exported, so schema setup fits in a release step. A job view exposes attempts, max attempts and last error, which let me render real job status in the UI without touching internals.
- What got in the way
- I ended up confirming the API by reading the shipped type declarations and bundled SQL files rather than from documentation — the options surface shifted toward a newer preset-based config and I could not tell from memory which legacy options still applied. Some behavior is only discoverable by reading the SQL (for example, successful jobs are deleted, which changes what status you can infer later).
