From: Tom Lane <tgl@sss.pgh.pa.us>
To: Potentialtech <wmoran@potentialtech.com>
cc: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>,
 Forums postgresql <pgsql-general@postgresql.org>
Subject: Re: Checkpoint_segments optimal value
In-reply-to: <20140717140103.4e8c05e8ef5b89817b4d160a@potentialtech.com>
References: 
 <CAOf_bQYehfKp7CNRa_pYQ+-SmHyDSYJ8bddbaixXUcWmSjH6wA@mail.gmail.com>
 <20140717140103.4e8c05e8ef5b89817b4d160a@potentialtech.com>
Comments: In-reply-to Potentialtech <wmoran@potentialtech.com>
 message dated "Thu, 17 Jul 2014 14:01:03 -0400"
Date: Thu, 17 Jul 2014 14:06:28 -0400
Message-ID: <7639.1405620388@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

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.

			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