From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem with autovacuum and pg_autovacuum |
Date: | 2007-07-06 06:00:19 |
Message-ID: | 2e78013d0707052300u6d8a8ba9l4ce4c35eba35dc2f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/5/07, Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> wrote:
>
>
> Hello,
>
> 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.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hannes Dorbath | 2007-07-06 06:30:03 | Re: tsearch2 in multilingual database? |
Previous Message | Chris Travers | 2007-07-06 03:02:14 | Re: Localization trouble |