Force a checkpoint after schema creation or upgrade

RESOLVED FIXED in mozilla2.0b9

Status

()

RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: mak, Assigned: mak)

Tracking

unspecified
mozilla2.0b9
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fixed-in-places])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

8 years ago
Just for added safety.
To do this I'll have to cleanup the migration code a bit so that:
1. I remove an empty useless transaction for normal startups
2. I have a single point to put the forcing

This means I want to remove all old migration code that comes from Firefox 3 alphas (finally!), or at least, the most part.
(Assignee)

Comment 1

8 years ago
Created attachment 494920 [details] [diff] [review]
patch v1.0
Attachment #494920 - Flags: review?(sdwilsh)
Comment on attachment 494920 [details] [diff] [review]
patch v1.0

>+++ b/toolkit/components/places/src/nsNavHistory.cpp
>   // Ensure that temp tables are held in memory, not on disk.  We use temp
>   // tables mainly for fsync and I/O reduction.
>-  rv = mDBConn->ExecuteSimpleSQL(NS_LITERAL_CSTRING(
>+  nsresult rv = mDBConn->ExecuteSimpleSQL(NS_LITERAL_CSTRING(
The comment here is clearly outdated!

>+  // Grow places in 10MB increments
>+  mDBConn->SetGrowthIncrement(10 * 1024 * 1024, EmptyCString());
I should have caught this before.  Can we add a BYTES_PER_MEGABYTE constant somewhere?
nit: (void)

r=sdwilsh
Attachment #494920 - Flags: review?(sdwilsh)
Attachment #494920 - Flags: review+
Attachment #494920 - Flags: approval2.0+
(Assignee)

Comment 3

8 years ago
Created attachment 494980 [details] [diff] [review]
patch v1.1
Attachment #494920 - Attachment is obsolete: true
(Assignee)

Comment 4

8 years ago
http://hg.mozilla.org/projects/places/rev/0b18344e65ca
Whiteboard: [fixed-in-places]
(Assignee)

Comment 5

8 years ago
http://hg.mozilla.org/mozilla-central/rev/0b18344e65ca
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b9
You need to log in before you can comment on or make changes to this bug.