Is this of theoretical interest (up to and including a specification/requirement) or this a practical concern (i.e. need to know when to update somebody’s dashboard widget (but the query is too slow to simply refresh on-demand)?
> On Dec 22, 2018, at 9:42 AM, Ricardo Martin Gomez <rimartingo...@hotmail.com> > wrote: > > Hi, perhaps you can use triggers for some tables. > Regards. > > Obtener Outlook para Android <https://aka.ms/ghei36> > From: Mitar <mmi...@gmail.com> > Sent: Saturday, December 22, 2018 1:21:49 AM > To: Kevin Brannen > Cc: pgsql-general@lists.postgresql.org > Subject: Re: Watching for view changes > > Hi! > > On Thu, Dec 20, 2018 at 12:54 PM Kevin Brannen <kbran...@efji.com > <mailto:kbran...@efji.com>> wrote: > Hmm, I guess I could see that as long as the DB wasn't too [write] busy, else > you'd be flooded with notifications. > > Sure. But this could be resolved by allowing notifications to be batched > together. Debounce them. So could maybe configure how often you want such > notifications and if they are more often they would be combined together into > one. > > Maybe it's a useful idea for you ... or maybe not. 😊 > > Thanks. Yes, this is one approach to do it. Hooking into every modify call at > the app level and in this way have some information what is changing. I would > prefer doing it in the database though, so that it could be independent from > the source of the change. Moreover, not all UPDATE queries really do end up > updating the data. > > > Mitar > > -- > http://mitar.tnode.com/ <http://mitar.tnode.com/> > https://twitter.com/mitar_m <https://twitter.com/mitar_m>
