Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1D2A89FB5F1 for ; Mon, 5 Mar 2007 17:47:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 75399-10 for ; Mon, 5 Mar 2007 17:47:31 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by postgresql.org (Postfix) with ESMTP id 59BA39FB2C9 for ; Mon, 5 Mar 2007 17:47:34 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id i28so1787787wxd for ; Mon, 05 Mar 2007 13:47:33 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=utdyrPfl7QkzRY3srSpk4EuYBQlYoovcVL2htnjVe5N/uPwfKW1BMw8TTH/wnoK32y7zWQkE5wFjLGc2Ll8/bAxfxVpl0pADkT9m12dx9whV6wFAFCpyuayF6KvGmdQv+g41MLbqdHnV8dSjrNwcNiEGvRhn9f6DB2fhorkUgTo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Og2jrFy7Sy7DI54Moi+GMZU2ZER2GN03iVR9VGgE5/fGwCSZOaPKRLSwMHxda43EQ0AvWaNR/gVJjYvZDSenE1UvubxTPm4EqKy8QbSN08D0pMV9CsE9a3UC16SFxtJqOzRVDlDcVXbC8cmc2JT9uV0HFmnux0yFlRXywg2IGzM= Received: by 10.70.130.8 with SMTP id c8mr10520328wxd.1173131253391; Mon, 05 Mar 2007 13:47:33 -0800 (PST) Received: by 10.70.109.16 with HTTP; Mon, 5 Mar 2007 13:47:33 -0800 (PST) Message-ID: <357fa7590703051347oae6ce8rb34a188a823bb66d@mail.gmail.com> Date: Mon, 5 Mar 2007 16:47:33 -0500 From: "Steven Flatt" To: "Tomas Vondra" Subject: Re: Turning off Autovacuum Cc: pgsql-performance@postgresql.org In-Reply-To: <45EC7D05.60204@fuzzy.cz> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34576_7765352.1173131253361" References: <357fa7590703050800u5954e55fyc806ee19fb1f161@mail.gmail.com> <45EC7D05.60204@fuzzy.cz> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/98 X-Sequence-Number: 23503 ------=_Part_34576_7765352.1173131253361 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Yeah, I'm hoping there's an easier way. I'd have to put several thousand entries in the pg_autovacuum table only to remove them a few minutes later. What I really want is to disable the daemon. Any idea why I can't just simply set autovacuum to off? Steve On 3/5/07, Tomas Vondra wrote: > > If you want to disable it only for some tables, you can put special > values into pg_autovacuum. This won't disable the autovacuum daemon, but > some of the tables won't be vacuumed. > > Tomas > > Not quite a performance question, but I can't seem to find a simple > > answer to this. We're using 8.1.4 and the autovacuum daemon is > > running every 40 seconds cycling between 3 databases. What is the > > easiest way to disable the autovacuumer for a minute or two, do some > > other work, then re-enable it? Do I have to modify postgresql.conf > > and send a HUP signal to pick up the changes? > > > > I figured this would work but I can't find a reason why not: > > > > # show autovacuum; > > autovacuum > > ------------ > > on > > (1 row) > > > > # set autovacuum to off; > > ERROR: parameter "autovacuum" cannot be changed now > > > > In postgresql.conf: > > > > autovacuum = on > > > > Thanks, > > > > Steve > > > > ------=_Part_34576_7765352.1173131253361 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Yeah, I'm hoping there's an easier way.  I'd have to put several thousand entries in the pg_autovacuum table only to remove them a few minutes later.  What I really want is to disable the daemon.
 
Any idea why I can't just simply set autovacuum to off?
 
Steve

 
On 3/5/07, Tomas Vondra <tv@fuzzy.cz> wrote:
If you want to disable it only for some tables, you can put special
values into pg_autovacuum. This won't disable the autovacuum daemon, but
some of the tables won't be vacuumed.

Tomas
> Not quite a performance question, but I can't seem to find a simple
> answer to this.  We're using 8.1.4 and the autovacuum daemon is
> running every 40 seconds cycling between 3 databases.  What is the
> easiest way to disable the autovacuumer for a minute or two, do some
> other work, then re-enable it?  Do I have to modify postgresql.conf
> and send a HUP signal to pick up the changes?
>
> I figured this would work but I can't find a reason why not:
>
> # show autovacuum;
>  autovacuum
> ------------
>  on
> (1 row)
>
> # set autovacuum to off;
> ERROR:  parameter "autovacuum" cannot be changed now
>
> In postgresql.conf:
>
> autovacuum = on
>
> Thanks,
>
> Steve
>


------=_Part_34576_7765352.1173131253361--