can someone explain this to me?  or, better yet, point me to a FAQ about 
it?

Specifically:

ams=# select * from _dns.sl_status;
  st_origin | st_received | st_last_event |      st_last_event_ts      | 
st_last_received |    st_last_received_ts     | st_last_received_event_ts  | 
st_lag_num_events |      st_lag_time 
-----------+-------------+---------------+----------------------------+------------------+----------------------------+----------------------------+-------------------+------------------------
          1 |           2 |        276648 | 2006-01-21 10:53:44.100582 |        
   276648 | 2006-01-21 10:53:43.819043 | 2006-01-21 10:53:44.100582 |           
      0 | 3 days 04:41:33.986261
          1 |           3 |        276648 | 2006-01-21 10:53:44.100582 |        
   276617 | 2006-01-21 14:48:25.992746 | 2006-01-21 10:48:31.9358   |           
     31 | 3 days 04:46:46.151043
          1 |           4 |        276648 | 2006-01-21 10:53:44.100582 |        
   276647 | 2006-01-21 10:53:34.03965  | 2006-01-21 10:53:34.030373 |           
      1 | 3 days 04:41:44.05647
(3 rows)

what are the various fields?  all I can "understand" based on the above is 
that st_origin=1+st_received=3 is out of sync with 2/4 ... but, for 
instance, what updates these fields?

st_last_event / st_last_event_ts are all the same, so I'm guessing that 
the master updates that field ...

but what about the other fields?

I'm *guessing* that 1/3 is saturn, my remote dns server, but only because 
of the st_lag_num_events being so high ...

I'm happy to read through a doc on this, to better understand how the 
fields should be read ... I just need to figure out how to monitor slony 
better to detect problems ;(





----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]           Yahoo!: yscrappy              ICQ: 7615664
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general

Reply via email to