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

  • From: "Kevin Closson" <kevinc@xxxxxxxxxxxxx>
  • To: "Oracle-L Freelists" <Oracle-L@xxxxxxxxxxxxx>
  • Date: Tue, 26 Sep 2006 11:24:55 -0700

>>>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

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


Other related posts: