So I've noticed recently that I'm vacuuming the sl_?.log files with postgres and this doesn't appear right. The fact is slon has it's own process for dealing with this and I believe it's a clean truncate.
I'm wondering how do I go about figuring out whether postgres is in fact vacuuming these logs and how to stop it? I would rather allow slon to handle it and stop postgres from dealing with the slon tables (as far as vacuuming them goes) In slon 2.0.2 there is this query that doesn't seem to work in the 1.2.x versions. select oid, relname from pg_class where relnamespace = (select oid from pg_namespace where nspname = '_' || 'MyCluster') and relhasindex; Thanks Tory Note: I'm one of the unhappy ones that feel the current postgres/slon upgrade paths are painful. Multi TB db requires a dump restore?!?!?!?! slon can't be ported a tad to be backward compatible, so you have to completely build new and uninstall install, and rebuild your slon cluster. _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
