| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | JC Praud <brutaltruth42(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: auto truncate/vacuum full |
| Date: | 2009-10-28 16:13:54 |
| Message-ID: | 3073cc9b0910280913t15e05081yf6e1997f958b8efa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Oct 27, 2009 at 6:29 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>
> Do you have a vacuum in cron or something like that? As Tom says, if it
> had been autovacuum, it should have been cancelled automatically (else
> we've got a bug); but something invoking vacuum externally wouldn't
> have, so what you describe is what we would expect.
>
then we have a bug (at least in 8.3, haven't tried in 8.4)... i see
this a month ago, an autovacuum blocking a lot of concurrent updates
and selects... once i pg_cancel_backend() the autovacuum process the
other ones starting to move
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Penrod, John | 2009-10-28 16:17:22 | Has anyone seen this while running pg_dumpall? |
| Previous Message | Ivan Sergio Borgonovo | 2009-10-28 15:48:35 | Re: still on joining array/inline values was and is: design, ref integrity and performance |