dba at richyen.com wrote:
> Hi everyone,
> 
> Just wanted to look for an explanation regarding what happens on the
> subscriber's end of a replication set.  I currently have 4 nodes (1 thru
> 4), and node 4 also has the "-a <dir>" flag turned on for log shipping (but
> I think this is irrelevant)



> 
> Occasionally, I will see in test_slony_state_dbi.pl, that one of the
> subscribers has really old events or that the provider is lagging behind
> the provider, so I decided to harvest some data.  Wrote up a cronjob that
> will fetch the average slony lag on node 4 (I could've picked any of them,
> but just chose this one because load was lowest).
> 
>


> Using Slony 2.0.3, postgres 8.4.2 on CentOS 2.6.18 on all nodes.

1.  You should upgrade right away to 2.0.4.  Slony 2.0.3 has a rather 
serious memory corruption bug.  (the bug was not present in 2.0.2).

2. What you describe sounds like bug 127 
(http://bugs.slony.info/bugzilla/show_bug.cgi?id=127) which is present 
in any recent 1.2.x version and in all currently released 2.0.x versions 
but has been fixed in git and is planned to be included in 2.0.5


> 
> Much appreciated!
> --Richard
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142