Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ktsour@gmail.com>) id 1TJPAN-0004ML-Hx
	for pgsql-performance@postgresql.org; Wed, 03 Oct 2012 13:39:11 +0000
Received: from mail-we0-f174.google.com ([74.125.82.174])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ktsour@gmail.com>) id 1TJPAL-0006fE-Nk
	for pgsql-performance@postgresql.org; Wed, 03 Oct 2012 13:39:11 +0000
Received: by weyt9 with SMTP id t9so4311307wey.19
	for <pgsql-performance@postgresql.org>;
	Wed, 03 Oct 2012 06:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:mime-version:content-type:from:in-reply-to:date
	:content-transfer-encoding:message-id:references:to:x-mailer;
	bh=48S5Na58d/lKOa/Zv6zsvs3Gd2vkY/tTgWFRgbMG20A=;
	b=i+1Tj4iZpn2YQj2feWoEdF9XVhu5XxvUi4CTDSA4jJZv5Kg5nH6cXsWSmLrNkpm5D/
	jN5v+gGQcw4cvf2GPvF7e73oYNg3CVoemfAbW5T4ez/b7+9YoaxKDUrLRqXDlUQaYefh
	TcGkRDKI1HSWP6qcjDsNvlP+wU2oWZ0eeOgbTlSBDcWY5/ircxOg/7C0zlzht2lcKiiB
	kT8NAUIcwtK1GxrR3Xdsvm6KHbhinNUx1dALy8HCsPVaGoS4aQuOSfDwpYs50UK7t8Xx
	F+WqjCKVeLuGblvEgNq0mNoowbBC9Cm0o66r8nbIGVU005Tm+cD9nTe/ojIyOmOC+77g
	yP1g==
Received: by 10.180.94.226 with SMTP id df2mr29841896wib.11.1349271548616;
	Wed, 03 Oct 2012 06:39:08 -0700 (PDT)
Received: from [192.168.1.103] (kstr60.static.otenet.gr. [79.129.45.250])
	by mx.google.com with ESMTPS id dm3sm8527584wib.3.2012.10.03.06.39.06
	(version=TLSv1/SSLv3 cipher=OTHER);
	Wed, 03 Oct 2012 06:39:07 -0700 (PDT)
Subject: Re: Postgres becoming slow, only full vacuum fixes it
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Kiriakos Tsourapas <ktsour@gmail.com>
In-Reply-To: <5526E5B0-DDCD-4D47-91B7-B3D4CA11A83E@gmail.com>
Date: Wed, 3 Oct 2012 16:39:04 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <61492A85-AB61-4F8B-A59D-E1483FF51B73@gmail.com>
References: <20120926113953.221020@gmx.com>
	<34C83EA2-7004-4D37-9674-ADFB4A475C07@gmail.com>
	<5526E5B0-DDCD-4D47-91B7-B3D4CA11A83E@gmail.com>
To: pgsql-performance@postgresql.org
X-Mailer: Apple Mail (2.1278)
X-Pg-Spam-Score: -2.7 (--)
X-Archive-Number: 201210/21
X-Sequence-Number: 47980

I am posting back to let you know that the DB is working fine since the =
changes in the autovacuum settings.

I am including the changes I made for later reference to anyone that may =
face similar issues.


Thank you all for your time and help !


On Sep 28, 2012, at 9:52, Kiriakos Tsourapas wrote:

> Dear all,
>=20
> Just letting you know that making the autovacuum policy more =
aggressive seems to have fixed the problem.
> It's been 4 days now and everything is running smoothly.
>=20
> Just a reminder, what I changed was :
> autovacuum_vacuum_scale_factor =3D 0.01
> autovacuum_analyze_scale_factor =3D 0.005
> making autovacuum run at 1% instead of 20% (the dafault) and the =
analyze run at 0,5% instead of 10%.
>=20
> Maybe it's more aggressive than needed... I will monitor and post =
back.
>=20
>=20
> Thank you all for your help.