Re: Disable autovacuum guc?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disable autovacuum guc?
Date: 2016-10-20 02:55:06
Message-ID: CAMsr+YFeEosCWDHD+HCYPO5HS-6J+XsWiQCPxjVhbjTi0+y59g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 October 2016 at 09:27, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> Hello,
>
> After all these years, we are still regularly running into people who say,
> "performance was bad so we disabled autovacuum". I am not talking about once
> in a while, it is often. I would like us to consider removing the autovacuum
> option. Here are a few reasons:
>
> 1. It does not hurt anyone

I disagree.

It's important for a number of tests, and can be very useful when
doing diagnostic work. It's also important for some kinds of data
recovery efforts.

However, I do think the documentation needs to loudly warn users not
to turn it off, and that if they think vacuum is slowing their system
down they probably actually have to make it run MORE. The problem is
people not understanding autovac, and taking away the option to turn
it off won't help. They'll just find other ways to cripple it.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2016-10-20 03:01:16 Re: Query cancel seems to be broken in master since Oct 17
Previous Message Josh Berkus 2016-10-20 02:22:52 Re: Disable autovacuum guc?