postgres-impl-listen-notify

PostgreSQL LISTEN/NOTIFY sends asynchronous notifications to listening clients upon transaction commit. This Skill implements pub/sub notifications for real-time cache invalidation and client-side updates without polling.

PostgreSQL LISTEN/NOTIFY messages are transaction-bound, ensuring notifications are only sent upon transaction commit. This guarantees that listeners only receive updates for database changes that have been successfully committed.

To handle the PostgreSQL LISTEN/NOTIFY 8000-byte payload limit, this Skill implements key-based data fetching. Instead of sending large payloads directly, it sends a key that clients use to fetch the full data separately.

Yes, this LISTEN/NOTIFY implementation integrates with PostgreSQL 15, 16, and 17 for cache invalidation. It delivers payloads asynchronously to listening sessions to trigger real-time updates without requiring client-side polling.

The best way to trigger job-queue wakeups in PostgreSQL without polling is using LISTEN/NOTIFY. This Skill leverages transaction-bound notification sending to asynchronously wake up job queues upon database commits.

To set up real-time user profile updates, use this LISTEN/NOTIFY implementation to listen for 'user_updated' notifications. It manages transaction-bound delivery and payload sizes to update web application UIs upon database changes.