We have a simple 2-node master/slave system, and the sl_log_1 on the master has currently half a million rows and growing at a rate of roughly 10 per second, even though the slave is fully caught up. I do see regular
2006-04-03 14:37:39 BSTLOG: duration: 1336.384 ms statement: delete from "_replication".sl_log_1 where log_origin = '1' and log_xid < '226300425'; delete from "_replication".sl_log_2 where log_origin = '1' and log_xid < '226300425'; delete from "_replication".sl_seqlog where seql_origin = '1' and seql_ev_seqno < '96499'; and 2006-04-03 14:42:33 BSTLOG: duration: 250432.316 ms statement: vacuum analyze "_replication".sl_log_1; queries on the master, yet half a million rows seems like an /awful/ lot.. I would be worrying about it if it'd always been this large, but sl_log_1 has been gradually growing. Does this sound normal? Oddly, pgadmin3 is telling me the estimated row count is only 30000 even after a vacuum analyze.. Finally - should there be any kind of index set on sl_log_1 ? Cheers, Gavin. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
