←back to thread

Postgres LISTEN/NOTIFY does not scale

(www.recall.ai)
570 points davidgu | 1 comments | 07 Jul 25 14:05 UTC | HN request time: 0.308s | source
Show context
sleepy_keita ◴[11 Jul 25 01:04 UTC] No.44527431[source]▶
LISTEN/NOTIFY was always a bit of a puzzler for me. Using it means you can't use things like pgbouncer/pgpool and there are so many other ways to do this, polling included. I guess it could be handy for an application where you know it won't scale and you just want a simple, one-dependency database.
replies(3): >>44527549 #>>44528158 #>>44528472 #
1. nhumrich ◴[11 Jul 25 04:43 UTC] No.44528472[source]▶
You can setup notify to run as a trigger on an events table. The job that listens shouldn't need a pool, it's a long lived connection anyway. Now you can keep using pgbouncer everywhere else.