On Tue, January 16, 2007 15:08, Thomas Pundt wrote:
> Hi,
>
>
> we seem to have a problem with our replication cluster - the sl_log_1
> table doesn't get cleaned out. Can anybody give some advice on how to
> resolve the issue?
>
[ SNIP ]
> RPONLINE=# select * from "_RPO".sl_status;
> ]-------------+---------------------------
> st_origin                 | 1
> st_received               | 3
> st_last_event | 2018097
> st_last_event_ts          | 2007-01-16 14:54:44.99581 st_last_received
> | 1525251
> st_last_received_ts       | 2006-12-30 09:46:15.781741
> st_last_received_event_ts | 2006-12-30 09:46:15.774831 st_lag_num_events
> | 492846
> st_lag_time               | 17 days 05:08:29.448725 -[ RECORD 3


A node with id = 3 lags 17 days behind the origin. While that node
is lagging, all events are kept in the log.

So you need to either let that node catch up or remove it from the
cluster. When that is completed, the log will be cleaned after about
20 minutes.

- Niels