←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.265s | source
Show context
polote ◴[10 Jul 25 20:38 UTC] No.44525307[source]▶
Rls and triggers dont scale either
replies(2): >>44525677 #>>44525805 #
Spivak ◴[10 Jul 25 21:26 UTC] No.44525805[source]▶
Neither do foreign keys the moment you need to shard. Turns out that there's no free lunch when you ask your database to do "secret extra work" that's supposed to be transparent-ish to the user.
replies(1): >>44526573 #
1. mulmen ◴[10 Jul 25 22:49 UTC] No.44526573[source]▶
Does that only apply when you need to shard within tenants?

If each tenant gets an instance I would call that a “shard” but in that pattern there’s no need for cross-shard references.

Maybe in the analytics stack but that can be async and eventually consistent.