I have one subscriber, one master.

Running 'select * from sl_status;' on the master I see:

<<
 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 |       1713287 | 2007-05-16 11:46:39.741258
|          1708951 | 2007-05-16 11:45:30.50751 | 2007-05-16
06:37:55.004498 |              4336 | 05:08:45.916761
>>

I.e.
st_last_received_event_ts == '2007-05-16 06:37:55.004498' and
st_lag_num_events == 4336 and
st_lag_time == '05:08:45.916761' (5 hours?)

Slony is controlled from the subscriber. I have restarted slony from
the subscriber (clumsily with 'kill' then 'slon.sh restart' because
'slon.sh stop' didn't seem to stop it).

Events are getting processed but very slowly such that st_lag_time is
increasing.

Every night I update a field in 100,000 records and slony can't seem
to quite catch up.

The load averages on the two database servers is 'normal' which means
low for the master and moderate for the subscriber.

Suggestion? Thanks!

- Don Barthel