Re: Listen / Notify - what to do when the queue is full - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id 1266344520.29919.6961.camel@jdavis
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-hackers
On Tue, 2010-02-16 at 16:02 +0000, Greg Sabino Mullane wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> 
> > * We also discussed the idea of having a NOTIFY command that 
> > would work from Primary to Standby.
> 
> Just curious, what's a use case for this?

If you have some kind of cache above the DBMS, you need to invalidate it
when a part of the database is updated. It makes sense that every reader
would want to know about the update, not just those connected to the
master.

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Matthias Brantner
Date:
Subject: Re: XQuery support
Next
From: Jeff Davis
Date:
Subject: Re: LISTEN/NOTIFY and notification timing guarantees