From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | "Jesper Krogh" <jesper(at)krogh(dot)cc> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: autovacuum? |
Date: | 2008-04-18 02:59:55 |
Message-ID: | 2e78013d0804171959k60d2f95ao5e735023433fbe43@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Apr 18, 2008 at 1:18 AM, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
>
>
> So it seems to be running.
Yes.
> But shouldn't it hit the table a lot more?
That depends on your autovac settings, especially
autovacuum_vacuum_scale_factor. If it is set to 0.2 (which is
default), then autovacuum would hit the table whenever the percentage
of dead tuples is at least 20%. Again, the percentage of dead tuples
depends on your table size and rate of insert/update/delete.
> How do I check that it is somehow near optimal?
>
Again that depends on how much table bloat you can sustain. If you
don't want the table to bloat too much, you can set aggressive
settings for autovac. But that would trigger autovac more often and
may have performance implication on your other concurrent queries.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | David Jorjoliani | 2008-04-18 06:18:35 | Re: Database update problem from crontab on ubuntu server |
Previous Message | Phillip Smith | 2008-04-18 02:03:02 | Re: Database update problem from crontab on ubuntu server |