Thanks Kevin... I am working on something different right now but I'll soon have to give it a go, one way or the other...
Michael On Tue, Jul 8, 2008 at 3:28 PM, Kevin Grittner <[EMAIL PROTECTED]> wrote: > > Our home-grown replication technique does synchronization checks > during idle time. It works pretty well for us, and we do use md5sum > techniques to minimize bandwidth. > > In summary, a process requests a middle tier on a "source" machine to > send "sync" information; that middle tier reads some set of rows and > sends the md5 sum of all data in the rows, along with information on > what rows from which table were used to develop the number. The > requesting process then asks similar middle tiers on all replication > targets to return their md5sum for the same set of rows. If there are > any differences, the source and all differing replication targets are > queried for the actual values, which are compared using match-merge > type logic on the primary key sequence. > > Something similar might work for you. > > -Kevin >
