From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | jd(at)commandprompt(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: autovacuum not honoring pg_autovacuum in 8.3.5? |
Date: | 2009-02-13 20:51:38 |
Message-ID: | 3073cc9b0902131251l7933347bqc1eaabc70a611a59@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 13, 2009 at 3:21 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> Hello,
>
> I found this today. Note, auto vacuum has been disabled for this
> relation for a very, very long time. At the very end you will see that
> this relation has been autovacuumed previously as well. We have a manual
> cron to vacuum this table every hour so I am unsure why autovacuum is
> doing what it is doing.
>
> app=# select * from pg_autovacuum where vacrelid = '21474846';
> -[ RECORD 1 ]----+---------
> vacrelid | 21474846
> enabled | f
> vac_base_thresh | 0
> vac_scale_factor | 0
> anl_base_thresh | 0
> anl_scale_factor | 0
> vac_cost_delay | 0
> vac_cost_limit | 0
> freeze_min_age | 0
> freeze_max_age | 0
>
i was bitten for this already... the problem is that you have all
parameters in 0... they should be -1 (specifically max_freeze_age)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2009-02-13 20:56:42 | Re: The science of optimization in practical terms? |
Previous Message | Tom Lane | 2009-02-13 20:44:46 | Re: PQinitSSL broken in some use casesf |