-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

~From everything I read from Anne. Out of order writes are what cause
the db corruption. If there is FIFO disk cache then you might not have
the must up to date records, but the database wouldn't be corrupted. It
would essentially be like the database is in the state that it was a few
seconds ago. Its more of a time delay than anything else I believe.
Assuming a FIFO disk cache.

Alan McDonald wrote:

|>Hi again!
|>
|>There's one little point I forgot to make in my previous post.
|>
|>There are now filesystems that garantee the order of asynchronous write
|>(LinLogFS, and, I think, ReiserFS v4). On such file systems, would it be
|>safe to turn ForcedWrites off, thus gaining a lot of performance?
|>
|>Thanks!
|>
|>Jonathan Neve.
|
|
| I don't think it's the order per se that's important as much as it is
the OS
| making untimely writes. Forced writes on Windows is important because
| windows will cache it's writes and it is not as reliable as Linux in the
| server stakes. Let's not forget that OS's do not know how to recognise the
| boundary of database transactions. The database server is the only thing
| which knows this.
| Alan
|
|
|
|
|
| Yahoo! Groups Links
|
|
|
|
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)

iD8DBQFAcWitvWeCZ4RLdzYRAjyrAJ9WR4CFKoA7C0TiBdfuTOzHFj8iAQCeO0cw
/ziA167t6/wYZhIWoW+LbIU=
=+gf8
-----END PGP SIGNATURE-----