Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: re Direct IO -- was RE: Important note about asynchronous commit

RE: re Direct IO -- was RE: Important note about asynchronous commit

From: Kevin Closson <kevinc_at_polyserve.com>
Date: Tue, 26 Sep 2006 11:24:55 -0700
Message-ID: <5D2570CAFC98974F9B6A759D1C74BAD0E5B179@ex2.ms.polyserve.com>

>>>
>>>Oracle should always be opening the files with O_DSYNC.

Port specific since O_DSYNC is largely a Solaris API extention. Don't code that on Linux with Glibc :-)

Fact is if Oracle is running on a *supported* OS and the files are in buffered filesystems, there WILL ALWAYS be an API used to ensure certain writes are synced. It varies by port from open(O_SYNC) to calling fsync(). That latter being done in a couple of really old ports to address bugs in open(O_SYNC) because heaven knows fsync is not better for the job than an O_SYNC open.

In the end, it is all spam. Databases like Oracle should be suing direct I/O for heaven's sake.

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Sep 26 2006 - 13:24:55 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US