tail -f slon_output_for_slave.log | grep sub_set When you get output... you'll know it's done. For a more comprehensive approach (ie, monitoring the entire subscription process), take a look at the logrep section of tools/mkservice/README
Andrew On 8/6/07, Rudolf van der Leeden <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm planning to replace "dbmirror", currently used in a simple > master/slave setup.Slony seems to be the right choice and I started to > test Slony in our scenario of two nodes (master/provider node, > slave/receiver node). > It looks very good and we are now planning the deployment of Slony. > > My question: > I now how to test the cluster for the end of the initial copy after a > "subscribe set" has been submitted. > What I don't know is how to inquire the actual state of the replication. > If the application is quiet and no more modifications are done on the master > database, > how do I know that Slony (actually the slon daemon on the slave side) has > finished mirroring the pending transactions? > > Thanks for your help, > > Rudolf van der Leeden > [EMAIL PROTECTED] > Logic United GmbH, Munich > > > > > > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general > >
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
