Re: Listen / Notify - what to do when the queue is full

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Listen / Notify - what to do when the queue is full
Date: 2009-11-19 01:26:18
Message-ID: 4B049EBA.6010207@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-11-19 01:26:37 Re: Listen / Notify - what to do when the queue is full
Previous Message James Pye 2009-11-19 01:20:54 Re: Python 3.1 support