"Rafael Domiciano" <rafael.domiciano at gmail.com> writes:
> Frequently Slony is vacuuming my database, and I'm having to kill his proccess because it's slowing the client-side application.
> I tryied to find option that disables the vacuum but i'm unsucessful.
> Someone know how to stop vacuum's Slony?

You can look at the documentation for the slon command, and find how
to do this.

However, it is entirely probable that this is a Really Unwise thing to
do.

Slony-I does not vacuum anything of your application's tables; it only
runs VACUUM and ANALYZE against its own internal tables.

Those tables need to be vacuumed quite frequently.

"Rafael Domiciano" <rafael.domiciano at gmail.com> writes:
> I have a proccess at 
> midnigth that does a "vacuumdb -a -v -z -f", so I don't need Slony's vacuum 
> at midday. 

That is absolutely incorrect.

Slony-I's internal tables MUST be vacuumed WAY more frequently than
once per day.  If you suppress the vacuuming that Slony-I does, and do
not run autovacuum or something similar, you WILL experience big
problems with replication.

We didn't code Slony-I to run VACUUM on its tables just for fun - we
did so because it was *necessary*.  You suppress the VACUUMing at your
peril.

If you examine the documentation, you can find a way to suppress the
vacuuming, but I decline to explain where, as I am reasonably certain
from the details that you have given that it would have *terrible*
implications for your environment.
-- 
output = reverse("gro.mca" "@" "enworbbc")
http://linuxfinances.info/info/bestpractices.html
"Programming today  is a race  between software engineers  striving to
build bigger and better  idiot-proof programs, and the Universe trying
to  produce  bigger  and  better  idiots.  So  far,  the  Universe  is
winning."  -- Rich Cook