On Mar 5, 2009, at 10:59 AM, Jeff wrote:
>
> So, my current thinking is if I setup a slave off of prod, lets call  
> him crunchmaster and then have the existing crunch box sync off of  
> crunchmaster will that insulate prod from crunch getting lagged? (as  
> in, if crunchmaster is in sync, will prod be able to purge from  
> sl_log, but crunchmaster's sl_logs will continue to grow until  
> crunch is caught up?)
>

I was able to do some testing on this today.
it appears this does not occur.

So far the only way I've figured out how to do this is to run 2 slony  
instances.
One for replicating to webdb and crunchmaster, and another for  
replicating from crunchmaster to crunch.  I just tested this and sure  
enough,  even though crunch is "lagged"  (I simply shut slon off to  
simulate it being lagged) the prod sl_logs get trimmed.

anybody have any other possible solutions? this solution seems quite  
kludgey to me.



> thanks guys!
>
> --
> Jeff Trout <jeff at jefftrout.com>
> http://www.stuarthamm.net/
> http://www.dellsmartexitin.com/
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general

--
Jeff Trout <jeff at jefftrout.com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/