Re: Autovacuuming

From: "Gourish Singbal" <gourish(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Autovacuuming
Date: 2006-04-25 06:03:00
Message-ID: 674d1f8a0604242303w15be5f2oe4ba806873d1984d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks for the reply. we will be reviewing the settings soon.
Also have manually ran the database-wide vacuum on the 50GB database . (for
safety reasons). the transaction count is 1147399191. we plan to automate
this process once a month or so.

Do we need to Disable the Auto-vacuum deamon when we manually run the
database-wide vacuum command ?.

thanks in advance.

On 4/24/06, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
>
> On Mon, Apr 24, 2006 at 11:21:16AM +0530, Gourish Singbal wrote:
> > The Age of the database is 1144759836 . We have enabled autovacuuming .
> > The details are:-
> > autovacuum = on
> > autovacuum_naptime = 300
> > autovacuum_vacuum_threshold = 10000
> > autovacuum_analyze_threshold = 5000
> > autovacuum_vacuum_scale_factor = 0.3
> > autovacuum_analyze_scale_factor = 0.3
>
> Those settings are *really* conservative... I normally use 400, 200,
> 0.2, 0.1 respectively...
>
> > Wanted to know when the auto-vacuum daemon will run an
> database-wide vacuum
> > call to avoid transaction ID wraparound failures.
>
> IIRC it will do that somewhere between 2B and 4B transactions have
> elapsed. The true answer lies somewhere in
> src/backend/postmaster/autovacuum.c.
> --
> Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
> Pervasive Software http://pervasive.com work: 512-231-6117
> vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
>

--
Best,
Gourish Singbal

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2006-04-25 07:19:16 Re: Autovacuuming
Previous Message D Srinivas-in1713c 2006-04-25 04:48:46 Regarding start postgresql startservice