From: Rafael Domiciano <rafael.domiciano@gmail.com>
To: Julio Leyva <jcleyva@hotmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: checkpoint_timeout
Date: Wed, 8 Oct 2008 14:34:05 -0200
Message-ID: <3a0028490810080934l211d137uc9dde69cad7879d9@mail.gmail.com> (raw)
In-Reply-To: <BLU102-W420C4D08216238B5121B32A13B0@phx.gbl>
References: <3a0028490810071321j32b4f450m95123d02b9fe6f49@mail.gmail.com>
<f1d4f3170810071413l3bb62167n2fa32a8ab1ec6dc@mail.gmail.com>
<3a0028490810080531y155edffi7ff7c68b965a834a@mail.gmail.com>
<1223475780.6070.10.camel@bnicholson-desktop>
<3a0028490810080734r26912c72n94d6f509dfb55b6e@mail.gmail.com>
<BLU102-W53021316E8139B5A348338A13B0@phx.gbl>
<3a0028490810080919v3762f924je688a56210558e95@mail.gmail.com>
<BLU102-W420C4D08216238B5121B32A13B0@phx.gbl>
The wal_buffers is 64Kb (The default)...What Does wal_buffers do?
2008/10/8 Julio Leyva <jcleyva@hotmail.com>
> well it depends , our D.B is really high in transactions, and
> checkpoints_segments along with the wal_buffers are ok. you need to play
> with both of them
>
>
>
>
>
>
> ------------------------------
> Date: Wed, 8 Oct 2008 14:19:37 -0200
> From: rafael.domiciano@gmail.com
> To: jcleyva@hotmail.com
> Subject: Re: [ADMIN] checkpoint_timeout
> CC: bnichols@ca.afilias.info; chirag.dave@gmail.com;
> pgsql-admin@postgresql.org
>
>
> Hello Julio,
> If I set my postgresql server to checkpoint_segments = 10 aren't going to
> be poor segments?
>
>
> 2008/10/8 Julio Leyva <jcleyva@hotmail.com>
>
> We have a transactional D.B writing directly to postgres (8.3) and these
> parameters have worked ok for us
>
>
> checkpoint_timeout = 5min
> checkpoint_segments = 10
> wal_buffers = 1024kB
>
>
>
> ------------------------------
> Date: Wed, 8 Oct 2008 12:34:00 -0200
> From: rafael.domiciano@gmail.com
> To: bnichols@ca.afilias.info
> Subject: Re: [ADMIN] checkpoint_timeout
> CC: chirag.dave@gmail.com; pgsql-admin@postgresql.org
>
>
> 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@ca.afilias.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.
>
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rafael.domiciano@gmail.com, jcleyva@hotmail.com
Subject: Re: checkpoint_timeout
In-Reply-To: <3a0028490810080934l211d137uc9dde69cad7879d9@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox