Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Postgres fsync off (not needed) with NetApp
- From: "Jonah H. 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: Thu, 15 Jun 2006 01:14:26 -0400
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/
- Follow-Ups:
- Re: Postgres fsync off (not needed) with NetApp
- From: Jim C. Nasby
- Re: Postgres fsync off (not needed) with NetApp
- From: Dan Gorman
- Re: Postgres fsync off (not needed) with NetApp
- References:
- Postgres fsync off (not needed) with NetApp
- From: Dan Gorman
- Re: Postgres fsync off (not needed) with NetApp
- From: Mark Lewis
- Re: Postgres fsync off (not needed) with NetApp
- From: Greg Stark
- Postgres fsync off (not needed) with NetApp
- Prev by Date: Re: Precomputed constants?
- Next by Date: Re: Postgres fsync off (not needed) with NetApp
- Previous by thread: Re: Postgres fsync off (not needed) with NetApp
- Next by thread: Re: Postgres fsync off (not needed) with NetApp
- Indexes: