Re: Fwd: Apple Darwin disabled fsync?

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fwd: Apple Darwin disabled fsync?
Date: 2005-02-20 17:42:01
Message-ID: 87zmxzuo0m.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Peter Bierman <bierman(at)apple(dot)com> writes:

> > In most cases you do not need such a heavy handed operation and fsync() is
> > good enough.

Really? Can you think of a single application for which this definition of
fsync is useful?

Kernel buffers are transparent to the application, just as the disk buffer is.
It doesn't matter to an application whether the data is sitting in a kernel
buffer, or a buffer in the disk, it's equivalent. If fsync doesn't guarantee
the writes actually end up on non-volatile disk then as far as the application
is concerned it's just an expensive noop.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2005-02-20 18:31:11 Re: win32 performance - fsync question
Previous Message Tom Lane 2005-02-20 17:30:51 Re: Get rid of system attributes in pg_attribute?