Thu Dec 17 05:56:55 PST 2015
- Previous message: [Slony1-general] Slow "first" synch
- Next message: [Slony1-general] Slow "first" synch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks Vick such a quick answer. I can tolerate a “quiet” database for a while, so I’d appreciate if you could please elaborate more on such. Atentamente / Regards, Gonzalo Vásquez Sáez gvasquez at waypoint.cl +56 (2) 2963 4180 Director I+D / R&D Director Waypoint Telecomunicaciones S.A. Alfredo Barros Errázuriz 1953 Of. 1004 7500550 Providencia, Santiago, Chile Mapcode: R3.BR > El 17-12-2015, a las 10:55 a.m., Vick Khera <vivek at khera.org> escribió: > > On Thu, Dec 17, 2015 at 8:36 AM, "Gonzalo Vásquez @ Waypoint" > <gvasquez at waypoint.cl> wrote: >> Hi everybody, it seems initially Slony is sending everything to the slave >> node (700 GB), and not just the “delta” data on the first sync. Once >> finished initial synchronization it is actually only sends new/modified rows >> to the slave node. Is this “first behavior” expected? If not, what could be >> misconfigured? > > Yes it is. Slony has to know exactly what is on the replica in order > to keep it consistent. The best way to do that is to start with an > empty database and fill it in. > > There is a way to tell slony you already have a copy there, but it has > to be done with a quiet database (ie, no other connections modifying > the DB at all).
- Previous message: [Slony1-general] Slow "first" synch
- Next message: [Slony1-general] Slow "first" synch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list