pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Mark Lewis <mark.lewis@mir3.com>
To: Dan Gorman <dgorman@hi5.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres fsync off (not needed) with NetApp
Date: Wed, 14 Jun 2006 14:54:45 -0700
Message-ID: <1150322085.31200.39.camel@archimedes> (raw)
In-Reply-To: <9A377C54-361D-4F01-BF7A-7632FBA3453C@hi5.com>
References: <9A377C54-361D-4F01-BF7A-7632FBA3453C@hi5.com>

No.  You need fsync on in order to force the data to get TO the NetApp
at the right time.  With fsync off, the data gets cached in the
operating system.

-- Mark Lewis

On Wed, 2006-06-14 at 14:48 -0700, Dan Gorman wrote:
> All,
>    So I thought I'd pose this question:
> 
> If I have a pg database attached to a powervault (PV) with just an  
> off-the-shelf SCSI card I generally want fsync on to prevent data  
> corruption in case the PV should loose power.
> However, if I have it attached to a NetApp that ensures data writes  
> to via the NVRAM can I safely turn fsync off to gain additional  
> performance?
> 
> Best Regards,
> Dan Gorman
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster



view thread (11+ messages)  latest in thread

Message-ID: <1150322085.31200.39.camel@archimedes>
Permalink:  ../1150322085.31200.39.camel@archimedes/
Also on:    postgresql.org/message-id/1150322085.31200.39.camel@archimedes

 · 

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: mark.lewis@mir3.com, dgorman@hi5.com
  Subject: Re: Postgres fsync off (not needed) with NetApp
  In-Reply-To: <1150322085.31200.39.camel@archimedes>

* 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