| From: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with autovacuum and pg_autovacuum |
| Date: | 2007-07-07 12:51:43 |
| Message-ID: | 20070707145143.9a9c200b.adsmail@wars-nicht.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
--
Andreas 'ads' Scherbaum
Failure is not an option. It comes bundled with your Microsoft product.
(Ferenc Mantfeld)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | henryJack | 2007-07-07 14:27:20 | What secret resipy of PostgreSQL (insert more faster than delete)? |
| Previous Message | Gabriele | 2007-07-07 12:16:56 | PostGreSQL Replication |