Re: Checkpoint_segments optimal value - Mailing list pgsql-general

From Tom Lane
Subject Re: Checkpoint_segments optimal value
Date
Msg-id 7639.1405620388@sss.pgh.pa.us
Whole thread Raw
In response to Re: Checkpoint_segments optimal value  (Potentialtech <wmoran@potentialtech.com>)
Responses Re: Checkpoint_segments optimal value  (Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>)
Re: Checkpoint_segments optimal value  (Potentialtech <wmoran@potentialtech.com>)
List pgsql-general
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


pgsql-general by date:

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