| From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
|---|---|
| To: | sthomas(at)optionshouse(dot)com |
| Cc: | Kevin Grittner <kgrittn(at)mail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unexplained Major Vacuum Archive Activity During Vacuum |
| Date: | 2012-11-01 16:40:23 |
| Message-ID: | CAF-3MvPpqjRfQ-zqFRxLUShEW26atxap8=wAF89C7xcfKQsXUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1 November 2012 17:19, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
> On 11/01/2012 10:28 AM, Kevin Grittner wrote:
> Based on my past experience with 8.2, and my understanding of 9.1, I
> moved autovacuum_freeze_max_age up to 650M so we'd never get a mid-day
> freeze. And the default for vacuum_freeze_table_age is 150M, which I hadn't
> changed.
Instead of attempting to postpone freeze until beyond the life
expectancy of our universe, what you probably should have done is
vacuum more often so that vacuum has less work to do.
--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2012-11-01 16:44:25 | Re: Unexplained Major Vacuum Archive Activity During Vacuum |
| Previous Message | Filip Rembiałkowski | 2012-11-01 16:33:22 | question on foreign key lock |