Re: Watching for view changes

Поиск
Список
Период
Сортировка
От Ricardo Martin Gomez
Тема Re: Watching for view changes
Дата
Msg-id SC1P15201MB23043ECC20218275F67BF8E6A3B90@SC1P15201MB2304.LAMP152.PROD.OUTLOOK.COM
обсуждение исходный текст
Ответ на Re: Watching for view changes  (Mitar <mmitar@gmail.com>)
Ответы Re: Watching for view changes  (Rob Sargent <robjsargent@gmail.com>)
Список pgsql-general
Дерево обсуждения
Hi, perhaps you can use triggers for some tables.
Regards.

From: Mitar <mmitar@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 <KBrannen@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/
https://twitter.com/mitar_m

В списке pgsql-general по дате отправления:

Предыдущее
От: Mark
Дата:
Сообщение: Re: Query planner / Analyse statistics bad estimate rows=1 withmaximum statistics 10000 on PostgreSQL 10.2
Следующее
От: Rob Sargent
Дата:
Сообщение: Re: Watching for view changes