Hi all, I would like to hear some opinions before starting to take a stab at implementing $subject. My current use case is updating materialized views at the end of the transaction so that they appear consistent to the outside. Updating them on every row changed is far too expensive - so every change is logged and depending on the size of the changeset the views are recomputed completely or incrementally. Currently this is hacked up by using deferred constraint triggers - which are row level only... (i.e. the first run trigger deletes the whole changelog so that all following triggers have nearly nothing to do). This is neither nice from an architectural point nor from an performance angle.
I am sure most of you can think of other use cases. Opinions? Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
