Updating a materialized view in my case. It should only update when 2-3 of our 30+ tables get new data, which for those is kind of rare. Not having such a trigger means I will have to call it in each usage in the code and hope future maintainers don't forget it. This is why I postponed migrating the one search query where materialized views would be useful, because it's heavy.
2015-05-27 13:42 GMT+03:00 Marko Tiikkaja <ma...@joh.to>: > On 5/27/15 12:39 PM, Jordan Gigov wrote: > >> I found myself in need of triggers that are run only once per transaction, >> rather than per row or statement within the transaction. Meaning it will >> always be deferred and never called twice for the same transaction. >> > > What's the use case? > > > .m >
