Andreas 'ads' Scherbaum wrote:
> On Sat, 7 Jul 2007 00:12:32 +0200 Andreas 'ads' Scherbaum wrote:
>
> > On Fri, 6 Jul 2007 12:06:41 -0400 Alvaro Herrera wrote:
> >
> > > Andreas 'ads' Scherbaum wrote:
> > > > The value is '0' for all columns in all entries, except 'vacrelid' and 'enabled'.
> > > > Can a VACUUM run happen, even if enabled is set to false?
> > >
> > > Huh, try putting -1 in all columns instead. 0 is a nasty value to have
> > > in there. I haven't tested the effects but if freeze_max_age is 0 it
> > > may be doing what Pavan says.
> >
> > Ok, did this. Will take a look, what autovacuum is doing now.
>
> Seems like that was the problem. I changed all '0' to '-1' and VACUUM is
> skipping this tables now.
>
>
> Thanks for finding this out
Oops :-( We should certainly make an effort to check the validity of
the values in pg_autovacuum, but 0 is a perfectly valid value, so the
check would not help you any in this case :-(
--
Alvaro Herrera http://www.PlanetPostgreSQL.org/
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended." (Gerry Pourwelle)
