Message-ID: <52F7A3AC.2090905@fuzzy.cz>
Date: Sun, 09 Feb 2014 16:50:04 +0100
From: Tomas Vondra <tv@fuzzy.cz>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Bloated tables and why is vacuum full the only option
References: 
 <CAGTBQpYO0xK6_RExbEgCpe782uSRq_0sdZ4jxh=hSotAYj94xg@mail.gmail.com>
In-Reply-To: 
 <CAGTBQpYO0xK6_RExbEgCpe782uSRq_0sdZ4jxh=hSotAYj94xg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 7.2.2014 19:47, Claudio Freire wrote:
>
> Question is... why isn't all that free space being used? The table
> grows in size even though there's plenty (65%) of free space.
> 
> I've got autovacuum severely crippled and that could be a reason, but
> I do perform regular vacuum runs weekly that always run to completion.
> I also do routine reindexing to stop index bloat on its tracks, yet
> freshly-reindexed indexes get considerably reduced in size with vacuum
> full.

Are you logging autovacuum actions? I.e. what is

    log_autovacuum_min_duration

set to? It it's set to -1 you won't get any messages because of
conflicting locks or stuff like that, which might be the culprit here.

Also, when you're running the weekly VACUUM, do VACUUM (VERBOSE) and
post it here. That might at least help us eliminate some of the usual
suspects.

regards
Tomas


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