Closed
Bug 1639252
Opened 6 years ago
Closed 1 year ago
Use PRAGMA analysis_limit=N before PRAGMA optimize
Categories
(Toolkit :: Places, task, P3)
Toolkit
Places
Tracking
()
RESOLVED
INVALID
People
(Reporter: mak, Assigned: jteow)
References
Details
Attachments
(1 obsolete file)
This is just an optimization to do less work. We can use the suggested N=1000 value.
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → jteow
Status: NEW → ASSIGNED
Updated•1 year ago
|
Attachment #9492559 -
Attachment is obsolete: true
| Assignee | ||
Comment 2•1 year ago
|
||
I posted a patch but I think we don't need to do this anymore:
Beginning with SQLite version 3.46.0 (2024-05-23), the recommended way of running ANALYZE is with the PRAGMA optimize command. The PRAGMA optimize will automatically set a reasonable, temporary analysis limit that ensures that the PRAGMA optimize command will finish quickly even on enormous databases. Applications that use the PRAGMA optimize instead of running ANALYZE directly do not need to set an analysis limit.
| Assignee | ||
Comment 3•1 year ago
|
||
I verified with Marco that we're well beyond 3.46. As a result, we don't need to do this.
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•