Re: [Tracker] Releasing Tracker 0.6.90
- From: Martyn Russell <martyn imendio com>
- To: jamie mccrack gmail com
- Cc: Tracker mailing list <tracker-list gnome org>
- Subject: Re: [Tracker] Releasing Tracker 0.6.90
- Date: Mon, 09 Feb 2009 15:33:25 +0000
Jamie McCracken wrote:
On Mon, 2009-02-09 at 10:49 +0000, Martyn Russell wrote:
Martyn Russell wrote:
Jamie McCracken wrote:
[snip]
Attila (working at Nokia) has experienced some slowdowns this morning
with some initial testing - this could be the new extractor logging of
course and I plan on minimising that, but it could also be this new
change. He will be investigating it. For now can we revert this?
Attila just confirmed the revision which caused the slowdown, and it is
indeed this change. Even Carlos just mentioned it to me. I have as yet
to try it. But it sounds like this needs reverting.
ok you can revert - there is a chance of corruption of course because
default is FULL if power is cut whilst updating db
Yea, we did have an extensive discussion on this this morning between
Mikael, Carlos, Jurg and I. There are several points here worth mentioning:
1. We pause ALL indexing on low battery (which is a preventative of
course but not full proof).
2. No one recently (last 6 months at least) has reported any kind of
activity.
3. The website says this is really unlikely:
"There is a very small (though non-zero) chance that a power failure at
just the wrong time could corrupt the database in NORMAL mode. But in
practice, you are more likely to suffer a catastrophic disk failure or
some other unrecoverable hardware fault"
I would say the speed impairment is not worth the highly unlikely
database corruption we could face. If we find this is happening more
than once or twice for people we can of course change this.
I will go ahead with the release then :)
Thanks,
--
Regards,
Martyn
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]