pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Greg Smith <greg@2ndquadrant.com>
Cc: jd@commandprompt.com
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org
Cc: Ben Chobot <bench@silentmedia.com>
Subject: Re: BBU Cache vs. spindles
Date: Thu, 21 Oct 2010 13:54:03 -0500
Message-ID: <4CC045FB0200002500036C4B@gw.wicourts.gov> (raw)
In-Reply-To: <4CC078DD.3010107@2ndquadrant.com>
References: <4CC02A520200002500036C14@gw.wicourts.gov>
	<201010211659.o9LGxkV01781@momjian.us>
	<4CC02ED30200002500036C24@gw.wicourts.gov>
	<4CC078DD.3010107@2ndquadrant.com>

Greg Smith <greg@2ndquadrant.com> wrote: 
> Kevin Grittner wrote:
 
>> 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.
 
I'm not concerned about an fsync after the controller has it; I'm
concerned about a system crash in the middle of writing an 8K page
to the controller.  Other than the expected *size* of the window of
time during which you're vulnerable, what does a BBU caching
controller buy you in this regard?  Can't the OS rearrange the
writes of disk sectors after the 8K page is written to the OS cache
so that the window might occasionally be rather large?
 
-Kevin



view thread (61+ messages)  latest in thread

Message-ID: <4CC045FB0200002500036C4B@gw.wicourts.gov>
Permalink:  ../4CC045FB0200002500036C4B@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4CC045FB0200002500036C4B@gw.wicourts.gov

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, greg@2ndquadrant.com, jd@commandprompt.com, scott.marlowe@gmail.com, bruce@momjian.us, scrawford@pinpointresearch.com, bench@silentmedia.com
  Subject: Re: BBU Cache vs. spindles
  In-Reply-To: <4CC045FB0200002500036C4B@gw.wicourts.gov>
  References: <4CC02A520200002500036C14@gw.wicourts.gov> <201010211659.o9LGxkV01781@momjian.us> <4CC02ED30200002500036C24@gw.wicourts.gov> <4CC078DD.3010107@2ndquadrant.com> <4CC045FB0200002500036C4B@gw.wicourts.gov>

* 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