| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | D C <ptradingcom(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: "VACUUM FULL ANALYZE" vs. Autovacuum Contention |
| Date: | 2011-07-07 21:21:42 |
| Message-ID: | CAOR=d=3tpFoT27g6U8nU1BPmyG0soA2UdNGfhv+69aq09MHWew@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jul 7, 2011 at 2:30 PM, D C <ptradingcom(at)gmail(dot)com> wrote:
> Hello,
>
> (Apologies for any possible duplication of this email.)
>
> (Also, apologies if this is an obvious question. I have gone through the
> archives without seeing something that directly ties to this.)
>
> We are running Postgresql on a 64b RHEL5.2 64b server. "Uname -a":
> --------------Linux xxxxxxx 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT
> 2008 x86_64 x86_64 x86_64 GNU/Linux
>
> We have autovacuum enabled with the following settings:
>
> autovacuum_naptime = 30s
> autovacuum_vacuum_threshold = 200
> autovacuum_vacuum_scale_factor = 0.5
> autovacuum_vacuum_cost_delay = 10
>
> In addition to autovacuuming, each day, early, in the morning, we run a full
> vacuum, like this: "vacuumdb --all --full --analyze".
Why?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-07-07 21:30:50 | Re: "VACUUM FULL ANALYZE" vs. Autovacuum Contention |
| Previous Message | D C | 2011-07-07 20:30:39 | "VACUUM FULL ANALYZE" vs. Autovacuum Contention |