Limitations and Support of Listen and Notify

Learn the limitations and support for the listen and notify mechanism in PostgreSQL.

We'll cover the following

Limitations of listen and notify
Listen and notify support in drivers

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.

Get hands-on with 1400+ tech skills courses.

Part I: Preface

Introduction to PostgreSQL

Part II: Introduction to Structured Query Language

Part III: Writing SQL Queries

Business Logic

A Small Application

The SQL REPL: An Interactive Setup

Indexing in PostgreSQL

Part IV: SQL Toolbox

SQL Tools

Managing Output in SQL

Understanding Nulls

Window Functions

Relations and Joins

Part V: Data Types

Serialization and Deserialization

PostgreSQL Data Types 101

Denormalized Data Types

Part VI: Data Modeling

Object Relational Mapping and Tooling for Database Modeling

Normalization

Practical Use Case: Geonames

Modelization Anti-Patterns

Denormalization

Not Only SQL

Part VII: Data Manipulation and Concurrency Control

Another Small Application

Isolation and Locking

Computing and Caching in SQL

Triggers

Listen and Notify

Batch Update, MoMA Collection

Part VIII: PostgreSQL Extensions

What’s a PostgreSQL Extension?

Auditing Changes with hstore

Million Song Dataset

Using Trigrams for Typos

Denormalizing Tags with intarray

The Most Popular Pub Names

Geolocation with PostgreSQL

Counting Distinct Users with HyperLogLog

Appendix

Limitations and Support of Listen and Notify

Limitations of listen and notify