6 min read
|
Saved October 29, 2025
|
Copied!
Do you care about this?
Recall.ai faced significant performance issues with their Postgres database due to the high concurrency of NOTIFY commands used during transactions, which caused global locks and serialized commits, leading to downtime. After investigating, they discovered that the LISTEN/NOTIFY feature did not scale well under their workload of tens of thousands of simultaneous writers. They advise against using LISTEN/NOTIFY in high-write scenarios to maintain database performance and scalability.
If you do, here's more
Click "Generate Summary" to create a detailed 2-4 paragraph summary of this article.
Questions about this article
No questions yet.