From: Tom Lane <tgl@sss.pgh.pa.us>
To: Миша Тюрин <tmihail@bk.ru>
Cc: pgsql-general <pgsql-general@postgresql.org>
Cc: Sergey Burladyan <eshkinkot@gmail.com>
Subject: Re: freeze cannot be finished
Date: Wed, 13 Nov 2013 10:37:22 -0500
Message-ID: <5199.1384357042@sss.pgh.pa.us> (raw)
In-Reply-To: <1384356585.995240612@f50.i.mail.ru>
References: <1384356585.995240612@f50.i.mail.ru>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
=?UTF-8?B?0JzQuNGI0LAg0KLRjtGA0LjQvQ==?= <tmihail@bk.ru> writes:
> We are experiencing suspicious and very painful case in our top-business-critical database. We have only 7 weeks before emergency stop of the cluster cause wraparound task in autovacuum process can not be finished again and again.
I'm betting most of the pain comes from this:
> vacuum_cost_delay 40 (autovacuum_vacuum_cost_delay -1)
> vacuum_cost_limit 700
You've set these parameters to values that will make vacuum crawl.
It's not terribly surprising that it's failing to keep up with what
needs to be done.
I'd try setting vacuum_cost_delay to zero again until you're more
or less caught up. After that you could perhaps adopt a value in
the range of a millisecond or two. Not 40.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, tmihail@bk.ru, eshkinkot@gmail.com
Subject: Re: freeze cannot be finished
In-Reply-To: <5199.1384357042@sss.pgh.pa.us>
* 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