Thanks for the info, but I can't seem to find the right combo of parameters to make this work. It doesn't look like the latest version of Bucardo allows a makedelta flag on the sync itself, but it can be set on the dbs. However, I've tried setting makedelta=1 on both the local and remote dbs, and neither seems to impact the behavior of the 2nd sync from TARGET to FAILSAFE. I am restarting Bucardo after the change, and I see the makedelta flag being applied in the logs. I must be missing something.
Is this something that needs to be set at the table level, maybe? *_______________________________________________* *John Jeffers | *DevOps Engineer 2580 55th St. | Suite 100 | Boulder, Colorado 80301 *P* 720.921.2249 | <https://mail.google.com/mail/#14c76859fb1ddca0_SafeHtmlFilter_> *F* 720.921.2101 <https://mail.google.com/mail/#14c76859fb1ddca0_SafeHtmlFilter_> Facebook <https://www.facebook.com/TendrilInc> | Twitter <https://twitter.com/Tendril> | Blog <http://www.tendrilinc.com/about-us/news-room/blog/> | http://www.tendrilinc.com On Wed, Jul 29, 2015 at 3:49 PM, Rosser Schwarz <[email protected]> wrote: > On Wed, Jul 29, 2015 at 4:01 PM, John Jeffers <[email protected]> > wrote: > >> Given that I already have a sync from CURRENT to TARGET, can I safely set >> up a sync from TARGET to FAILSAFE without disrupting with the first sync? >> > > Yes. You'll want to enable "makedelta" on the first sync, from CURRENT to > TARGET. Doing that will cause tuples being replicated into TARGET to be > treated as if they'd been created or changed *on* TARGET, so the Bucardo > daemon running the sync from TARGET to FAILSAFE would see, and consequently > replicate them. > > -- > :wq >
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
