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-06 14:10:50 |
Message-ID: | 20070706161050.717b94ee.adsmail@wars-nicht.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 6 Jul 2007 11:30:19 +0530 Pavan Deolasee wrote:
Hello,
> On 7/5/07, Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> wrote:
> >
> > On Wed, 4 Jul 2007 18:04:35 -0400 Alvaro Herrera wrote:
> >
> > > Most likely it is worried about XID wraparound, and those are precisely
> > > the tables that need urgent vacuumed because they haven't been vacuumed
> > > in a long time.
> >
> > No, autovacuum is doing this with every run. Beside this, the database has
> > only some 10k changes per day. The wraparound was my first idea, but i
> > don't see a reason, why this should be happen with every autovacuum run.
> >
> Did you check freeze_max_age values in the pg_autovacuum table ? A very
> small value can trigger XID wraparound related VACUUMs in every run.
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?
Greetings from Italy
--
Andreas 'ads' Scherbaum
Failure is not an option. It comes bundled with your Microsoft product.
(Ferenc Mantfeld)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2007-07-06 14:38:50 | Check if language is installed |
Previous Message | Perry Smith | 2007-07-06 13:57:41 | Re: Polymorphic delete help needed |