Date: Thu, 17 Jul 2014 14:53:22 -0400
From: Potentialtech <wmoran@potentialtech.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>, Forums postgresql
 <pgsql-general@postgresql.org>
Subject: Re: Checkpoint_segments optimal value
Message-Id: <20140717145322.0029297552ba3c692c52a96f@potentialtech.com>
In-Reply-To: <7639.1405620388@sss.pgh.pa.us>
References: 
 <CAOf_bQYehfKp7CNRa_pYQ+-SmHyDSYJ8bddbaixXUcWmSjH6wA@mail.gmail.com>
 <20140717140103.4e8c05e8ef5b89817b4d160a@potentialtech.com>
 <7639.1405620388@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

On Thu, 17 Jul 2014 14:06:28 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Potentialtech <wmoran@potentialtech.com> writes:
> > If the warning isn't happening too often, I would try increasing it only a
> > little and see if it helps.  If it's not enough you can then increase it some
> > more.  Various sources around the Internet suggest that you don't want to go
> > much larger than 256 for this (if only because it's uncommon to do so and is
> > probably indicative of other tuning that you need to do).  Unfortunatley, you
> > need to restart PG for the change to take effect, so you have to balance
> > experimenting with your tuning against how often you can get away with a server
> > restart.
> 
> Huh?  You don't need a restart, just a reload (SIGHUP) to change that.

Really?  Well, thanks for correcting me on that.

-- 
Potentialtech <wmoran@potentialtech.com>


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