pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Torsten Förtsch <torsten.foertsch@gmx.net>
To: Дмитрий Шалашов <skaurus@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Server vacuuming the same table again and again
Date: Fri, 25 Apr 2014 11:47:08 +0200
Message-ID: <535A2F1C.2060107@gmx.net> (raw)
In-Reply-To: <CAKPeCUE60iAdwDCJv82DTNQYpJgrM_O2ehTPBAdbx6kqFWrunA@mail.gmail.com>
References: <CAKPeCUE60iAdwDCJv82DTNQYpJgrM_O2ehTPBAdbx6kqFWrunA@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

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



view thread (10+ messages)  latest in thread

Message-ID: <535A2F1C.2060107@gmx.net>
Permalink:  ../535A2F1C.2060107@gmx.net/
Also on:    postgresql.org/message-id/535A2F1C.2060107@gmx.net

 · 

reply

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-performance@postgresql.org
  Cc: torsten.foertsch@gmx.net, skaurus@gmail.com
  Subject: Re: Server vacuuming the same table again and again
  In-Reply-To: <535A2F1C.2060107@gmx.net>

* 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