That is, if the queue overflows what you should do is drop the payloads and condense all the messages for a given class into a single notification for that class with "unknown payload". That way if a cache which wants to invalidate specific objects gets a queue overflow condition then at least it knows it should rescan the original data and rebuild the cache and not just serve invalid data.
That's far more complicated than throwing an error and it discards user payload information. Let the error indicate a rescan is needed.
-- Andrew Chernow eSilo, LLC every bit counts http://www.esilo.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
