Limitations and Support of Listen and Notify

Limitations of listen and notify

It is important for an application, using the PostgreSQL notification capabilities, to miss notification events. Notifications are only sent to connected client connections.

Any queueing mechanism requires that events that are accumulated when there’s no worker connected, are kept available until the next connection. Replication is a special case of event queueing. It’s not possible to implement queueing correctly with the PostgreSQL listen and notify feature.