Re: checkpoint_timeout

From: "Rafael Domiciano" <rafael(dot)domiciano(at)gmail(dot)com>
To: "Brad Nicholson" <bnichols(at)ca(dot)afilias(dot)info>
Cc: chirag(dot)dave(at)gmail(dot)com, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: checkpoint_timeout
Date: 2008-10-08 14:34:00
Message-ID: 3a0028490810080734r26912c72n94d6f509dfb55b6e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello Brad,

All of my bgwriter parameters is set on default. Following:#bgwriter_delay =
200ms # 10-10000ms between rounds
#bgwriter_lru_percent = 1.0 # 0-100% of LRU buffers
scanned/round
#bgwriter_lru_maxpages = 5 # 0-1000 buffers max written/round
#bgwriter_all_percent = 0.333 # 0-100% of all buffers
scanned/round
#bgwriter_all_maxpages = 5 # 0-1000 buffers max written/round

I am trying now to increase the checkpoint_segments to 40...

2008/10/8 Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>

> On Wed, 2008-10-08 at 10:31 -0200, Rafael Domiciano wrote:
> > The server is running Postgres 8.2.4
> > When the server is doing too much operations like I, U or D the
> > postgres stop a while each 5 min...!
> > I mean "stopping" that I don't receive any response from postgres, and
> > the process the all people are running stay there, waiting for
> > something.
> > I read a several names to it like: gap, stall, slowdown... I don't
> > know the write expression for this situation.
>
> The bgwriter was added to help alleviate this problem.
>
> What are your settings for that? The solution may be to push dirty
> buffers to disk more aggressively via the bgwriter so you have less work
> to do at checkpoint time.
>
>
> --
> Brad Nicholson 416-673-4106
> Database Administrator, Afilias Canada Corp.
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Martin Badie 2008-10-08 15:10:11 replication with table add/removes..
Previous Message Brad Nicholson 2008-10-08 14:23:00 Re: checkpoint_timeout