[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] 0.17 "release candidate", last call for bugs...

From: Christof Petig
Subject: Re: [Monotone-devel] 0.17 "release candidate", last call for bugs...
Date: Tue, 08 Mar 2005 18:03:02 +0100
User-agent: Mozilla Thunderbird 1.0 (X11/20050117)

Nathaniel Smith schrieb:
On Tue, Mar 08, 2005 at 11:09:09AM +0100, Christof Petig wrote:

Tonight (3 hours before you wote this announcement) I finished one of
the things on my todo list for 0.17: Replace the sqlite3 CVS snapshot by
a known release. So in the sqlite3 branch at
61d2cc2412b253f00a337077007c26abcecbec84 you will find the current
stable sqlite3 release (3.1.3).

Whether or not we should include either the tested December's CVS
snapshot or this release in 0.17 I'm uncertain. It should pass the tests
(currently compiling) and besides some performance problems in the
cvssync branch I don't know of any problems with my last import.

Well, I guess my question is, would you expect upgrading to this
latest sqlite release to make any difference whatsoever? :-) Does it
fix bugs, go faster, any ideas?

No, I do not expect any visible differences, neither do I know of any
issues of either revision. But it feels better to ship a release with a
released database (3.1.3) than with a _random_ cvs snapshot (3.0.9x).

Since we don't use any of 3.0's (BLOBs, query parameter) neither 3.1's
features (autovacuum, cursors), I do not expect the old snapshot to show
bugs. But in the likely case that the planner heuristic has improved
over the last three months a tiny speedup is possible.


PS: The new database passed all tests.
PPS: You can find my merge at 06d1d4e8b99269c8adca3cc082cedaef5a102cc4
(missing a ChangeLog <blush>)

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]