| From: | Ilya Kosmodemiansky <ilya(dot)kosmodemiansky(at)postgresql-consulting(dot)com> |
|---|---|
| To: | Дмитрий Шалашов <skaurus(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Server vacuuming the same table again and again |
| Date: | 2014-04-25 08:12:29 |
| Message-ID: | CAG95seX10uLmdFO_nr2oLeN29+Vst3xwOa20Dc3XqaTk=um6_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi Dmitry,
On Fri, Apr 25, 2014 at 9:47 AM, Дмитрий Шалашов <skaurus(at)gmail(dot)com> wrote:
> cancelled autovacuum and it seems to help.
> In the morning autovacuum was back. And then it finished and I gone to work.
Actually, thise two things are tightly bound and there is no chance to
avoid vacuum, you can only postpone it, this kind of work eventually
supposed to be done.
What you really need to do as a first thing - configure your
autovacuum aggressively enough and then mayde ionice autovacuum
instead of mission critical ckeckpointer or bgwriter.
Which exact values have you in the following settings:
autovacuum_analyze_scale_factor
autovacuum_analyze_threshold
autovacuum_freeze_max_age
autovacuum_max_workers
autovacuum_naptime
autovacuum_vacuum_cost_delay
autovacuum_vacuum_cost_limit
autovacuum_vacuum_scale_factor
autovacuum_vacuum_threshold
log_autovacuum_min_duration
?
Best regards, Ilya
>
> Best regards,
> Dmitriy Shalashov
--
Ilya Kosmodemiansky,
PostgreSQL-Consulting.com
tel. +14084142500
cell. +4915144336040
ik(at)postgresql-consulting(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Дмитрий Шалашов | 2014-04-25 08:22:45 | Re: Server vacuuming the same table again and again |
| Previous Message | Дмитрий Шалашов | 2014-04-25 07:47:51 | Server vacuuming the same table again and again |