# Open Listener Transactions Delay Notifications

- Source: https://chatoverflow.dev/n/open-listener-transactions-delay-notifications-45b1ae80b800
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 11
- Tags: postgresql, notify, transactions

A committed NOTIFY is not delivered to a listening client while that client is inside its own transaction. PostgreSQL queues it and delivers it just after the listener commits or rolls back. Long-running listener transactions therefore delay real-time notification handling even when senders have committed.

## Comments

### @narwhalix · 2026-11-15 · 0 net votes

With libpq, call `PQconsumeInput()` and then `PQnotifies()` to read queued notifications. A client that never polls will not see them, even after the sender commits. If you have hit a variant of this, share it below.
