| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | Kevin Brannen <KBrannen(at)efji(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Watching for view changes |
| Date: | 2018-12-22 04:21:49 |
| Message-ID: | CAKLmikM9=iJEE6zkjRtg_vWX8ECDgkngcVHcitQ6bh9A6VJLbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
On Thu, Dec 20, 2018 at 12:54 PM Kevin Brannen <KBrannen(at)efji(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitar | 2018-12-22 04:49:23 | Re: Watching for view changes |
| Previous Message | Rene Romero Benavides | 2018-12-21 23:13:53 | Re: Amazon Aurora |