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

Re: Configuring PostgreSQL to minimize impact of checkpoints

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Paul Tuckfield <paul(at)tuckfield(dot)com>
Cc: <jao(at)geophile(dot)com>, Matthew Nuzum <cobalt(at)bearfruit(dot)org>,<pgsql-performance(at)postgresql(dot)org>, Rob Fielding <rob(at)dsvr(dot)net>
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: 2004-05-11 22:07:36
Message-ID: Pine.LNX.4.33.0405111607090.23876-100000@css120.ihs.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Tue, 11 May 2004, Paul Tuckfield wrote:

> Love that froogle.
> 
> It looks like a nice card.     One thing I didn't get straight is if 
> the cache is writethru or write back.
> 
> If the original posters problem is truly a burst write problem (and not 
> linux caching or virtual memory overcommitment) then writeback is key.

the MegaRaid can be configured either way.  it defaults to writeback if 
the battery backed cache is present, I believe.


In response to

pgsql-performance by date

Next:From: scott.marloweDate: 2004-05-11 22:08:20
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Previous:From: Paul TuckfieldDate: 2004-05-11 21:52:57
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints

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