pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: guoping.zhang@nec.com.au, pgsql-performance@postgresql.org, "Guoping Zhang (E-mail)" <guopingz@nstc.nec.com.au>
Subject: Re: how unsafe (or worst scenarios) when setting fsync
Date: Thu, 27 Apr 2006 10:57:46 -0400
Message-ID: <11142.1146149866@sss.pgh.pa.us> (raw)
In-Reply-To: <1146121984.3120.56.camel@localhost.localdomain>
References: <003b01c669c4$34bbd7b0$74304c93@eddy>
	<1146121984.3120.56.camel@localhost.localdomain>

Simon Riggs <simon@2ndquadrant.com> writes:
> On Thu, 2006-04-27 at 16:31 +1000, Guoping Zhang wrote:
>> Can we set fsync OFF for the performance benefit, have the risk of only 5
>> minutes data loss or much worse?

> Thats up to you. 

> fsync can be turned on and off, so you can make critical changes with
> fsync on, then continue with fsync off.

I think it would be a mistake to assume that the behavior would be
nice clean "we only lost recent changes".  Things could get arbitrarily
badly corrupted if some writes make it to disk and some don't.

			regards, tom lane



view thread (14+ messages)  latest in thread

Message-ID: <11142.1146149866@sss.pgh.pa.us>
Permalink:  ../11142.1146149866@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11142.1146149866@sss.pgh.pa.us

 · 

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: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, guopingz@nstc.nec.com.au
  Subject: Re: how unsafe (or worst scenarios) when setting fsync
  In-Reply-To: <11142.1146149866@sss.pgh.pa.us>

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

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