counterweight/hojas
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

intersting stuff

Browse source
This commit is contained in:
counterweight 2026-07-25 11:11:07 +02:00
parent c60a31d451
commit 87a7dba6ba
Signed by: counterweight
GPG key ID: 883EDBAA726BD96C
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
interesting/making-postgres-listen-notify-scale.md Normal file
View file

@ -0,0 +1,14 @@
# Making Postgres LISTEN/NOTIFY scale
https://www.dbos.dev/blog/postgres-listen-notify-scalability
This blogpost by dbos dunks on this other one (https://www.recall.ai/blog/postgres-listen-notify-does-not-scale) by recall.ai where they state that Postgres' LISTEN/NOTIFY does not scale.
The original thesis is that using LISTEN/NOTIFY kills the write throughput of the database it is working on. This is because it holds a LOCK on the entire database. They spotted the peculiarity because, even though their instance queries were all blowing up, resource usages on the metal was going down. Locks explain that.
Then the guys at dbos came in and said: well, that's true, but you can work around that easy peasy. They gave an example from their own systems. The approach is:
- Make the NOTIFY a simple pinger, not a data sender.
- Buffer notifications
- To cover for the case where there is a crash, buffer is lost and there is no NOTIFY, make the consumers also poll here in there.
To be honest, dbos points are not bad, but fucking hell aren't they way more complicated.