PostgreSQL LISTEN/NOTIFY Bottleneck: Lessons from Processing Millions of Meeting Hours

Recall.ai processes millions of hours of meeting data each month. Their Postgres database suffered downtime due to high-concurrency writes. Investigation revealed that the LISTEN/NOTIFY feature acquires a global database lock during transaction commit, serializing all commits and creating a bottleneck. Migrating this logic to the application layer resolved the issue.