←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.455s | source
Show context
callamdelaney ◴[10 Jul 25 23:18 UTC] No.44526788[source]▶
My kneejerk reaction to the headline is ‘why would it?’.

It’s unsurprising to me that an AI company appears to have chosen exactly the wrong tool for the job.

replies(3): >>44526797 #>>44527255 #>>44528010 #
kristianc ◴[11 Jul 25 00:34 UTC] No.44527255[source]▶
Sounds like a deliberate attempt to avoid spinning up Redis, Kafka, or an outbox system early on.. and then underestimated how quickly their scale would make it blow up. Story as old as time.
replies(4): >>44527509 #>>44527547 #>>44529439 #>>44529665 #
j16sdiz ◴[11 Jul 25 01:19 UTC] No.44527509[source]▶
Kafka head of line blocking sucks.
replies(2): >>44527936 #>>44534841 #
1. LgWoodenBadger ◴[11 Jul 25 17:26 UTC] No.44534841[source]▶
Isn't this one of the things partitioning is meant to ameliorate? Either through partitions themselves, or through an appropriate partitioning strategy?