February 2009February 2009 mk Tue, 03/30/2010 - 20:33
MonetDB Feb2009-SP2 release
Release "Feb2009-SP2" consists of the following updated components
Feb 2009 SP2 bug-fix release
One set of fixes that affects all components is that stack overflow checking has been improved. It is now much less likely that the server crashes when queries need too much stack space. Instead, the server will return an error.
MonetDB/XQuery (tijah): fixes to UTF-8 handling; fixes towards being able to index more than 2**31 words on a 64 bit architecture.
MonetDB5: fixed a crash on exit of the server (this crash was not harmful, just annoying).
MonetDB: avoid integer overflow on very large tables.
mclient/msqldump: fixes to the order in which tables, views, and functions are dumped; also dump triggers; fixed the Ubuntu and Debian installers to include mclient and msqldump.
MonetDB/XQuery: fixed a bug where documents were not available when another document in the collection was loaded.
merovingian/monetdb: fixes to the way the server is stopped.
MonetDB/SQL: fixed a bad concurrency bug where updates were lost or data was incorrectly inserted.
The following bug tracker items were fixed since the Feb2009 SP1 release:
Feb 2009 SP1 bug-fix release
The main fix that was done in this release that affects all parts of the code, but most especially MonetDB/SQL is that we have plugged a large number of memory leaks. MonetDB/SQL can now handle larger databases and more demanding queries. This is especially noticeable on 32 bit Windows systems where the memory management system (the system malloc library) is not as sophisticated as the one in Linux.
mclient/msqldump: Fix to the order in which tables and views are dumped: tables must be dumped before views, since views may reference tables and the view creation will only work if the referenced tables already exist.
mclient: Fixed potential deadlock situation when there is a large input file and several queries early on produce large results.
MonetDB/XQuery: Fixed a bug where a replace operation could corrupt the document (bug #2642003).
The following bug tracker items were fixed since the Feb2009 release:
The following things were fixed or changed in merovingian and monetdb:
The following was changed in the JDBC interface:
Feb 2009 feature release
We now provide Debian (Lenny, i.e. 5.0) and Ubuntu (Intrepid, i.e. 8.10) packages. These packages have only been very lightly tested (the packaged software is tested extensively, though). For now we provide 32 and 64 bit versions for Debian and only a 64 bit version for Ubuntu. This of course in addition to the Fedora packages we already provided.
MonetDB Server 5
The code base has been tested for memory leaks reducing the change of running out of memory too quickly.
The Merovingian has undergone more thorough stress testing making it much more stable.
The optimizer of SQL has been overhauled. Rather than working on the binary plans, it performs optimization on the relational algebra tree before it produces the binary plans.
Like the previous "Nov 2008 SP2" release, the default Algebra-based Pathfinder compiler ("ALG") still does not support a few XQuery features and extensions. A detailed list and temporary work-arounds by resorting to the deprecated "milprint_summer" ("MPS") version of the Pathfinder compiler can be found here.
Time and date related types and the comparison and extraction functions on top of them have been implemented in MonetDB/XQuery.
Mainly for MonetDB developers:
The MonetDB testing tools (Mtest.py & friends) from MonetDB/src/testing/ have been moved into their own "testing" CVS module / MonetDB component.
In case you plan to upgrade your existing CVS-based "MonetDB" installation, please run `make uninstall` in your "MonetDB" build directory, first, i.e., before running `cvs update` in your "MonetDB" source directory.
Once you update your "MonetDB" to the latest CVS development trunk version, and plan to continue (or start) using Mtest.py, you also need to check out the new "testing" CVS module (from SF) and compile and install it any time after you compiled and installed "MonetDB", and before you plan to use Mtest.py.
The new "testing" CVS module depends only on "MonetDB" (and hence requires that to be installed), but on no other MonetDB component (except from the "buildtools", in case your are compiling from CVS sources). No other MonetDB component depends on the new "testing" CVS module other than that you obviously need to have "testing" installed once you want/need to run tests using Mtest.py.
The MonetDB testing tools (Mtest.py & friends) are not part of the actual MonetDB functionality, but mainly for MonetDB development purposes (and hence only distributed in the source tarballs, but not in any (official) binary packages).
To make them less dependent on release cycles (and vice versa), as well as to prepare making them usable without MonetDB --- for now, they actually still depend on MonetDB; see below) --- we decided to separate the MonetDB testing tools from the "MonetDB" CVS module into their own "testing" CVS module.
For the time being (i.e., until further notice), "testing" depends on "MonetDB" --- more precisely only on some utils from MonetDB/src/common/, but not on the GDK kernel from MonetDB/src/gdk/, as
Python modules "subprocess26.py" & "trace.py" have been moved from <PYTHON_LIBDIR>/MonetDB/ to <PYTHON_LIBDIR>/MonetDBtesting/ .
A detailed list of the 65 bug reports that have been closed since the previous "Nov 2008 SP2" release can be found in the MonetDB Bug Tracker at SourceForge: page 1/2, page 2/2.
Known Issues in this Release
|© 1994-2009 CWI||Contact us Legal SourceForge Bugs Tracker TestWeb PermaStore|