From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Anthony Bull <antsbull(at)gmail(dot)com> |
Cc: | Edson Richter <edsonrichter(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pg 9.1: Do I need to run vacuum analyze instead vacuum full? |
Date: | 2012-07-25 00:02:05 |
Message-ID: | CAOR=d=2C6XFRe92=-3v34vhC+V7OwDXrdLoH8U7p=x8dQ2rM2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jul 24, 2012 at 5:43 PM, Anthony Bull <antsbull(at)gmail(dot)com> wrote:
> We found the auto vacuum would always kick in during our daily data loads in
> the mornings and completely bottle neck our system, and in the end had to
> turn it off and schedule our own vacuum analyze over the weekend each week
> using crontab. We do a couple of gigs of inserts a week into our postgres
> db - and having control of when vacuuming happens is pretty important, as
> our system is online 24 hours to both northern and southern hemispheres.
Please note that autovacuum is tunable in terms of how much load it
places on a system when it runs. Often making it somewhat less
aggressive can accomplish the same task as scheduling regular vacuums.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2012-07-25 00:46:09 | Re: Smaller data types use same disk space |
Previous Message | Anthony Bull | 2012-07-24 23:43:54 | Re: Pg 9.1: Do I need to run vacuum analyze instead vacuum full? |