<div dir="ltr">Updating a materialized view in my case. It should only update when 2-3 of our 30+ tables get new data,
whichfor those is kind of rare. Not having such a trigger means I will have to call it in each usage in the code and
hopefuture maintainers don't forget it. This is why I postponed migrating the one search query where materialized views
wouldbe useful, because it's heavy.<br /></div><div class="gmail_extra"><br /><div class="gmail_quote">2015-05-27 13:42
GMT+03:00Marko Tiikkaja <span dir="ltr"><<a href="mailto:marko@joh.to"
target="_blank">marko@joh.to</a>></span>:<br/><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px#ccc solid;padding-left:1ex"><span class="">On 5/27/15 12:39 PM, Jordan Gigov wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I found myself
inneed of triggers that are run only once per transaction,<br /> rather than per row or statement within the
transaction.Meaning it will<br /> always be deferred and never called twice for the same transaction.<br
/></blockquote><br/></span> What's the use case?<span class="HOEnZb"><font color="#888888"><br /><br /><br /> .m<br
/></font></span></blockquote></div><br/></div>
