The MonetDB team at CWI/MonetDB BV is pleased to announce the
Dec2016-SP3 bugfix release of the MonetDB suite of programs.
More information about MonetDB can be found on our website at
<http://www.monetdb.org/>.
For details on this release, please see the release notes at
<http://www.monetdb.org/Downloads/ReleaseNotes>.
As usual, the download location is <http://dev.monetdb.org/downloads/>.
Dec 2016-SP3 bugfix release
MonetDB Common
* Fixed a bug when appending string bats that are fully duplicate
eliminated. It could happend that the to-be-appended bat had an
empty string at an offset and at that same offset in the
to-be-appended-to bat there happened to be a (sequence of) NULL(s).
Then this offset would be used, even though it might nog be the
right offset for the empty string in the to-be-appended-to bat.
This would result in multiple offsets for the empty string,
breaking the promise of being duplicate eliminated.
Bug Fixes
* 6138: Weak duplicate elimination in string heaps > 64KB
* 6183: ResultSet returns double quoted column name if name contains
space characters
* 6216: Assertion raised (sqlsmith)
* 6219: Crash in rel_optimizer (sqlsmith)
* 6227: Monetdb fails on remote tables
* 6228: mclient crashes if real column is multiplied by it itself
* 6229: ANALYZE, unexpected end of input
* 6230: ANALYZE, syntax error
* 6237: semijoin with empty right bat does not return immediately
* 6242: Crash on rel_reduce_groupby_exps (sqlsmith)
* 6243: Static optimization gives wrong result (1 + NULL = -127)
* 6245: Nested query crashes all versions of MonetDB or gives wrong
result starting from Dec2016-SP2
* 6246: update statements: references to a table do not bind to its
alias
* 6247: Type analysis issue (sqlsmith)
* 6248: update statements: the semantic stage does not resolve the
relation in the from clause
* 6250: Assertion failure when querying a Blob column with order by
DESC
* 6251: Crash after adding an ordered index on sys.statistics column
and querying sys.statistics
* 6253: FITS Data Vaults does not work when using user/pw and other
than sys schema name
I want to know the file system or how the data is stored in MonetDB.
I know data for each column is stored in separate files. But I want to know
what those .*thead *and .*tail *files inside BAT folder of the monetDB data
folder mean and how data is stored in those files.
Please help me ASAP.
Thank you.
I want to know the file layout of columnar data storage in MonetDB. I know
each column is stored in separate files. Actually I want to know the exact
layout as in a block diagram to get a clear picture of the storage layout.
Helps are appreciated.
Regards,
Senthil Vidhiyakar. S
The MonetDB team at CWI/MonetDB BV is pleased to announce the
Dec2016-SP2 bugfix release of the MonetDB suite of programs.
More information about MonetDB can be found on our website at
<http://www.monetdb.org/>.
For details on this release, please see the release notes at
<http://www.monetdb.org/Downloads/ReleaseNotes>.
As usual, the download location is <http://dev.monetdb.org/downloads/>.
Dec 2016-SP2 bugfix release
Bug Fixes
* 4034: argnames array in rapi.c has fixed length (that was too
short)
* 6080: mserver5: rel_bin.c:2391: rel2bin_project: Assertion `0'
failed.
* 6081: Segmentation fault (core dumped)
* 6082: group.subgroup is undefined if group by is used on an
expression involving only constants
* 6111: Maximum number of digits for hge decimal is listed as 39 in
sys.types. Should be 38 as DECIMAL(39) is not supported.
* 6112: Crash upgrading Jul2015->Jun2016
* 6130: Query rewriter crashes on a NULL pointer when having a
correlated subquery
* 6133: A crash occurs when preparing an INSERT on joined tables
during the query semantic phase
* 6141: Getting an error message regarding a non-GROUP-BY column
rather than an unknown identifier
* 6177: Server crashes
* 6186: Null casting causes no results (silent server crash?)
* 6189: Removing a NOT NULL constraint from a PKey column should NOT
be allowed
* 6190: CASE query crashes database
* 6191: MT_msync failed with "Cannot allocate memory"
* 6192: Numeric column stores wrong values after adding large numbers
* 6193: converting to a smaller precision (fewer or no decimals after
decimal point) should round/truncate consistently
* 6194: splitpart returns truncated last part if it contains non
ascii caracters
* 6195: Cast from huge decimal type to smaller returns wrong results
* 6196: Database crashes after generate_series query
* 6198: COALESCE could be more optimized
* 6201: MonetDB completely giving up on certain queries - no error
and no result
* 6202: querying a table with an ordered index on string/varchar
column crashes server and makes server unrestartable!
* 6203: copy into: Failed to import table Leftover data 'False'
* 6205: Integer addition overflow
* 6206: casting strings with more than one trailing zero ('0') to
decimal goes wrong
* 6209: Aggregation over complex OR expressions produce wrong results
* 6210: Upgrading a database from Jun2015 or older crashes the server
* 6213: SQLsmith causes server to crash
* 6217: Segfault in rel_optimizer (sqlsmith)
* 6218: grouped quantiles with all null group causes following groups
to return null
* 6224: mal_parser: cannot refer to types containing an underscore
Databases created with the default branch before changeset f054b7310be7
(Mar 1, 2017) are *not* compatible with the default branch from that
changeset on.
The changeset is a merge of fixes from the Dec2016 branch, and one of
the fixes introduced a version number update of the BBP.dir file. This
update was incompatible with an earlier update of the version number
that was exclusive to the default branch.
There are two possible solutions:
- dump your database(s) with a version from before the chnangeset, and
restore with a version after.
- manually update the version number in the BBP.dir file and ignore the
possibility that the bug that was fixed may be in your database.
Manually fixing the BBP.dir file involves incrementing the number on the
first line of the file from 25118 to 25119. Needless to say, this is
not recommended.
Remember, there are no guarantees when using the default branch. In
fact, there are also no guarantees when using any other branch. The
only thing we promise is that we will do our best to make sure the
actual releases work and can be upgraded properly.
--
Sjoerd Mullender
Tomorrow, March 2, we will be upgrading the hardware for the system on
which all monetdb.org infrastructure runs. Expect some downtime.
--
Sjoerd Mullender