Oban.Notifiers.Postgres 8kb limit -- clarification?

The Oban docs state the following regarding Oban.Notifiers.Postgres:

However, it is not as scalable as other notifiers because because each notification requires a separate query and notifications can’t exceed 8kb.

What would it take to exceed this 8kb limit? What exactly is inside the notification payload? Is it the whole Oban job?

1 Like

In addition to Oban’s internal use, the notifier is available for use by other application code. All it would take is serializing a large enough map.

The most common Oban driven examples are for oban_met when it hands off the current metrics between nodes or in oban_pro when using the Relay module.

There are many notification payloads, and they’re all kept as small as possible. No notification includes the entire job data. Insert triggers, which are a very frequent notification if you don’t disable them, only include the queue name.

3 Likes

Thanks for clarifying. I was adding some debugging to investigate further and the normal payloads did look very small.