IndexedDB: fsync after transactions.

IndexedDB: fsync after transactions.

IndexedDB corruption rose, only on CrOS, in the 32 release. Included in
that release was a change that stopped calling fsync after transactions 
commit. It is the only IDB change that possibly sacrficed stability to get
better performance. So: revert it and see if corruption jumps back to 31
levels.

BUG=299831, 338385
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=247351

[dgrogan, 2014-01-27 21:16:39]

Josh, could you review this?

[jsbell, 2014-01-27 21:18:21]

lgtm

https://codereview.chromium.org/137423006/diff/1/content/browser/indexed_db/l...
File content/browser/indexed_db/leveldb/leveldb_database.cc (right):

https://codereview.chromium.org/137423006/diff/1/content/browser/indexed_db/l...
content/browser/indexed_db/leveldb/leveldb_database.cc:44: // Set _back_ to true
in attempt to fix corruption increase on CrOS devices.
Can you make this a TODO to either remove the #if block or reinstate the
difference?

[dgrogan, 2014-01-27 21:22:05]

https://codereview.chromium.org/137423006/diff/1/content/browser/indexed_db/l...
File content/browser/indexed_db/leveldb/leveldb_database.cc (right):

https://codereview.chromium.org/137423006/diff/1/content/browser/indexed_db/l...
content/browser/indexed_db/leveldb/leveldb_database.cc:44: // Set _back_ to true
in attempt to fix corruption increase on CrOS devices.
On 2014/01/27 21:18:22, jsbell wrote:
> Can you make this a TODO to either remove the #if block or reinstate the
> difference?

Done.

[commit-bot: I haz the power, 2014-01-27 21:23:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dgrogan@chromium.org/137423006/20001

[commit-bot: I haz the power, 2014-01-28 00:05:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dgrogan@chromium.org/137423006/20001

[commit-bot: I haz the power, 2014-01-28 00:24:36]

Change committed as 247351