Re: Database writing architecture

In article <4kpjqg$td_at_inet-nntp-gw-1.us.oracle.com>, pzola_at_us.oracle.com (Paul Zola ) writes: ...
|>
|> I have no direct experience with Sybase, so I can't say for sure
|> whether or not Sybase runs the risk of database corruption when using
|> filesystem files. If true, there's no inherent limitation in UNIX that
|> makes this so.

fsync() has been around for ages, so there must be some other reason Sybase makes disclaimers about using filesystem files. With regards to raw files, unbuffered doesn't necessarily mean that the i/o isn't reordered by the device driver. If so then fsync() is required also. Or do the official raw device semantics preclude this?
|>
|> -p
|>
|> ==============================================================================
|> Paul Zola Technical Specialist
|> World-Wide Technical Support Development Tools
|> ==============================================================================
|> Computers possess the truly profound stupidity of the inanimate. - B. Sterling
|> Disclaimer: Opinions and statements are mine, and do not necessarily
|> reflect the opinions of Oracle Corporation.

-- 
Joe Seigh	seigh_at_bose.com
-- 
Joe Seigh	seigh_at_bose.com