| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Benjamin Krajmalnik" <kraj(at)illumen(dot)com> |
| Cc: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Autovacuum stopped running |
| Date: | 2010-05-01 23:09:35 |
| Message-ID: | 11024.1272755375@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Benjamin Krajmalnik" <kraj(at)illumen(dot)com> writes:
> TO be truthful, I did not check that.
> I arrived at the conclusion because although I have 10 autovacuum
> threads, none of the tables had been autoanalyzed or autovacuumed in
> hours (and due to the nature of the activity they do so every minute).
> If I ever see this behavior now I know what to check for :) Thx.
We've seen one or two previous reports that suggested that the autovac
launcher might have stopped launching workers, but it hasn't been
reproducible. Are you using any nonstandard parameters for autovacuum?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Krajmalnik | 2010-05-01 23:21:49 | Re: Autovacuum stopped running |
| Previous Message | Tom Lane | 2010-05-01 22:52:19 | Re: Fresh build on OS X not working (memory) |