From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Potentialtech <wmoran(at)potentialtech(dot)com> |
Cc: | Prabhjot Sheena <prabhjot(dot)sheena(at)rivalwatch(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Checkpoint_segments optimal value |
Date: | 2014-07-17 18:06:28 |
Message-ID: | 7639.1405620388@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Potentialtech <wmoran(at)potentialtech(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Prabhjot Sheena | 2014-07-17 18:28:04 | Re: Checkpoint_segments optimal value |
Previous Message | Potentialtech | 2014-07-17 18:01:03 | Re: Checkpoint_segments optimal value |
From | Date | Subject | |
---|---|---|---|
Next Message | Prabhjot Sheena | 2014-07-17 18:28:04 | Re: Checkpoint_segments optimal value |
Previous Message | Potentialtech | 2014-07-17 18:01:03 | Re: Checkpoint_segments optimal value |