public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Michael Tharp <[email protected]>
Cc: Craig Ringer <[email protected]>
Cc: [email protected]
Subject: Re: no universally correct setting for fsync
Date: Mon, 10 May 2010 11:12:35 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Michael Tharp wrote:
> On 05/08/2010 04:07 AM, Craig Ringer wrote:
> > It's probably worth mentioning that people who want to turn off fsync to
> > gain a performance boost should instead look at a RAID controller with a
> > BBU so they can safely enable write-back caching, getting most of the
> > benefits of fsync=off safely.
> 
> Which options specifically should be set if a BBU is in use? Obviously 
> fsync should be on always, but can full_page_writes be disabled? Are 
> there other tweaks that can be done?
> 
> It would be great to see some practical hints in the documentation while 
> the fsync part is getting changed.

Uh, our docs have:

	Turning this parameter off speeds normal operation, but might
	lead to a corrupt database after an operating system crash or
	power failure. The risks are similar to turning off
	<varname>fsync</>, though smaller.  It might be safe to turn
	off this parameter if you have hardware (such as a battery-backed
	disk controller) or file-system software that reduces the risk
	of partial page writes to an acceptably low level (e.g., ZFS).

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

view thread (35+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: no universally correct setting for fsync
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox