> > Something on the origin did something similar. It updated a row and that > update caused no single value in the row to change. As pointed out, the > resulting update on the subscriber is done so that eventual triggers there > will fire. > > We can add a configuration option, suppressing those updates, to the 2.1 > todo list. In the meantime, if that happens that much that it causes > problems for you, it may be better to fix your application. Because your > origin must suffer the same bloat. >
True the master is also going to suffer the same bloat and it makes sense to fix my application first. Thanks, Sivakumar.K
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
