| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: auto vacuum |
| Date: | 2010-04-14 15:03:52 |
| Message-ID: | 20100414150352.GA3678@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Herouth Maoz wrote:
> We found out that the table's response depends on the rate of ANALYZE being performed. We have tuned the values in pg_autovacuum so that we have around one analyze per minute.
>
> What is bothering me is that sometimes the auto vacuum daemon decides to perform a vacuum analyze rather than just analyze. If it just does a vacuum independent of the analyze, we don't see much impact on performance. But if it does vacuum analyze, it means that until vacuum is over, it doesn't do another analyze, and this may take about five minutes, in which our performance under load conditions might deteriorate.
Hmm, this is an use case we never thought about. I don't think there's
any way to coerce autovacuum into doing what you want it to do. I
suggest you turn analyze off for this table (say by setting a very large
scale factor), and analyze it manually through cron or something.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raghavendra t | 2010-04-14 15:07:41 | Re: restore multiple tables postgres |
| Previous Message | Scott Mead | 2010-04-14 15:03:17 | Re: restore multiple tables postgres |