DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
	h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=ximGV9lwaxd0Fr6+qSHI8TJh2f8OiMblYjoNcsJs0fQdI0x1xKXDNBItyG0qGiZNGP3qyeJElptT75sUV0QYWS+i/SiC4L+oJ57p/gwAHgp4uHa2djUMBlNtN0bk7T0USGkbuD/1vOjIDXTXP6s2k4cHAUQmY/xzvMwwK5mVMH4=;
References: 
 <CABMVzL2y8mRM5C9xxejAyDqe0i1S78RAE3cEATGYNf5Ktz_Zdg@mail.gmail.com>
	<CAB6McgXMFS2XD_inm5LMSmZpYMoXm8mzF6t3JXVyJAqi_-98OA@mail.gmail.com>
	<CABMVzL3mmx8KOBCrVQzff3FciXg_DJGULd4f3an4a417FUb1XQ@mail.gmail.com>
	<CAB6McgUt0tBgZCYjRKgpPt41XPYLXwA8tcXDTp_vLTvwA1m30w@mail.gmail.com>
	<13A05E96-01A0-4B0A-8EA3-2A3B7FDF6838@hsk.hk>
	<1360154987.89420.YahooMailNeo@web162901.mail.bf1.yahoo.com>
	<CABMVzL0j=quCGWEdHO922kOjzmbqA7CntwMtE6abT=cx+sZaxQ@mail.gmail.com>
Message-ID: <1360185170.99635.YahooMailNeo@web162903.mail.bf1.yahoo.com>
Date: Wed, 6 Feb 2013 13:12:50 -0800 (PST)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: postgresql.conf recommendations
To: Johnny Tan <johnnydtan@gmail.com>
Cc: "ac@hsk.hk" <ac@hsk.hk>, Josh Krupka <jkrupka@gmail.com>,
	Alex Kahn <alex@paperlesspost.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
In-Reply-To: 
 <CABMVzL0j=quCGWEdHO922kOjzmbqA7CntwMtE6abT=cx+sZaxQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Johnny Tan <johnnydtan@gmail.com> wrote:

> Wouldn't this be controlled by our checkpoint settings, though?=20

Spread checkpoints made the issue less severe, but on servers with
a lot of RAM I've had to make the above changes (or even go lower
with shared_buffers) to prevent a burst of writes from overwhelming
the RAID controllers battery-backed cache.=A0 There may be other
things which could cause these symptoms, so I'm not certain that
this will help; but I have seen this as the cause and seen the
suggested changes help.

-Kevin


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