Re: Postgres fsync off (not needed) with NetApp

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Greg Stark" <gsstark(at)mit(dot)edu>
Cc: "Mark Lewis" <mark(dot)lewis(at)mir3(dot)com>, "Dan Gorman" <dgorman(at)hi5(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres fsync off (not needed) with NetApp
Date: 2006-06-15 05:14:26
Message-ID: 36e682920606142214i6a6532f3k1a895a784f7b16dc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 14 Jun 2006 23:33:53 -0400, Greg Stark <gsstark(at)mit(dot)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.

--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dan Gorman 2006-06-15 05:20:25 Re: Postgres fsync off (not needed) with NetApp
Previous Message Zoltan Boszormenyi 2006-06-15 04:31:02 Re: Precomputed constants?