Sun Jul 26 05:19:59 PDT 2009
- Previous message: [Slony1-general] postgres and slon is started or not!?? Slon command not known by system
- Next message: [Slony1-general] sl_status incorrectly reports long event lag
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello, I'm experiencing a curious issue with Slony 2.0.2 . If I shut down a slave, and subsequently boot it back up, the sl_status view's event lag grows continually, as if replication isn't working between the master and that particular slave. However, replication is observably working. I can make the sl_status view's lag for the slave return to zero by restarting slon daemons. Why might this be? I find the sl_status view very important for my particular application. Regards, Peter Geoghegan
- Previous message: [Slony1-general] postgres and slon is started or not!?? Slon command not known by system
- Next message: [Slony1-general] sl_status incorrectly reports long event lag
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list