| From: | Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com> |
|---|---|
| To: | "rjo_roy(at)yahoo(dot)com" <rjo_roy(at)yahoo(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | RE: Extremely slow autovacuum:vacuum to prevent wraparound |
| Date: | 2018-07-11 14:00:00 |
| Message-ID: | E9FA92C2921F31408041863B74EE4C2001AF00585E@CCPMAILDAG03.cantab.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
From: Rijo Roy [mailto:rjo_roy(at)yahoo(dot)com]
Sent: 11 July 2018 14:30
To: srkrishna(at)yahoo(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Extremely slow autovacuum:vacuum to prevent wraparound
No, I have 3 sessions of autovacuum against 3 tables which is doing a Vacuum to prevent wraparound as it hit the limit of autovacuum_freeze_max_age of 2 billion.
I also have a vaccumdb session which is invoked by me on these tables which is currently in paused state. So, I want to know whether I can kill the autivacuum sessions which is running since 5 days and extremely slow and just run a manual vacuum against these tables instead.
Is your autovacuum_freeze_max_age really set to 2 billion? The default value is 200 million. Setting it that high and disabling autovacuum isn’t just silly - it borders on sabotage!
I’ve used pg_cancel_backend() (NOT pg_terminate_backend()) on autovacuum jobs before without issue.
Good luck!
Steve.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Finzel | 2018-07-11 14:02:34 | Re: Open Source tool to deploy/promote PostgreSQL DDL |
| Previous Message | Olivier Gautherot | 2018-07-11 13:31:45 | Re: Extremely slow autovacuum:vacuum to prevent wraparound |