3,035
edits
Breakpad/Design/Database: Difference between revisions
Jump to navigation
Jump to search
→Breakpad Database
No edit summary |
|||
| Line 32: | Line 32: | ||
* Ignore stuff we haven't already accounted for, which ensures ACID but could eliminate things we "forgot" to prefill | * Ignore stuff we haven't already accounted for, which ensures ACID but could eliminate things we "forgot" to prefill | ||
I am not sure if this is the same problem as below -- I'd like to talk more about this in the meeting: | I am not sure if this is the same problem as below -- I'd like to talk more about this in the meeting (this was on this page from before): | ||
Using the same database and schema for the minidump data and also for control over the processing of the minidumps has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of minidumps, the processing of incoming minidumps is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design. | * Using the same database and schema for the minidump data and also for control over the processing of the minidumps has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of minidumps, the processing of incoming minidumps is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design. | ||