public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Kevin Grittner <[email protected]>
Cc: [email protected]
Cc: Greg Stark <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Michael Tharp <[email protected]>
Cc: [email protected]
Cc: Craig Ringer <[email protected]>
Subject: Re: no universally correct setting for fsync
Date: Mon, 10 May 2010 15:57:42 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

"Kevin Grittner" <[email protected]> writes:
> Perhaps Josh's language for fsync could be modified to work here
> (we're now talking about full_page_writes, for anyone who's lost
> track):
 
> | it is only advisable to turn off fsync if you can easily recreate
> | your entire database from external data.

> That covers bulk loads to an empty or just-backed-up database and
> entirely redundant databases.  Saying it should never be turned off
> would tend to make one wonder why we have the setting at all.

+1.  Perhaps for both of them, we should specify that the intended
use-case is for improving performance during initial database load
and similar cases.

			regards, tom lane

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], [email protected], [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