On Thu, 2009-11-26 at 10:26 +0100, Laurent Laborde wrote:
> On Wed, Nov 25, 2009 at 2:33 PM, Brad Nicholson
> <bnichols at ca.afilias.info> wrote:
> > On Wed, 2009-11-25 at 09:33 +0100, Laurent Laborde wrote:
> >> On Mon, Nov 23, 2009 at 5:37 PM, Brad Nicholson
> >> <bnichols at ca.afilias.info> wrote:
> >> >
> >> > If the vacuums are running, do you have a lot of long running
> >> > transactions against this database?
> >>
> >> nope :)
> >
> > -Did you disable vacuums in the slon?
> > -Do you have autovacuum enabled?  If so, post your autovac settings.
> > -If autovac is on, did you tell it to not process pg_listener?
> > -do you have appropriate logging set so the vacuums (either slon
> > triggers or autovac) will be logged?
> 
> I can't find a correct documentation about *how* to activate "vacuum
> from slony".

It is on by default - controlled by the slon.  Unless you turned it off,
it is running.

> If i understand correctly, just disabling the autovacuum on thoses
> tables should active the slony vacuum on them ?

No.  the Slon vacuum has nothing to do with autovacuum.

If you have slon vacuums on (which it sounds like), and you've disabled
autovacuum for these tables (which it also sounds like), and you have no
long running transactions against this node, I can only think of one
case.  Between the cleanup thread intervals where the vacuum runs (every
10 minutes by default), you have enough activity to bloat the table.

BTW, we have had good luck with turning off the slon triggered vacuums
and letting autovacuum handle things.
-- 
Brad Nicholson  416-673-4106
Database Administrator, Afilias Canada Corp.