Hannu Krosing hannu
Fri Nov 12 11:37:05 PST 2004
Hi

I have a situation, where my replica on node3 is ~1 day behind reality
(due to similar situation to the one discussed in the Slow-ny thread), but

accountdb=# select * from _accountdb_cluster.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 |        130148 | 2004-11-12 12:47:09.334286 |   
       130147 | 2004-11-12 11:46:07.979793 | 2004-11-12
12:46:07.30647  |                 1 | 00:48:32.935116
         1 |           3 |        130148 | 2004-11-12 12:47:09.334286 |   
       130146 | 2004-11-12 11:45:05.514404 | 2004-11-12
12:45:04.884938 |                 2 | 00:49:35.356648
(2 rows)


I was under the impression that sl_status should somehow show how far
behind the replica is.

---------------
Hannu



More information about the Slony1-general mailing list