Skip site navigation (1) Skip section navigation (2)

Re: checkpoint_timeout

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Rafael Domiciano" <rafael(dot)domiciano(at)gmail(dot)com>
Cc: "Julio Leyva" <jcleyva(at)hotmail(dot)com>,"pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: checkpoint_timeout
Date: 2008-10-08 18:08:46
Message-ID: 48ECB0DD.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
>>> "Rafael Domiciano" <rafael(dot)domiciano(at)gmail(dot)com> wrote: 
> Right...I going to restart my server only tonight, the access along
the day
> is too much to do now...!
> Maybe increasing a little bit could do difference?
> I thougth to increase to around 256 Kb!
> I have a doubt... what's the chance to my server get instable?
 
Changing wal_buffers to that isn't at all likely to cause problems,
unless you are teetering right on the edge of exceeding your shmmax
setting.  It's also unlikely to help much, in my opinion.
 
If the problem is checkpoints (which seems likely but far from a sure
thing based on the information provided), aggressive background writer
setting might be your best bet under 8.2.X.  To solve similar problems
we had to go to the following, although many on these lists feel that
settings this aggressive are rarely needed, so use at your own risk.
 
#bgwriter_delay = 200ms
bgwriter_lru_percent = 20.0
bgwriter_lru_maxpages = 200
bgwriter_all_percent = 10.0
bgwriter_all_maxpages = 600
 
Even better would be to go to the latest revision of the 8.3 release,
which at this writing is 8.3.4.  In that release PostgreSQL spreads
out the work of a checkpoint to minimize this problem.
 
-Kevin

In response to

Responses

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-10-08 18:16:33
Subject: Re: checkpoint_timeout
Previous:From: Rafael DomicianoDate: 2008-10-08 17:54:27
Subject: Re: checkpoint_timeout

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group