Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
Places:FsyncApproach: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
Cons: | Cons: | ||
= | =Split Database Approach= | ||
From Shaver: | |||
<blockquote>We could also just use two databases, one for history (with sync=off) and one for bookmarks (with sync=normal) and query against them both. Then you would get an fsync/s_f_r only when you updated a bookmark, and not during normal browser operation, and we would not be risking loss of bookmark data during crash.</blockquote> | |||
Pros: | |||
Cons: | |||