Hi Steve,
Apologies, I misread it as 2 billion, it is as you said set as 200 million
which is the default value for the parameter autovacuum_freeze_max_age. I just
wanted to confirm whether there would be any impact if I cancel or terminate
the backend for the existing autovacuum :vacuum table_name (to prevent
wraparound). I have initiated a normal vacuum manually but it is stuck on the
table where the autovacuum is processing it.
Thanks, Rijo Roy
Sent from Yahoo Mail on Android
On Wed, 11 Jul 2018 at 7:30 pm, Steven
Winfield<steven.winfi...@cantabcapital.com> wrote: #yiv7029743585
#yiv7029743585 -- _filtered #yiv7029743585 {panose-1:2 2 6 9 4 2 5 8 3 4;}
_filtered #yiv7029743585 {panose-1:2 2 6 9 4 2 5 8 3 4;} _filtered
#yiv7029743585 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered
#yiv7029743585 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered
#yiv7029743585 {panose-1:2 2 6 9 4 2 5 8 3 4;}#yiv7029743585 #yiv7029743585
p.yiv7029743585MsoNormal, #yiv7029743585 li.yiv7029743585MsoNormal,
#yiv7029743585 div.yiv7029743585MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;}#yiv7029743585
a:link, #yiv7029743585 span.yiv7029743585MsoHyperlink
{color:blue;text-decoration:underline;}#yiv7029743585 a:visited, #yiv7029743585
span.yiv7029743585MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv7029743585
span.yiv7029743585EmailStyle17 {color:#1F497D;}#yiv7029743585
.yiv7029743585MsoChpDefault {} _filtered #yiv7029743585 {margin:72.0pt 72.0pt
72.0pt 72.0pt;}#yiv7029743585 div.yiv7029743585WordSection1 {}#yiv7029743585
From: Rijo Roy [mailto:rjo_...@yahoo.com]
Sent: 11 July 2018 14:30
To: srkris...@yahoo.com
Cc: pgsql-gene...@postgresql.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.
This email is confidential. If you are not the intended recipient, please
advise us immediately and delete this message. The registered name of Cantab-
part of GAM Systematic is Cantab Capital Partners LLP. See -
http://www.gam.com/en/Legal/Email+disclosures+EU for further information on
confidentiality, the risks of non-secure electronic communication, and certain
disclosures which we are required to make in accordance with applicable
legislation and regulations. If you cannot access this link, please notify us
by reply message and we will send the contents to you.
GAM Holding AG and its subsidiaries (Cantab – GAM Systematic) will collect and
use information about you in the course of your interactions with us. Full
details about the data types we collect and what we use this for and your
related rights is set out in our online privacy policy at
https://www.gam.com/en/legal/privacy-policy. Please familiarise yourself with
this policy and check it from time to time for updates as it supplements this
notice
