On Feb 7, 2007, at 9:24 AM, Dan Falconer wrote:
Final thought: if my Slony setup hasn't figured itself out already, then I would venture to guess that this problem will recur next week after inventory processing. If so, I'll put a message on the list again, and maybe we can figure out what causes this little beasty to rear it's ugly not-so- littlehead.
when we do our monthly data cleanup, we take slony into account... after a certain number of records are purged (and their cascading deletes from foreign keys), we pause until slony is caught up. This does two things: it keeps slony from falling way too far behind and keeps the live reports we generate on demand current since they use the replica server. it does take a few days to purge the 30 days of data, but nobody really notices the extra load :-)
another thing to consider, and not knowing your equipment it may not apply, is that sometimes you just need faster equipment to support your heavy load.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
