🌕 Postgres LISTEN/NOTIFY 無法擴展
➤ 高並發環境下 LISTEN/NOTIFY 的效能限制
https://www.recall.ai/blog/postgres-listen-notify-does-not-scale
Recall.ai 在運行其會議記錄服務時,發現 Postgres 數據庫在面對大量同時寫入請求時出現了效能瓶頸。問題的根源在於 Postgres 的 LISTEN/NOTIFY 功能,當在事務期間發出 NOTIFY 查詢時,會鎖定整個數據庫,導致事務串行化,進而降低了系統的整體吞吐量和可用性。最終,他們建議在需要高擴展性的情況下避免使用 LISTEN/NOTIFY 功能。
+ 哇,這真是個重要的發現!我們也使用 Postgres,需要注意避免這個陷阱。
+ 聽起來像是在大規模應用中需要仔細考慮資料庫設計和功能選擇的案例。
#數據庫效能 #Postgres #LISTEN/NOTIFY
Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

🎉 Breaking news: #Postgres has a "LISTEN/NOTIFY" feature that didn't quite make it as the life of the party! 🎈NewRecall.ai discovers that it doesn’t "scale," a shocking revelation akin to discovering water is wet 💧. Just another day in the thrilling world of #desktop #SDKs and #meeting #bots. 💤
https://www.recall.ai/blog/postgres-listen-notify-does-not-scale #LISTEN #NOTIFY #NewRecall #AI #scaling #issues #HackerNews #ngated
Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

Don’t miss out on all the great talks and networking at PGConf NYC 2025! Get your ticket today!

https://2025.pgconf.nyc/tickets/

@PostgreSQL #postgres #conference

Today I managed to write a #Postgres query using 2 CTEs and a window function to delete some duplicate values (which should have been prevented by a proper unique constraint..) with only a tiny peek into the docs (I forgot the name of the `row_number()` function).

👁️ Watch Lukas Fittl’s (@lukas) talk from #PosetteConf 2025 “Best Practices for Tuning Slow #Postgres Queries. 🐢

https://youtu.be/ng6dKtrHAtE

#postgresql #databases #community

We’re going to take “A Look at the Elephant’s Trunk - PostgreSQL 18” with Magnus Hagander at PGConf NYC 2025!

https://postgresql.us/events/pgconfus2025/sessions/session/2095-a-look-at-the-elephants-trunk-postgresql-18/

@PostgreSQL #postgres #conference

Education and advocacy are top priorities for our Diversity Committee. Click the link below to find out more!

https://postgresql.us/diversity/

#PostgreSQL #postgres #diversity #inclusion

We want to be sure everyone who attends PGConf NYC 2025 has the best experience possible. Click below to find out how we are handling accessibility and accommodation:

https://2025.pgconf.nyc/inclusion/

@PostgreSQL #postgres #conference

×

The PgUS Diversity Committee works hard to ensure that our community is safe and welcoming to everyone! How do we do that? Click the link below for more info!

https://postgresql.us/diversity/

#PostgreSQL #postgres #diversity #inclusion