pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Greg Smith <greg@2ndquadrant.com>
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: Tue, 30 Nov 2010 22:13:12 -0500 (EST)
Message-ID: <201012010313.oB13DCu03542@momjian.us> (raw)
In-Reply-To: <4CC14F6A0200002500036CAB@gw.wicourts.gov>

Kevin Grittner wrote:
> Greg Smith <greg@2ndquadrant.com> wrote:
>  
> > I think Kevin's point here may be that if your fsync isn't
> > reliable, you're always in trouble.  But if your fsync is good,
> > even torn pages should be repairable by the deltas written to the
> > WAL
>  
> I was actually just arguing that a BBU doesn't eliminate a risk
> here; if there is a risk with production-quality disk drives, there
> is a risk with a controller with a BBU cache.  The BBU cache just
> tends to reduce the window of time in which corruption can occur.  I
> wasn't too sure of *why* there was a risk, but Tom's post cleared
> that up.
>  
> I wonder why we need to expose this GUC at all -- perhaps it should
> be off when fsync is off and on otherwise?  Leaving it on without
> fsync is just harming performance for not much benefit, and turning
> it off with fsync seems to be saying that you are willing to
> tolerate a known risk of database corruption, just not quite so much
> as you have without fsync.  In reality it seems most likely to be a
> mistake, either way.

According to our docs, and my submitted patch, if you are using ZFS then
you can turn off full-page writes, so full-page writes are still useful.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +



view thread (61+ messages)  latest in thread

Message-ID: <201012010313.oB13DCu03542@momjian.us>
Permalink:  ../201012010313.oB13DCu03542@momjian.us/
Also on:    postgresql.org/message-id/201012010313.oB13DCu03542@momjian.us

 · 

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: bruce@momjian.us, Kevin.Grittner@wicourts.gov, greg@2ndquadrant.com, scott.marlowe@gmail.com, scrawford@pinpointresearch.com, bench@silentmedia.com
  Subject: Re: BBU Cache vs. spindles
  In-Reply-To: <201012010313.oB13DCu03542@momjian.us>
  References: <4CC14F6A0200002500036CAB@gw.wicourts.gov> <201012010313.oB13DCu03542@momjian.us>

* 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