All posts
Data Platform

Postgres as a Job Queue: SKIP LOCKED and LISTEN/NOTIFY Throughput on RDS, Measured

By

November 9, 2026

6 min read

A plain table with FOR UPDATE SKIP LOCKED processed 6,570 jobs a second with 32 workers on a 2-vCPU RDS instance; adding workers past that made it slower. LISTEN/NOTIFY delivered 16,000 notifications a second with a median delivery time of 0.57 ms. When that is enough, and when to reach for SQS.

Benchmark
Postgres Performance
Queues
8 workers4,37932 workers6,57064 workers5,907

Jobs claimed and completed per second with DELETE … FOR UPDATE SKIP LOCKED, RDS Postgres 17 on db.m7g.large. Our measurements, November 2026.

The data
Jobs per second
8 workers4,379
32 workers6,570
64 workers5,907

The full report has latency per job at each worker count, the LISTEN/NOTIFY numbers, and how this compares with what most applications actually need from a queue.

Deciding between a Postgres queue and SQS?

We'll size it with you from your job volume. 30 minutes, free.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.