- users-list - monetdb.org

gcc optimization level?
by Roberto Cornacchia 14 May '21

14 May '21

I was wondering, -DCMAKE_BUILD_TYPE=Release (or RelWithDebInfo) doesn't seem to enable -O2 on gcc. Is there a good reason for it or was it just forgotten?

2 2

Announcement: New Oct2020-SP5 Bugfix release of MonetDB suite
by Sjoerd Mullender 10 May '21

10 May '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP5 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/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct2020-SP5 Bugfix Release (11.39.17) Windows Packaging * Added the monetdbe library to the Windows installer. MonetDB Common * A bug that would very occasionally produce an error "strPut: incorrectly encoded UTF-8", even when no incorrectly coded characters are used at all, has been fixed. It was the result of a rare combination of strings having been added to the column that caused essentially an off-by-one type of error to occur. SQL Frontend * A bug where a sequence of TRUNCATE TABLE and COPY INTO the just truncated table would result in success being reported to both queries, but the table still being empty afterwards, has been fixed. Merovingian * When stopping monetdbd using the `monetdbd stop' command, this command now waits for 5 seconds longer than the exittimeout value before it kills the monetdbd daemon instead of only 30 seconds total (or until that daemon stops earlier). This gives the daemon enough time to terminate the mserver5 processes that it is managing. If exittimeout is negative, the daemon and the monetdbd process initiating the stop wait indefinitely until the mserver5 processes have stopped. Bug Fixes * 3336: DB files not removed if all rows are deleted, even after restart * 7104: Monetdbe NTILE function does not produce correct ordering * 7108: Monetdb crashes on query execution * 7109: MERGE Statement incorrectly reports that input relation matches multiple rows * 7110: Monetdb Query parsing consistency issues in the latest release (Remote Table)

1 0

Announcement: New Oct2020-SP4 Bugfix release of MonetDB suite
by Sjoerd Mullender 12 Apr '21

12 Apr '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP4 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/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct2020-SP4 Bugfix Release (11.39.15) ODBC Driver * When connecting using a DSN (Data Source Name), information about the data source is retrieved from the ODBC.INI file. Now we also get the location of the LOGFILE from this file. The logfile can be used to log all calls to the MonetDB ODBC driver to a file which can be used for debugging. * The ODBC driver now only passes on information about HUGEINT columns as HUGEINT when the application has indicated interest by querying about the SQL_HUGEINT extension type using the SQLGetTypeInfo function or by specifying the type in a call to SQLSetDescField. Otherwise the driver silently translates the HUGEINT type to BIGINT. This means that most application will see BIGINT columns when the server produced a HUGEINT column and only give an error if the value in the HUGEINT column didn't fit into a BIGINT. Bug Fixes * 6786: function json.isvalid(js json) is not useful, could be removed * 7016: Database crashes when use similarity function on a table with more than 200k records * 7037: Clearer err msg for ALTER USER with insufficient privileges * 7042: AddressSanitizer:DEADLYSIGNAL in Oct2020/gdk/gdk_tracer.c:494 * 7050: file descriptor leak when forward=redirect * 7057: ODBC driver installer on Windows is missing some DLLs * 7058: MonetDBe: COPY INTO csv file does not produce any output * 7059: MonetDBe: 'reverse' C UDF crashes * 7061: Have bulk load support combined gzip files * 7064: Temporary hashes created in hash and unique logic should try to use transient data farm first * 7066: percent_rank function with wrong results * 7070: double free error when running MonetDBe Example * 7076: mserver5 ignores memory.low from cgroups v2 * 7077: Oct2020: new default privileges not effectively communicated * 7083: MonetDBe C++ Compiling Error * 7085: Mitosis and filter functions * 7087: SIGSEGV caused by error in subquery's function being ignored by top-level query * 7089: Data consistency problem of query results in the latest release of Monetdb (Remote Table)

1 0

Need info about --in-memory option
by Lakshmipathy Jois 09 Apr '21

09 Apr '21

Hi All, I am new to MonetDB and this is my first email to this group. I came across the option --in-memory for mserver5. I understood that if this option is set, then MonetDB operates out of memory and data is not persisted. I wanted to know more details about the working of MonetDB if this option is set: 1. If this option is set, what is the maximum data size that MonetDB can operate with? 2. If this option is set, will MonetDB use mmap only for reading purposes or not use mmap at all? Any other information is really welcome. Thanks in advance. Lakshmi Pathy S N

2 1

Problems installing October2020 version
by Ioannis Foufoulas 31 Mar '21

31 Mar '21

Hi, It seems that releases from October2020 have a different structure (and size) and instructions here https://www.monetdb.org/Documentation/ServerAdministration/Installation/Ins… <https://www.monetdb.org/Documentation/ServerAdministration/Installation/Ins…> are not working as expected. Is there any documentation on how to install the latest versions? Best, Yannis

2 1

Bug with remote tables in transactions
by Ioannis Foufoulas 30 Mar '21

30 Mar '21

Hi, We encounter a bug with remote tables as part of transactions: sql>CREATE REMOTE TABLE rmt_tbl (id int, name varchar(20)) ON ‘mapi:monetdb://remote.host.url:50000/dbname/scm1/l_tbl <monetdb://remote.host.url:50000/dbname/scm1/l_tbl>’; operation successful sql>BEGIN TRANSACTION; auto commit mode: off sql>DROP TABLE rmt_tbl; operation successful sql>ROLLBACK; auto commit mode: on sql>DROP TABLE if exists rmt_tbl; no such table: ‘sys.rmt_tbl’ sql> It seems that after rollback the table exists in the catalogue but it does not actually exists so that drop table fails even if we have ‘if exists’ This happens only with remote tables. Best, Yannis

2 1

RSS memory
by Roberto Cornacchia 11 Mar '21

11 Mar '21

Hi, I would appreciate some help interpreting the following memory-related issues. I've got a mserver5 instance running with cgroups v1 constraints - memory.limit_in_bytes = 17179869184 (16g) - memory.memsw.limit_in_bytes = 9223372036854771712 gdk_mem_maxsize is initialised as 0.815 * 17179869184 = 14001593384. So I get: sql>select * from env() where name in ('gdk_mem_maxsize', 'gdk_vm_maxsize'); +-----------------+---------------+ | name | value | +=================+===============+ | gdk_vm_maxsize | 4398046511104 | | gdk_mem_maxsize | 14001593384 | +-----------------+---------------+ That looks good. To my surprise, this instance gets frequently OOM-killed for reaching 16g of RSS (no swap used): memory: usage 16777216kB, limit 16777216kB, failcnt 244063804 memory+swap: usage 16777964kB, limit 9007199254740988kB, failcnt 0 kmem: usage 0kB, limit 9007199254740988kB, failcnt 0 Memory cgroup out of memory: Kill process 975803 (mserver5) score 1003 or sacrifice child Now, there are two different aspects: giving a process a memory cap and making the process respect that cap without getting killed. - if the process allocates more than defined with cgroups, then it gets killed. That is fine, it doesn't surprise me - the question is: why did monetDB surpass the 16g limit? Even more surprising, given that it "prudently" initialises itself at 80% of the available memory. Perhaps I was under the wrong assumption that MonetDB would never allocate more than gdk_mem_maxsize, but now I seem to realise that it simply uses this value to optimise its memory management (e.g. to decide how early to mmap). So, am I correct that setting gdk_mem_maxsize (indirectly via gcroups or directly via memmaxsize parameter) does not guarantee rss memory will stay underthat value? If that is true, I am back at square 1 in my quest for how to cap rss usage (without getting the process killed). Thanks for your help. Roberto

2 6

Structure of error messages and comprehensive list of errors
by imad hajj chahine 10 Mar '21

10 Mar '21

Hi, I am trying to understand the error messages and codes reported by MonetDB, to be able to better handle error reporting, monitoring and logging. What I understand so far about the structure of an error message, it starts with error code placed between '!' and after the error message, for ex: !42000! SELECT: identifier 'xyz' unknown. and sometimes a part of the query is included. I found the list of ODBCError in "clients/odbc/driver/ODBCError.c" file, but I am not sure if this is the complete list and if it's aligned with the error codes reported by MonetDB. Is there any standard for the message error structure and where can I find the list of errors with their descriptions? Thanks.

1 0

MonetDB development feedback and contribution
by Jamie Wang 19 Feb '21

19 Feb '21

Hi, I work for Opentext corporation and one of my dev team is heavily using MonetDB and would like to explore if there's common interest on certain functionalities that we have developed. We would be interested to exchange information, solicit feedback and the possibility to contribute to the community. Can someone please provide a few pointers as to how to proceed? Thanks in advance for your time and assistance. Jamie

1 0

Announcement: New Oct2020-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 19 Feb '21

19 Feb '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-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/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct2020-SP3 Bugfix Release (11.39.13) Bug Fixes * 7049: Implement DISTINCT for GROUP_CONCAT

1 0