http://www.slony.info/bugzilla/show_bug.cgi?id=143

           Summary: definition of sl_status.st_lag_time suspicious
           Product: Slony-I
           Version: 2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: low
         Component: stored procedures
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: peter_e at gmx.net
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


The column sl_status.st_lag_time is currently defined as

now() - ce.ev_timestamp::timestamp with time zone AS st_lag_time

This is pretty weird, because if nothing happens, such as on a slave, the lag
grows without bound, even though there is nothing wrong.  Monitoring systems
such as munin and nagios usually use this column to monitor the health of a
replication setup, but this makes it much less useful.

By contrast, the column st_lag_num_events is

e.ev_seqno - c.con_seqno AS st_lag_num_events

so it would make more sense in my mind to make st_lag_time

e.ev_timestamp - ce.ev_timestamp AS st_lag_time

Or at least the difference and inconsistency  between these two values should
be more clearly explained somewhere in the docs.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.