Date: Thu, 30 Jul 2015 16:07:52 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: John Scalia <jayknowsunix@gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum behavior
Message-ID: <20150730190752.GU2441@postgresql.org>
References: 
 <CABzCKRDtMfmgKFoMeTFDRGif+siQK9bXM4791ii8ZBJfORSFNA@mail.gmail.com>
 <20150730185939.GT2441@postgresql.org>
 <CABzCKRAVcKieKfWtnXJ0gDisDzWVYV0+cCb_adzZooAO3_2DoA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CABzCKRAVcKieKfWtnXJ0gDisDzWVYV0+cCb_adzZooAO3_2DoA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

John Scalia wrote:
> autovacuum_vacuum_cost_limit is currently set at -1. Not really sure what
> it should be, as I still need to look that up.

Yes, I saw that from your snippet, but that value means to use the value
from vacuum_cost_limit.  If that one is set to a positive value, it may
lead to sleeps during vacuum.

Also, tables could have values set in pg_class.reloptions, leading to
sleeps.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin