pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Mark Lewis <mark.lewis@mir3.com>
Cc: Dan Gorman <dgorman@hi5.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres fsync off (not needed) with NetApp
Date: Thu, 15 Jun 2006 10:54:20 -0500
Message-ID: <20060615155420.GK34196@pervasive.com> (raw)
In-Reply-To: <36e682920606142214i6a6532f3k1a895a784f7b16dc@mail.gmail.com>
References: <9A377C54-361D-4F01-BF7A-7632FBA3453C@hi5.com>
	<1150322085.31200.39.camel@archimedes>
	<873be7ay8u.fsf@stark.xeocode.com>
	<36e682920606142214i6a6532f3k1a895a784f7b16dc@mail.gmail.com>

On Thu, Jun 15, 2006 at 01:14:26AM -0400, Jonah H. Harris wrote:
> On 14 Jun 2006 23:33:53 -0400, Greg Stark <gsstark@mit.edu> wrote:
> >In fact the benefit of the NVRAM is precisely that it makes sure you 
> >*don't*
> >have any reason to turn fsync off. It should make the fsync essentially 
> >free.
> 
> Having run PostgreSQL on a NetApp with input from NetApp, this is
> correct.  fsync should be turned on, but you will not incur the *real*
> direct-to-disk cost of the sync, it will be direct-to-NVRAM.

Just so there's no confusion... this applies to any caching RAID
controller as well. You just need to ensure that the cache in the
controller absolutely will not be lost in the event of a power failure
or what-have-you. On most controllers this is accomplished with a simple
battery backup; I don't know if the higher-end stuff takes further steps
(such as flashing the cache contents to flash memory on a power
failure).
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (11+ messages)

Message-ID: <20060615155420.GK34196@pervasive.com>
Permalink:  ../20060615155420.GK34196@pervasive.com/
Also on:    postgresql.org/message-id/20060615155420.GK34196@pervasive.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jnasby@pervasive.com, jonah.harris@gmail.com, gsstark@mit.edu, mark.lewis@mir3.com, dgorman@hi5.com
  Subject: Re: Postgres fsync off (not needed) with NetApp
  In-Reply-To: <20060615155420.GK34196@pervasive.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