On Mar 22, 2007, at 11:03 AM, Victoria Parsons wrote:
Has anyone else found that they need a vacuum full to keep their replication, and/or general postgres use up to speed? Have I mis-understood the use of vacuum full, and does it do more than just recover disk space? Next time it goes wrong I will do vacuum full on a table at a time to see if I can narrow down the culprit.
vacuum full on origin or on replicas?This indicates to me that you're short on I/O bandwidth because the vacuum shrinks the tables. I wonder if just doing a re-index would solve your issue.
FWIW, I suffer similar issues, and my band-aid for now is to drop one index on the replica which only gets used on the origin for my largest table. That has made my replication stable.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
