Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
9 check-ins related to "analyze-worst-case"
|19:55||Simplify the computation of Index.aAvgEq. Leaf check-in: c4488730 user: drh tags: analyze-worst-case|
|18:45||Merge changes from trunk. check-in: 5294c977 user: drh tags: analyze-worst-case|
|14:43||Defer opening and writing statement journals until the size reaches a threshold (currently 64KiB). check-in: cb9302cc user: drh tags: trunk|
|14:31||Change the estimated row counts in stat1 to be one-third worst-case and two-threads average case. check-in: 21bfd47c user: drh tags: analyze-worst-case|
|12:45||Fix test cases to align with the improved stats computation. check-in: 810967bf user: drh tags: analyze-worst-case|
|23:02||Improvements to the logic for adding the "noskipscan" flag to stat1 entries. check-in: 421b5b54 user: drh tags: analyze-worst-case|
|21:27||The ANALYZE command automatically appends "noskipscan" to sqlite_stat1 entries that have large worst-case repeat estimates but small average repeat estimates. check-in: 6326ba58 user: drh tags: analyze-worst-case|
|18:30||Modify the ANALYZE command to store worst-case statistics in sqlite_stat1, rather thn average case. check-in: 5a0143c9 user: drh tags: analyze-worst-case|
|17:34||Fix a problem in fts5 where a corrupt db could lead to a (huge) buffer overread. check-in: c9a30e11 user: dan tags: trunk|