so a while ago I posted about pg_listener vs autovacuum, however it
seems sl_event is also nearly impossible to have vacuumed for me.
However since then another issue has come up: sl_event cannot be
autovacuumed.
As of earlier today the last successful autovac of sl_event on my
origin was in may (I'd run vacuum manually a few times between then
and now).
There is quite a lot of replication going on so it is pretty much
constantly busy. Looking at my logs "busy" is currently defined as
30-40M rows across various tables replicated daily. I'm not sure
there is much that can be done for slony 1.2 beyond scheduling some
manual vacuuming - would 2.x be less prone to these issues?
[postg...@xxxx log]$ grep "Jul 13" pgsql.log | grep "automatic vacuum
of table \"XXXX._replication.sl_event\"" | wc
540 6480 59228 (this morning)
[postg...@xxxx log]$ grep "Jul 12" pgsql.log | grep "automatic vacuum
of table \"XXXX._replication.sl_event\"" | wc
1438 17256 157726
[postg...@xxxlog]$ grep "Jul 11" pgsql.log | grep "automatic vacuum
of table \"XXXX._replication.sl_event\"" | wc
1164 13968 127691
--
Jeff Trout <[email protected]>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
