All I can say is that the overhead of that approach is enormous (which is why PostgreSQL makes it optional, I suppose), and if you check what you've written to disk after you've written it (checksums), the full-page write to an alternative location should not really be necessary. DBWR does that. And
mysql innodb use "Double Write" to prevent partial write. http://www.mysqlperformanceblog.com/2006/08/04/innodb-double-write/ But oracle doesn't have "Double Write", so what's the mechanism in orac...
All I can say is that the overhead of that approach is enormous (which is why PostgreSQL makes it optional, I suppose), and if you check what you've written to disk after you've written it (checksums), the full-page write to an alternative location should not really be necessary. DBWR does that. And
このブックマークにはスターがありません。
最初のスターをつけてみよう！
how oracle prevent "partial write"
mysql innodb use "Double Write" to prevent partial write. http://www.mysqlperformanceblog.com/2006/08/04/innodb-double-write/ But oracle doesn't have "Double Write", so what's the mechanism in orac...
7 人がブックマーク・3 件のコメント
＼ コメントが サクサク読める アプリです ／