If you're using SELECT FOR UPDATE SKIP LOCKED to build a job queue on Postgres, the tail-latency curve is a lot flatter than people expect. CockroachDB published a benchmark with P99 staying under 5ms with 100 concurrent workers on commodity hardware. Beats Redis-based queues for anything that needs transactional consistency with the rest of your writes.