- users-list - monetdb.org

Announcement: New Dec2023-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 10 May '24

10 May '24

The MonetDB Foundation is pleased to announce the Dec2023-SP3 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Bug Fixes - [7422](https://github.com/MonetDB/MonetDB/issues/7422): Aggregate functions with variadic arguments - [7472](https://github.com/MonetDB/MonetDB/issues/7472): MonetDB server crashes in `tail_type` - [7473](https://github.com/MonetDB/MonetDB/issues/7473): MonetDB server crashes in `SQLunionfunc` - [7478](https://github.com/MonetDB/MonetDB/issues/7478): MonetDB server crashes in `exp_equal` - [7496](https://github.com/MonetDB/MonetDB/issues/7496): Query on view fails to produce a resultset. Assertion triggered in rel2bin_select. - [7499](https://github.com/MonetDB/MonetDB/issues/7499): create schema + set schema inside a transaction that is rolled back causes the connection to be aborted - [7501](https://github.com/MonetDB/MonetDB/issues/7501): files remain in backup causing problems at restart - [7503](https://github.com/MonetDB/MonetDB/issues/7503): MonetDB server crashes using `WHEN MATCHED THEN UPDATE` - [7504](https://github.com/MonetDB/MonetDB/issues/7504): possible deadlock when a bat is made persistent when it is also getting unloaded - [7506](https://github.com/MonetDB/MonetDB/issues/7506): MonetDB Dec2023-SP2 crashes at `rel_value_exp2` - [7507](https://github.com/MonetDB/MonetDB/issues/7507): BBPextend: ERROR: trying to extend BAT pool beyond the limit (163840000) - [7508](https://github.com/MonetDB/MonetDB/issues/7508): MonetDB Dec2023-SP2 crashes at `exp_ref`

1 0

Announcement: New Dec2023-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 15 Apr '24

15 Apr '24

The MonetDB Foundation is pleased to announce the Dec2023-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB Common - Threads have their own list of free bats. The list was not returned to the system when a thread exited, meaning that the free bats that were in the list would not be reused by any thread. This has been fixed. - Fixed a couple of deadlock situations, one actually observed, one never observed. ### MonetDB5 Server - Fixed interaction between mserver5 and remote mserver5 when only one of the two has 128 bit integer support. ### SQL Frontend - Fixed issue where equal column aliases were created. When those aliases were parsed on the remote side it could give crashes. ### Bug Fixes - [7469](https://github.com/MonetDB/MonetDB/issues/7469): Crash when using `CONTAINS` - [7479](https://github.com/MonetDB/MonetDB/issues/7479): MonetDB server crashes in `exp_ref` - [7490](https://github.com/MonetDB/MonetDB/issues/7490): commonTerms optimizer no longer works - [7495](https://github.com/MonetDB/MonetDB/issues/7495): Crash when simultaneously querying and updating a string column.

1 0

Announcement: New Dec2023-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 18 Mar '24

18 Mar '24

The MonetDB Foundation is pleased to announce the Dec2023-SP1 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### - The copyright for the MonetDB software has been transferred to the newly established MonetDB Foundation, a not-for-profit foundation with the express goal of furthering the MonetDB database system. The license for the software does not change: MonetDB remains fully open source. ### Client Package - Fixed an issue where mclient wouldn't exit if the server it had connected to exited for whatever reason while the client was waiting for a query result. ### MonetDB Common - The internal hash function for floating point types has been changed. It is now no longer based on the bit representation, but on the value, meaning that +0 and -0 (yes, they both exist in floating point) now hash to the same value. - Fixed a regression where bats weren't always cleaned up when they weren't needed anymore. In particular, after a DELETE FROM table query without a WHERE clause (which deletes all rows from the table), the bats for the table get replaced by new ones, and the old, now unused, bats weren't removed from the database. ### Geom Module - We switched over to using the reentrant interface of the geos library. This fixed a number of bugs that would occur sporadically. ### SQL Frontend - performance improvement of 'startswith' and 'endswith' filter functions for join operators - The function json.isvalid(json) incorrectly returned true if the argument was null. It should return null. ### Bug Fixes - [6800](https://github.com/MonetDB/MonetDB/issues/6800): Please add information_schema (ANSI SQL norm) - [7152](https://github.com/MonetDB/MonetDB/issues/7152): Occasional dbfarm corruption upon database restart - [7390](https://github.com/MonetDB/MonetDB/issues/7390): Some MonetDB Server crashes found - [7412](https://github.com/MonetDB/MonetDB/issues/7412): MonetDB server crashes in `vscanf` - [7415](https://github.com/MonetDB/MonetDB/issues/7415): MonetDB server crashes in `HEAP_malloc` - [7416](https://github.com/MonetDB/MonetDB/issues/7416): MonetDB server crashes in `atom_get_int` - [7417](https://github.com/MonetDB/MonetDB/issues/7417): MonetDB server crashes in `trimchars`. - [7418](https://github.com/MonetDB/MonetDB/issues/7418): MonetDB server crashes in `bind_col_exp` - [7420](https://github.com/MonetDB/MonetDB/issues/7420): Performance issue with lower(string) - [7425](https://github.com/MonetDB/MonetDB/issues/7425): The last statement, execution error, is a false positive? - [7426](https://github.com/MonetDB/MonetDB/issues/7426): Unexpected result for INNER JOIN with IS NOT NULL - [7428](https://github.com/MonetDB/MonetDB/issues/7428): Unexpected result when using BETWEEN operator - [7429](https://github.com/MonetDB/MonetDB/issues/7429): Unexpected result when using `CASE WHEN` - [7430](https://github.com/MonetDB/MonetDB/issues/7430): Unexpected result when using `AND` and `IS NOT NULL` - [7431](https://github.com/MonetDB/MonetDB/issues/7431): [bug] Error code found, please confirm - [7432](https://github.com/MonetDB/MonetDB/issues/7432): MonetDB server crashes in `dameraulevenshtein` - [7433](https://github.com/MonetDB/MonetDB/issues/7433): MonetDB server crashes in `exp_atom` - [7434](https://github.com/MonetDB/MonetDB/issues/7434): MonetDB server crashes in `exp_bin` - [7435](https://github.com/MonetDB/MonetDB/issues/7435): MonetDB server crashes in `exp_copy` - [7436](https://github.com/MonetDB/MonetDB/issues/7436): MonetDB server crashes in `exp_ref` - [7437](https://github.com/MonetDB/MonetDB/issues/7437): MonetDB server crashes in `exp_values_set_supertype` - [7438](https://github.com/MonetDB/MonetDB/issues/7438): MonetDB server crashes in `exps_bind_column` - [7439](https://github.com/MonetDB/MonetDB/issues/7439): MonetDB server crashes in `exps_card` - [7440](https://github.com/MonetDB/MonetDB/issues/7440): MonetDB server crashes in `gc_col` - [7441](https://github.com/MonetDB/MonetDB/issues/7441): MonetDB server crashes in `is_column_unique` - [7442](https://github.com/MonetDB/MonetDB/issues/7442): MonetDB server crashes in `mat_join2` - [7443](https://github.com/MonetDB/MonetDB/issues/7443): MonetDB server crashes in `merge_table_prune_and_unionize` - [7444](https://github.com/MonetDB/MonetDB/issues/7444): [bug] the table cannot be created because the reserved word is incorrectly set - [7447](https://github.com/MonetDB/MonetDB/issues/7447): Unexpected result when using `BETWEEN` in `INNER JOIN` - [7448](https://github.com/MonetDB/MonetDB/issues/7448): Unexpected result when using `AND`/`OR` chain - [7450](https://github.com/MonetDB/MonetDB/issues/7450): Unexpected result when `CREATE VIEW` with `WHERE NULL` - [7451](https://github.com/MonetDB/MonetDB/issues/7451): Unexpected result when using `BETWEEN` and `CAST` - [7453](https://github.com/MonetDB/MonetDB/issues/7453): Cannot recover an msqldump - [7455](https://github.com/MonetDB/MonetDB/issues/7455): Unexpected result when using `BETWEEN` with `BOOLEAN` values - [7456](https://github.com/MonetDB/MonetDB/issues/7456): Crash when `INNER JOIN` with `VIEW` - [7457](https://github.com/MonetDB/MonetDB/issues/7457): Unexpected result when using `AND` with `INTEGER` - [7458](https://github.com/MonetDB/MonetDB/issues/7458): Unexpected result when using `SIGN` - [7461](https://github.com/MonetDB/MonetDB/issues/7461): Crash by potentially use of bad escape characters - [7462](https://github.com/MonetDB/MonetDB/issues/7462): Crash when using `BETWEEN AND` - [7465](https://github.com/MonetDB/MonetDB/issues/7465): Unexpected result when using `NULL` in `BETWEEN`

1 0

[MonetDB-users] Proofreading your professional documents
by Richard Hounslow 24 Feb '24

24 Feb '24

Dear Professor/Lecturer Please excuse us for contacting you directly. We are offering an efficient service to help you ensure your academic and professional work is written in perfect English. We will check the grammar and style of your work and return it to you to meet your requirements and deadlines. Proof-Reading-Service.com can provide you with a professional proofreading service at a very reasonable rate. All our proofreaders are highly qualified native English speakers. Many work as leading academics in their fields and all have extensive experience of proofreading to the highest standards. If you are interested in our service, please take a look at our website: www.proof-reading-service.com All you have to do is send us your document as a word attachment with the deadline and we will guarantee delivery of a perfectly written document to give you complete confidence when you submit your work. The fee is worked out on a flat rate (£6.95 per thousand words or 0.695 pence per word), so you know exactly how much the proofreading will cost in advance. Once we have received your document(s) we will confirm the word count, the price and the deadline. If you have not heard from us within 2 hours during normal business hours after you have sent your work please resend it from a different email account or send the file to proofreadings(a)gmail.com. We look forward to hearing from you! Yours faithfully Proof-Reading-Service.com

2 2

Problem to install new fresh database
by Ariel Abadi 30 Dec '23

30 Dec '23

Hi! Im trying to install the latest version of Monetdb, and seems the repo has an error. Can anyone help!? or had an idea how to solve this? [root@tc-mn monetdb]# yum update Loaded plugins: fastestmirror Determining fastest mirrors epel/x86_64/metalink | 32 kB 00:00:00 * epel: mirror.de.leaseweb.net base | 3.6 kB 00:00:00 epel | 4.7 kB 00:00:00 extras | 2.9 kB 00:00:00 monetdb | 1.5 kB 00:00:00 updates | 2.9 kB 00:00:00 (1/5): epel/x86_64/group_gz | 100 kB 00:00:00 (2/5): epel/x86_64/updateinfo | 1.0 MB 00:00:00 (3/5): monetdb/7/x86_64/primary | 120 kB 00:00:00 (4/5): updates/7/x86_64/primary_db | 24 MB 00:00:00 (5/5): epel/x86_64/primary_db | 7.0 MB 00:00:01 One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Parsing primary.xml error: Start tag expected, '<' not found [root@tc-mn monetdb]#

2 1

Announcement: New Dec2023 Feature release of MonetDB suite
by Sjoerd Mullender 28 Dec '23

28 Dec '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Dec2023 feature release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Dec2023 documentation can be found [here](https://www.monetdb.org/documentation-Dec2023/). ## Dec2023 Feature Release (11.49.1) ### - All binary packages are now signed with a new key with key fingerprint DBCE 5625 94D7 1959 7B54 CE85 3F1A D47F 5521 A603. - The ranges of merge partitions are now pushed down into the low level GDK operations, giving them a handle to sometimes execute more efficiently. - Removed the PYTHON MAP external language option, as after a fork the synchronization primitives could be in any state, leading to deadlocks. During the upgrade function definitions will fallback to the normal PYTHON language option. - Implemented direct masking for strimp construction. The strimps datastructure now keeps an array of 65K 64-bit integers that is zero everywhere except at the indexes that correspond to header pairs. The entry for the nth pair in order has the nth bit of the bitstring on. These can be used to quickly construct bitstrings. ### ODBC Driver - Corrected the output value of column CHAR_OCTET_LENGTH of ODBC functions SQLColumns() and SQLProcedureColumns(). ### MonetDB Common - Fixed a (rare) race condition between copying a bat (COLcopy) and updates happening in parallel to that same bat. This may only be an actual problem with string bats, and then only in very particular circumstances. - Introduced options wal_max_dropped, wal_max_file_age and wal_max_file_size that control the write-ahead log file rotation. - Removed function BATroles to set column names on BATs. - Removed the compiled-in limit on the number of threads that can be used. The number of threads are still limited, but the limit is dictated solely by the operating system and the availability of enough memory. - We now prevent accidental upgrades from a database without 128 bit integers to one with 128 bit integers (also known as HUGEINT) from happening. Upgrades will only be done if the server is started with the option --set allow_hge_upgrade=yes. ### Geom Module - Because recent changes to the geom module require the use of geos 3.10, the geom module is no longer available in older versions of Debian and Ubuntu. Specifically, Debian 10 and 11 (buster and bullseye) and Ubuntu 20.04 (Focal Fossa) are affected. There is no automatic upgrade available for databases that were geom enabled to databases that are not, so dump + restore is the only option (if no geom types are actually used). - Implements Rtree index in GDK layer based on librtree. The index is used in the implementation of the filter functions ST_Intersects and ST_Dwithin for geometric points. - Improves shapefile support by replacing functions SHPattach, SHPpartialimport, ahd SHPimport with SHPload. - Introduces functions ST_DistanceGeographic, ST_DwithinGeographic, ST_IntersectsGeographic, ST_CoversGeographic, ST_Collects with geodesic semantics. ST_Transform can be used to convert geodetic into geographic data using libPROJ. ### MonetDB5 Server - Removed MAL functions bat.reuse and bat.reuseMap. - The MAL functions io.import and io.export have been removed. - Removed MAL functions bat.getRole and bat.setColumn since the underlying function BATroles was removed. - Change how json is stored in the database: We now normalize json strings after parsing, removing whitespace and eliminating duplicate keys in objects. - The function json.filter now properly returns json scalars instead of wrapping them in an array. - Removed the MAL tokenizer module. It was never usable from SQL and in this form never would be. ### SQL Frontend - Introduction of table returning function `persist_unlogged(schema string, table string)` that attempts to persist data in disk if "schema"."table" is unlogged table in insert only mode. If persist attempt is successful, the count of the persisted rows is returned, otherwise the count is 0. - Added ISO/IEC 9075-11 SQL/Schemata (SQL:2011) with SQL system views: information_schema.schemata information_schema.tables information_schema.views information_schema.columns information_schema.character_sets information_schema.check_constraints information_schema.table_constraints information_schema.referential_constraints information_schema.routines information_schema.parameters information_schema.sequences For details see https://www.monetdb.org/documentation/user-guide/sql-catalog/information_sc… Most views have been extended (after the standard columns) with MonetDB specific information columns such as schema_id, table_id, column_id, etc. This simplifies filtering and joins with system tables/views in sys schema when needed. Note: MonetDB does NOT support catalog qualifiers in object names, so all the CATALOG columns in these information_schema views will always return NULL. - Added support for generated column syntax: GENERATED BY DEFAULT AS IDENTITY ... This allows the user to override the default generated sequence value during inserts. - Added SQL support for: <result offset clause> and <fetch first clause> in <query expression> ::= [ <with clause> ] <query expression body> [ <order by clause> ] [ <result offset clause> ] [ <fetch first clause> ] [ <sample clause> ] <result offset clause> ::= OFFSET <offset row count> [ {ROW|ROWS} ] <fetch first clause> ::= FETCH {FIRST|NEXT} <fetch first row count> {ROW|ROWS} ONLY ### Bug Fixes - [6933](https://github.com/MonetDB/MonetDB/issues/6933): Add support for scalar function IFNULL(expr1, expr2) - [7044](https://github.com/MonetDB/MonetDB/issues/7044): Improve error message regarding 3-level SQL names - [7261](https://github.com/MonetDB/MonetDB/issues/7261): Misleading error message - [7274](https://github.com/MonetDB/MonetDB/issues/7274): Aggregate function ST_Collect crashes mserver5 - [7376](https://github.com/MonetDB/MonetDB/issues/7376): Concurrency Issue: Second Python UDF Awaits Completion of First UDF - [7391](https://github.com/MonetDB/MonetDB/issues/7391): SQL 2023 : greatest/least functions with unlimited arguments (not only 2) - [7403](https://github.com/MonetDB/MonetDB/issues/7403): Join not recognized between two row_number() columns - [7413](https://github.com/MonetDB/MonetDB/issues/7413): MonetDB server crashes in `BATcalcbetween_intern`

1 0

Announcement: New Jun2023-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 20 Nov '23

20 Nov '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-SP3 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB Common - Fixed a regression where after a while the write-ahead log files weren't being rotated, meaning from some point onwards, the newest file just kept on growing. - When saving the SQL catalog during a low-level commit, we should only save the part of the catalog that corresponds to the part of the write-ahead log that has been processed. What we did was save more, which resulted in the catalog containing references to tables and columns whose disk presence is otherwise only in the write-ahead log. - A bug was fixed where the administration of which bats were in use was interpreted incorrectly during startup, causing problems later. One symptom that has been observed was failure to startup with a message that the catalog tables could not be loaded. ### SQL Frontend - Added a missing interface function sys.timestamp_to_str with a TIMESTAMP (as opposed to TIMESTAMP WITH TIME ZONE) argument. The missing interface caused error messages being produced when the function was called with a TIMESTAMP argument, although it did give the correct result. ### Bug Fixes - [7300](https://github.com/MonetDB/MonetDB/issues/7300): Implement missing standard SQL DATE and TIMESTAMP functions - [7324](https://github.com/MonetDB/MonetDB/issues/7324): string_distance('method',str1, str2) as a generic distance function - [7409](https://github.com/MonetDB/MonetDB/issues/7409): Numpy table returning UDFs with variadic arguments - [7410](https://github.com/MonetDB/MonetDB/issues/7410): SIGSEGV cause database corruption

1 0

Hot Backup no longer working when restoring
by warren.master＠rohatyngroup.com 18 Nov '23

18 Nov '23

i have been using hot backups for a while now , they are fast and have been very reliable for creating new servers and restoreing existig ones today I tried a restore from our daily hot backup that used call sys.hot_snapshot('/home/monetdb/mdb_hotbackup_20231117-1355390956724.tar.lz4'); I use the following to set up a new server monetdbd create /home/dbFarm tar -I lz4 -C /home/dbFarm -axf mdb_hotbackup_20231117-1355390956724.tar.lz4 monetdb start trg log filles with thousands of the below message and the db crashes MSG trg[9744]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(381716) transient Im using lastest build on all machines MonetDB 5 server v11.47.11 (Jun2023-SP2) 2023-11-18 04:58:15 MSG trg[9744]: # Serving database 'trg', using 8 threads 2023-11-18 04:58:15 MSG trg[9744]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers 2023-11-18 04:58:15 MSG trg[9744]: # Found 62.759 GiB available main-memory of which we use 51.149 GiB 2023-11-18 04:58:15 MSG trg[9744]: # Copyright (c) 1993 - July 2008 CWI. 2023-11-18 04:58:15 MSG trg[9744]: # Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved

1 0

Announcement: New Jun2023-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 03 Oct '23

03 Oct '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### - Fixed an installation issue on Debian and Ubuntu introduced in the last build. - Do a lot more error checking, mostly for allocation failures. More is still needed, though. - Improve performance of the ILIKE operator when the pattern contains only ASCII characters. In this case we do not need to treat any characters as UTF-8 and we can use much faster routines that perform byte comparisons. ### MonetDB Common - Fixed a number of data races (race conditions). - Fixed a reference counting problem when a BAT could nog be loaded, e.g. because of resource limitations. - Only check for virtual memory limits when creating or growing bats, not for general memory allocations. There is (still) too much code that doesn't properly handle failing allocations, so we need to avoid those as much as possible. This has mostly an effect if there are virtual memory size restrictions imposed by cgroups (memory.swap.max in cgroups v2, memory.memsw.limit_in_bytes in cgroups v1). - The low-level commit turned out to always commit every persistent bat in the system. There is no need for that, it should only commit bats that were changed. This has now been fixed. - Implemented timeout/exit checks in a bunch more operators. Long(er) running operators occasionally check whether they're taking too long (past a user-specified timeout) or whether the server is exiting. This is now done in more places. ### Bug Fixes - [7094](https://github.com/MonetDB/MonetDB/issues/7094): Drop remote tables in transactions and rollback - [7303](https://github.com/MonetDB/MonetDB/issues/7303): Improve the performance of multi-column filters - [7400](https://github.com/MonetDB/MonetDB/issues/7400): VM max memory is not check correctly for cgroups v2 - [7401](https://github.com/MonetDB/MonetDB/issues/7401): Column aliases used incorrectly in UNION subqueries - [7402](https://github.com/MonetDB/MonetDB/issues/7402): Privileges on merge table not propagated to partition tables

1 0

rdf/sparql support in monetdb
by nguyenm9＠aol.com 08 Aug '23

08 Aug '23

Hey folks, new to monetdb and was wondering what the current support for rdf/sparql would be in the db? I can see mention of rdf support from years past but nothing recent. is this option still available? thanks!

1 0