Postgres LISTEN/NOTIFY Actually Scales (When You Treat It Like a Wake-Up, Not a Queue)
Postgres LISTEN/NOTIFY feels magical for low-latency streaming, but naïve “NOTIFY on every row” designs can bottleneck on an exclusive queue lock during commit. Treat notifications as wake-ups, batch them, and rely on the table as the durable source of truth (with periodic polling as a backstop) to scale safely.