From: | Dimitri <dimitrik(dot)fr(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "PostgreSQL Performance" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Filesystem Direct I/O and WAL sync option |
Date: | 2007-07-03 15:26:55 |
Message-ID: | 5482c80a0707030826v38c59870ib90599ba43337e72@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)enterprisedb(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Lewis | 2007-07-03 16:01:05 | Re: Delete Cascade FK speed issue |
Previous Message | Heikki Linnakangas | 2007-07-03 15:06:29 | Re: Filesystem Direct I/O and WAL sync option |