7 check-ins related to "oom-handling"
|14:11||Improvements to the way out-of-memory conditions are handled, resulting in an almost 1% performance gain in the commmon case where OOM errors do not occur. check-in: b082538da7 user: drh tags: trunk|
|13:38||Add the slightly faster sqlite3DbMallocRawNN(db,n) routine for the majority cases where db is guaranteed to be not NULL. Closed-Leaf check-in: 0a802e96ab user: drh tags: oom-handling|
|04:50||OOM failures on sqlite3_errmsg16() in an app-defined function are no longer benign. check-in: 9efb223f4c user: drh tags: oom-handling|
|02:50||Minor simplification of schema error reporting. check-in: a8846aeed9 user: drh tags: oom-handling|
|02:42||Further performance improvements that fall out of the mallocFailed changes. check-in: d94416ddca user: drh tags: oom-handling|
|01:55||Improvements to the way that OOM errors are processed. check-in: c3ef03478a user: drh tags: oom-handling|
|19:50||Temporarily back out the 0.5% performance improvement from check-in [632071bac5ff32]. Need a more elaborate solution that works with reentrant virtual tables and SQL functions. check-in: 42736fb0ad user: drh tags: trunk|