pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: David G Johnston <david.g.johnston@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Difference between fsync and open_sync
Date: Fri, 18 Apr 2014 22:24:47 -0400
Message-ID: <20140419022447.GB16260@momjian.us> (raw)
In-Reply-To: <1397793265476-5800669.post@n5.nabble.com>
References: <CAOqBXCBetP1Abp7S9GPar6Vp4tBGzLDDeN0hGM2kQXDyVTgadw@mail.gmail.com>
	<1397793265476-5800669.post@n5.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On Thu, Apr 17, 2014 at 08:54:25PM -0700, David G Johnston wrote:
> > And i understood the difference between, for example, fsync and fdatasync,
> > and between open_datasync and open_sync, but i cannot understand the
> > difference between open_sync and fsync or between open_datasync and
> > fdatasync , As far as i could understand, the open_* methods call the
> > open() method of linux, and f*sync methods calls the fsync() method of
> > linux?
> > 
> > My doubt is about what's the difference between them, or a link where this
> > is explained. In the previous link it talks about the 4 methods but i
> > cannot distinguish the difference between them.
> 
> fsync and open are both system functions for which documentation exists on
> the Internet.
> 
> Short answer seems to be that the physical write is guaranteed: open =
> immediately; fsync = at commit
> 
> As long as "fsync mode" is on after a commit command returns the WAL is
> promised to be physically written to disk; the means and speed of doing so
> vary according to the method chosen (limited by platform), the workload, the
> hardware, and the OS.
> 
> Others will correct any misunderstandings I may have acquired in my quick
> reading and reasoning.

The open* sync methods use a flag when the file is open that cause
_every_ write to be flushed to disk automatically.  The non-open* types
allow multiple writes and require a specific sync* command to be issued
when needed.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (3+ messages)

Message-ID: <20140419022447.GB16260@momjian.us>
Permalink:  ../20140419022447.GB16260@momjian.us/
Also on:    postgresql.org/message-id/20140419022447.GB16260@momjian.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bruce@momjian.us, david.g.johnston@gmail.com
  Subject: Re: Difference between fsync and open_sync
  In-Reply-To: <20140419022447.GB16260@momjian.us>
  References: <CAOqBXCBetP1Abp7S9GPar6Vp4tBGzLDDeN0hGM2kQXDyVTgadw@mail.gmail.com> <1397793265476-5800669.post@n5.nabble.com> <20140419022447.GB16260@momjian.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