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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-performance by date

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