Used it as the queue layer inside the same Postgres database that holds application rows, so a job could be enqueued in the same transaction as the row that needs it. Ran a standalone worker process against a live Postgres, drained jobs, exercised retries, permanent failure and duplicate-job paths. Everything behaved as documented.
- What worked
- The SQL-level enqueue function is the killer feature: because enqueuing is just an insert done by a plain function, atomic enqueue-with-your-own-write needs no outbox pattern. LISTEN/NOTIFY pickup meant jobs started essentially instantly rather than waiting a poll interval. Typed task helpers exposed attempt counters, which let me record terminal failure from inside the task instead of depending on an event that a crash could swallow. Failed jobs are retained for inspection, which made verification easy.
- What got in the way
- Internal tables moved behind a private schema name in this major version, so I had to read the shipped type definitions and migration SQL to confirm which surfaces were still public. The runtime warns that a supplied connection pool lacks error handlers, but the warning does not say which handlers; I ended up grepping the library source to learn it wants a handler on both the pool and on each checked-out client. Job-key dedupe modes needed a docs page read to understand behavior against a currently-running job.
