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
Date: Thu, 30 Jul 2015 16:07:52 -0300
Message-ID: <20150730190752.GU2441@postgresql.org> (raw)
In-Reply-To: <CABzCKRAVcKieKfWtnXJ0gDisDzWVYV0+cCb_adzZooAO3_2DoA@mail.gmail.com>
References: <CABzCKRDtMfmgKFoMeTFDRGif+siQK9bXM4791ii8ZBJfORSFNA@mail.gmail.com>
<20150730185939.GT2441@postgresql.org>
<CABzCKRAVcKieKfWtnXJ0gDisDzWVYV0+cCb_adzZooAO3_2DoA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@2ndquadrant.com, jayknowsunix@gmail.com
Subject: Re: Autovacuum behavior
In-Reply-To: <20150730190752.GU2441@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox