Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Postgres fsync off (not needed) with NetApp
- From: Greg Stark <gsstark(at)mit(dot)edu>
- To: Mark Lewis <mark(dot)lewis(at)mir3(dot)com>
- Cc: Dan Gorman <dgorman(at)hi5(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Postgres fsync off (not needed) with NetApp
- Date: 14 Jun 2006 23:33:53 -0400
Mark Lewis <mark(dot)lewis(at)mir3(dot)com> writes: > On Wed, 2006-06-14 at 14:48 -0700, Dan Gorman wrote: > > > > 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? > > 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. 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. -- greg
- Follow-Ups:
- Re: Postgres fsync off (not needed) with NetApp
- From: Jonah H. Harris
- 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
- Postgres fsync off (not needed) with NetApp
- Prev by Date: Re: Confirmation of bad query plan generated by 7.4
- Next by Date: Re: Precomputed constants?
- Previous by thread: Re: Postgres fsync off (not needed) with NetApp
- Next by thread: Re: Postgres fsync off (not needed) with NetApp
- Indexes: