# 
# 
# patch "ChangeLog"
#  from [5562dfcc729751c89c067fea6a850d151af192e6]
#    to [310bf18b17f414c0451e073f504026d8168df244]
# 
# patch "database.cc"
#  from [13f6d195058997c85c3cc8485b31947bab8357c0]
#    to [2d10672483bebf2fffbd7c1ac0edf6ddbe322f98]
# 
# patch "schema_migration.cc"
#  from [b3e500ba1fc90f6e50af697899afda44a7adbe9c]
#    to [68292293578bfaa6f996002650d4ffe13a29d216]
# 
============================================================
--- ChangeLog	5562dfcc729751c89c067fea6a850d151af192e6
+++ ChangeLog	310bf18b17f414c0451e073f504026d8168df244
@@ -1,5 +1,11 @@ 2006-12-18  Matthew Gregan  <address@hidden
 2006-12-18  Matthew Gregan  <address@hidden>
 
+	* database.cc (database::load),
+	schema_migration.cc (migrator::migrate):
+	PerformanceWork/SQLiteAnalyzeDiscussion in the wiki makes a strong
+	argument that ANALYZE provides no benefit for our use profile.
+	Remove ANALYZE calls from the post-load and post-migrate code.
+
 	* win32/monotone.iss: Don't ask the user a bunch of questions
 	about repositories, keys, branches, and workspaces at a point
 	where they might not know the answers.  Based on feedback from new
============================================================
--- database.cc	13f6d195058997c85c3cc8485b31947bab8357c0
+++ database.cc	2d10672483bebf2fffbd7c1ac0edf6ddbe322f98
@@ -514,7 +514,6 @@ database::load(istream & in)
     }
 
   assert_sqlite3_ok(__sql);
-  execute(query("ANALYZE"));
 }
 
 
============================================================
--- schema_migration.cc	b3e500ba1fc90f6e50af697899afda44a7adbe9c
+++ schema_migration.cc	68292293578bfaa6f996002650d4ffe13a29d216
@@ -319,9 +319,6 @@ migrator
         E(logged_sqlite3_exec(sql, "VACUUM", NULL, NULL, NULL) == SQLITE_OK,
           F("error vacuuming after migration"));
 
-        E(logged_sqlite3_exec(sql, "ANALYZE", NULL, NULL, NULL) == SQLITE_OK,
-          F("error running analyze after migration"));
-
         switch (regime)
           {
           case upgrade_changesetify: