Over the last 30 hours there have been a tremendous amount of changes
against my db. This morning there are 5.6 million entries in sl_log_1.
Over time the fetch log statements are getting longer in duration.
Is there any hope the log switch/truncate will complete?
LOG: 00000: duration: 7768.196 ms statement: fetch 100 from LOG;
LOCATION: exec_simple_query, postgres.c:1015
LOG: 00000: duration: 7775.775 ms statement: fetch 100 from LOG;
LOCATION: exec_simple_query, postgres.c:1015
LOG: 00000: duration: 7764.928 ms statement: fetch 100 from LOG;
LOCATION: exec_simple_query, postgres.c:1015
STATEMENT: delete from "_mycluster_procluster".sl_log_1 where
log_origin = '1' and log_xid < '252358837'; delete from
"_mycluster_procluster".sl_log_2 where log_origin = '1' and log_xid <
'252358837'; delete from "_mycluster_procluster".sl_seqlog where
seql_origin = '1' and seql_ev_seqno < '647367'; select
"_mycluster_procluster".logswitch_finish();
NOTICE: 00000: Slony-I: log switch to sl_log_2 still in progress -
sl_log_1 not truncated
LOCATION: exec_stmt_raise, pl_exec.c:2149
STATEMENT: delete from "_mycluster_procluster".sl_log_1 where
log_origin = '2' and log_xid < '220973324'; delete from
"_mycluster_procluster".sl_log_2 where log_origin = '2' and log_xid <
'220973324'; delete from "_mycluster_procluster".sl_seqlog where
seql_origin = '2' and seql_ev_seqno < '605163'; select
"_mycluster_procluster".logswitch_finish();
Thanks in advance,
bruce
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
