| From: | Artem Tomyuk <admin(at)leboutique(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | autovacuum disk IO |
| Date: | 2016-03-02 15:25:10 |
| Message-ID: | CANYYVq+vJ+8ZUm-jGVXd=Y4vPBKhd0R72nNtY-3tFYJ81YWPwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
Hi.
I've noticed that autovac. process worked more than 10 minutes, during this
zabbix logged more than 90% IO disk utilization on db volume....
===========>29237 2016-03-02 15:17:23 EET 00000 [24-1]LOG:
automatic vacuum of table "lb_upr.public._reference32": index scans: 1
pages: 0 removed, 263307 remain
tuples: 298 removed, 1944753 remain, 0 are dead but not yet removable
buffer usage: 67814 hits, 265465 misses, 15647 dirtied
avg read rate: 3.183 MB/s, avg write rate: 0.188 MB/s
*system usage: CPU 5.34s/6.27u sec elapsed 651.57 sec*
Is it possible to log autovac. io impact during it execution?
Is there any way to limit or "nice" autovac. process?
Thanks to all for any help.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-03-02 15:31:15 | Re: [PERFORM] autovacuum disk IO |
| Previous Message | Guillaume Lelarge | 2016-03-02 14:09:12 | Re: To avoid a database shutdown, execute a database-wide VACUUM |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-03-02 15:31:15 | Re: [PERFORM] autovacuum disk IO |
| Previous Message | James Parks | 2016-03-02 07:36:20 | Re: Merge joins on index scans |