From: Greg Smith <greg@2ndquadrant.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: jd@commandprompt.com, Scott Marlowe <scott.marlowe@gmail.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org, Ben Chobot <bench@silentmedia.com>
Subject: Re: BBU Cache vs. spindles
Date: Thu, 21 Oct 2010 13:31:09 -0400
Message-ID: <4CC078DD.3010107@2ndquadrant.com> (raw)
In-Reply-To: <4CC02ED30200002500036C24@gw.wicourts.gov>
References: <4CC02A520200002500036C14@gw.wicourts.gov>
<201010211659.o9LGxkV01781@momjian.us>
<4CC02ED30200002500036C24@gw.wicourts.gov>
Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.us> wrote:
>
>
>> full_page_writes is designed to guard against a partial write to a
>> device. I don't think the raid cache can be partially written to
>>
>
> So you're confident that an 8kB write to the controller will not be
> done as a series of smaller atomic writes by the OS file system?
Sure, that happens. But if the BBU has gotten an fsync call after the
8K write, it shouldn't return success until after all 8K are in its
cache. That's why full_page_writes should be safe on a system with BBU
as Bruce is suggesting. But I'd like to see some independent proof of
that fact, that includes some targeted tests users can run, before we
start recommending that practice.
--
Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
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-performance@postgresql.org
Cc: greg@2ndquadrant.com, Kevin.Grittner@wicourts.gov, bruce@momjian.us, scott.marlowe@gmail.com, scrawford@pinpointresearch.com, bench@silentmedia.com
Subject: Re: BBU Cache vs. spindles
In-Reply-To: <4CC078DD.3010107@2ndquadrant.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