Message-ID: <535A2F1C.2060107@gmx.net>
Date: Fri, 25 Apr 2014 11:47:08 +0200
From: =?UTF-8?B?VG9yc3RlbiBGw7ZydHNjaA==?= <torsten.foertsch@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KjQsNC70LDRiNC+0LI=?= <skaurus@gmail.com>,
 "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Server vacuuming the same table again and again
References: 
 <CAKPeCUE60iAdwDCJv82DTNQYpJgrM_O2ehTPBAdbx6kqFWrunA@mail.gmail.com>
In-Reply-To: 
 <CAKPeCUE60iAdwDCJv82DTNQYpJgrM_O2ehTPBAdbx6kqFWrunA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 25/04/14 09:47, Дмитрий Шалашов wrote:
> Half a day ago one of our production PG servers (arguably busiest one)
> become very slow; I went to investigate the issue and found that it runs
> simultaneously '(auto)VACUUM ANALYZE recommendations' - largest table on
> that server - and checkpoint, giving a 100% disk load

Maybe the table has reached the state where it needs a VACUUM FREEZE.
Autovacuum does that for you but it requires a complete scan of the table.

Torsten


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