> Have you tried this with newer versions? I recall discussions taking > place about automatically extending the grouping until it reaches a > second transaction. > > The main reason for increasing group size during the initial sync was to > get out of that first large copy transaction caused by Slony itself. > > > It is normally the size, by time not necessarily real work, of the > transaction being replicated that causes the problems -- although there > are cases where having several sets can also make things difficult.
As of RC2 I still had problems and resolved to rebuilding slon with "group_size = 100" explicitly set somewhere in the loop. I must say, however, I didn't not spend as much time with the options as I had previously. I'm initiating another initial sync tomorrow with a large database and I pledge to spend a little more time on this issue. regards, michael _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
