| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | POSTGRES <pgsql-es-ayuda(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] autovaccum can be disabled? |
| Date: | 2008-12-17 17:24:19 |
| Message-ID: | 20081217172419.GG4453@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
Jaime Casanova escribió:
> 2008/12/17 Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>:
> >>
> >>> Nevertheless, i'm seeing this in the logs:
> >>>
> >>> LOG: automatic analyze of table "mic.public.tcom_invitacion" system
> >>> usage: CPU 0.00s/0.04u sec elapsed 0.04 sec
> >>
> >> Es raro que sea un "automatic analyze" ... ¿estás seguro que la tabla es
> >> la misma? Verifica el search_path.
>
> de hecho hubo un vacuum automatico tambien de esa tabla... :(
>
> LOG: automatic vacuum of table "mic.public.tcom_invitacion": index scans: 0
> pages: 0 removed, 85305 remain
> tuples: 0 removed, 3938524 remain
> system usage: CPU 0.30s/0.70u sec elapsed 1.00 sec
La otra explicación podría ser que pusiste un valor bajo en
max_freeze_age. Por favor muestra toda la tupla pg_autovacuum.
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"La felicidad no es mañana. La felicidad es ahora"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2008-12-17 17:30:20 | Re: [HACKERS] autovaccum can be disabled? |
| Previous Message | Jaime Casanova | 2008-12-17 17:19:27 | Re: [HACKERS] autovaccum can be disabled? |