Re: Filesystem Direct I/O and WAL sync option - Mailing list pgsql-performance

From Dimitri
Subject Re: Filesystem Direct I/O and WAL sync option
Date
Msg-id 5482c80a0707030826v38c59870ib90599ba43337e72@mail.gmail.com
Whole thread Raw
In response to Re: Filesystem Direct I/O and WAL sync option  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Filesystem Direct I/O and WAL sync option
List pgsql-performance
Yes, disk drives are also having cache disabled or having cache on
controllers and battery protected (in case of more  high-level
storage) - but is it enough to expect data consistency?... (I was
surprised about checkpoint sync, but does it always calls write()
anyway? because in this way it should work without fsync)...

On 7/3/07, Heikki Linnakangas <heikki@enterprisedb.com> wrote:
> Dimitri wrote:
> > I'm very curious to know if we may expect or guarantee any data
> > consistency with WAL sync=OFF but using file system mounted in Direct
> > I/O mode (means every write() system call called by PG really writes
> > to disk before return)...
>
> You'd have to turn that mode on on the data drives as well to get
> consistency, because fsync=off disables checkpoint fsyncs of the data
> files as well.
>
> --
>    Heikki Linnakangas
>    EnterpriseDB   http://www.enterprisedb.com
>

pgsql-performance by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Filesystem Direct I/O and WAL sync option
Next
From: Mark Lewis
Date:
Subject: Re: Delete Cascade FK speed issue