upgrading mysql repositories from format 1.14 to format 2a
Hello. I am slowly preparing for the upgrade of our central internal host's shared repository of MySQL branches, from repository format 1.14 to 2a. I would like to use this bug report as the place of resolution of issues faced as I progress (I have already read the 2a upgrade guide).
I just upgraded my local shared repo from 1.14 to 2a with "bzr upgrade --2a" (it took ~8 hours); this local repo is a good approximation of our central repo.
My observations:
size of .bzr 850 MB 300 MB good
(after "bzr pack", and excluding "obsolete_packs")
time for "bzr log -n0" 23 secs 14 secs good
time for "bzr annotate big_file" 12 secs 24 secs bad
I'm using bzr.dev pulled a few days ago.
I think "annotate" is a serious problem, could you please fix the slowdown observed in 2a? My colleagues already complain of the slowness of annotate since we migrated to bzr, I'd rather not make it worse.
If you want to reproduce this: big_file above is sql/mysqld.cc from this branch:
https:/
Then I have general questions. When I'm confident that the new format is good for us, I'll do the migration in steps:
- at T1: ask the 100+ colleagues to install bzr 2.1 (then most will, and a few won't, that happens)
- at T2: upgrade the central shared repo to 2a
- at T3: ask colleagues to upgrade their shared repo (either with "bzr upgrade --2a", or by "scp"-ing a copy of the central repo, to be determined later).
What I wonder is:
1) between T2 and T3, will a colleague with a 1.9/1.14 local repo be able to push to the 2a central repo? to pull from the 2a central repo? to "bzr branch" a branch from the 2a central repo?
2) after T2, will Launchpad mirroring (visible in https:/
3) after T2, will a colleague using an old bzr (like bzr 1.15) be able to accidentally break something by pushing/pulling to/from the 2a central repo, or will he get a nice error message?
Thanks for your help.
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Bazaar Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
This question was originally filed as bug #519822.
Can you help with this problem?
Provide an answer of your own, or ask GuilhemBichot for more information if necessary.