Re: Checkpoint_segments optimal value - Mailing list pgsql-general

From Potentialtech
Subject Re: Checkpoint_segments optimal value
Date
Msg-id 20140717145322.0029297552ba3c692c52a96f@potentialtech.com
Whole thread Raw
In response to Re: Checkpoint_segments optimal value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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>


pgsql-general by date:

Previous
From: Prabhjot Sheena
Date:
Subject: Re: Checkpoint_segments optimal value
Next
From: Potentialtech
Date:
Subject: Re: Checkpoint_segments optimal value