On Feb 7, 2007, at 10:38 AM, Dan Falconer wrote:
One more quick note: over the night, we had a vacuum analyze run on the whole database (it's cronned to run weekly). In the output of the vacuum (it was set to verbose), it looks like our main inventory table had 7 indexes, each of which had 12.7M index row versions (along with 12.7 row versions from the table itself) removed. This would probably affect Slony *somehow*... but I'mnot sure if it would directly contribute to the problem at hand.
If this has been going on for a long time, I'd recommend trying to reindex your table... since you have a replica you can do this on the replica first, swap roles, then do it on the other server, and swap roles back.
Every few months I need to do this and on the bigger, high-churn tables it saves about 40% of the disk usage per index. My biggest tables push 230+ million rows, and grow at about O(1 million) per day.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
