RE: Extremely slow autovacuum:vacuum to prevent wraparound

From: Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com>
To: "rjo_roy(at)yahoo(dot)com" <rjo_roy(at)yahoo(dot)com>, "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:20:29
Message-ID: E9FA92C2921F31408041863B74EE4C2001AF005C26@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 15:14
To: Steven Winfield
Cc: pgsql-general(at)postgresql(dot)org
Subject: RE: Extremely slow autovacuum:vacuum to prevent wraparound

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

Stack Overflow confirms my memories about killing autovacuum - pg_cancel_backend() should be fine.
https://stackoverflow.com/questions/18048842/danger-in-killing-autovacuum-vacuum-queries-to-prevent-wraparound

Steve.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rijo Roy 2018-07-11 14:22:35 RE: Extremely slow autovacuum:vacuum to prevent wraparound
Previous Message Rijo Roy 2018-07-11 14:14:07 RE: Extremely slow autovacuum:vacuum to prevent wraparound