issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes in `HEAP_malloc`.
**To Reproduce**
```sql
CREATE TABLE t1 AS SELECT t1.value AS id, CAST( sys.group_concat( CASE WHEN id.value IS NOT NULL THEN 'DB' ELSE '' END , '') AS BLOB) AS name FROM sys.generate_series(0, 1000) AS t1 LEFT JOIN sys.generate_series(0, 1000) AS id ON id.value < t1.value GROUP BY id ORDER BY id ;
insert into t1 (select * from t1) ;
insert into t1 (select * from t1) ;
insert into t1 (select * from t1) ;
insert into t1 (select * from t1) ;
DELETE FROM t1 WHERE id=1;
select nth_value(aa, 1) over (partition by bb) from analytics ;
insert into t1 (select * from t1) ;
insert into t1 (select * from t1) ;
```
**Backtrace of the Crash**
```c
#0 0x7ffb416f2ce7 (HEAP_malloc+0xa7)
#1 0x7ffb4170319a (BLOBput+0x7a)
#2 0x7ffb4165effe (BATappend_or_update+0x15ee)
#3 0x7ffb416656fa (BATupdate+0x4a)
#4 0x7ffb405956c1 (append_col_execute+0x8b1)
#5 0x7ffb4058197b (append_col+0xcb)
#6 0x7ffb403e02b0 (mvc_append_wrap+0x660)
#7 0x7ffb4095829f (runMALsequence+0xf0f)
#8 0x7ffb4095d933 (DFLOWworker+0x4a3)
#9 0x7ffb417df8a7 (thread_starter+0xc7)
#10 0x7ffb402fa609 (start_thread+0xd9)
#11 0x7ffb4021d133 (clone+0x43)
```
**Software versions**
- MonetDB version number: v11.47.11 (Jun2023-SP2)
- OS and version: Ubuntu 20.04
- From docker image monetdb/monetdb:Jun2023-SP2
An example of steps to reproduce in docker container (**write the poc into /tmp/test.sql first**):
```bash
docker container rm monetdb_test -f # remove the old one
docker run -e MDB_DB_ADMIN_PASS=monetdb --name monetdb_test -itd monetdb/monetdb:Jun2023-SP2
# start monetdb in docker
docker exec monetdb_test bash -c 'echo -n -e "user=monetdb\npassword=monetdb\n" > /root/.monetdb'
# set username and password
sleep 10 # wait the server start
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR"
# check the existence of mserver5 process
cat /tmp/test.sql | docker exec -i monetdb_test mclient monetdb # run test case
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR" || { echo "[CRASH] Mserver5 process does NOT exist."; exit 1; }
# check the existence of mserver5 process
echo "[INFO] Server normal."
```
It can also be reproduced on MonetDB Dec2023_root, self-compiled by `CC=clang-12 CXX=clang++-12 cmake /root/monetdb -DCMAKE_BUILD_TYPE=RelWithDebInfo`.
**Issue labeling**
bug | MonetDB server crashes in `HEAP_malloc` | https://api.github.com/repos/MonetDB/MonetDB/issues/7415/comments | 2 | 2023-11-15T16:37:08Z | 2024-06-27T13:18:50Z | https://github.com/MonetDB/MonetDB/issues/7415 | 1,995,138,527 | 7,415 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes in `GDKanalytical_correlation`.
**To Reproduce**
```sql
CREATE TABLE v0 ( v1 , v2 ) as ( select i , cast ( i as string ) from generate_series ( 1 , 1000 ) as t ( i ) );
DELETE FROM v0 WHERE NULLIF ( v2 , v2 = ( SELECT corr ( v1 , v1 ) OVER ( ROWS 2 PRECEDING ) ) ) ;
```
**Backtrace of the Crash**
```c
#0 0x7f413b189c02 (GDKanalytical_correlation+0xdbb2)
#1 0x7f4139c11497 (do_covariance_and_correlation+0xd67)
#2 0x7f4139c235db (SQLcorr+0x5b)
#3 0x7f413a07429f (runMALsequence+0xf0f)
#4 0x7f413a079933 (DFLOWworker+0x4a3)
#5 0x7f413aefb8a7 (thread_starter+0xc7)
#6 0x7f4139a16609 (start_thread+0xd9)
#7 0x7f4139939133 (clone+0x43)
```
**Software versions**
- MonetDB version number: v11.47.11 (Jun2023-SP2)
- OS and version: Ubuntu 20.04
- From docker image monetdb/monetdb:Jun2023-SP2
An example of steps to reproduce in docker container (**write the poc into /tmp/test.sql first**):
```bash
docker container rm monetdb_test -f # remove the old one
docker run -e MDB_DB_ADMIN_PASS=monetdb --name monetdb_test -itd monetdb/monetdb:Jun2023-SP2
# start monetdb in docker
docker exec monetdb_test bash -c 'echo -n -e "user=monetdb\npassword=monetdb\n" > /root/.monetdb'
# set username and password
sleep 10 # wait the server start
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR"
# check the existence of mserver5 process
cat /tmp/test.sql | docker exec -i monetdb_test mclient monetdb # run test case
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR" || { echo "[CRASH] Mserver5 process does NOT exist."; exit 1; }
# check the existence of mserver5 process
echo "[INFO] Server normal."
```
It can also be reproduced on MonetDB Dec2023_root, self-compiled by `CC=clang-12 CXX=clang++-12 cmake /root/monetdb -DCMAKE_BUILD_TYPE=RelWithDebInfo`.
**Issue labeling**
bug | MonetDB server crashes in `GDKanalytical_correlation` | https://api.github.com/repos/MonetDB/MonetDB/issues/7414/comments | 1 | 2023-11-15T16:35:47Z | 2024-06-27T13:18:49Z | https://github.com/MonetDB/MonetDB/issues/7414 | 1,995,136,232 | 7,414 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes in `BATcalcbetween_intern`.
**To Reproduce**
```sql
CREATE TABLE v0 ( v1 oid ) ;
INSERT INTO v0 ( v1 ) VALUES ( NULL ) , ( 3 ) , ( 46 ) , ( 10 ) , ( 1 ) ;
DELETE FROM v0 WHERE v1 <= ( SELECT 2 AS zero WHERE ( v1 BETWEEN 1 AND ( SELECT MAX ( v1 ) FROM v0 name ) ) >= v1 ) ;
```
**Backtrace of the Crash**
```c
#0 0x7f7f51281dbc (BATcalcbetween_intern+0x14b1c)
#1 0x7f7f5128ea68 (BATcalcbetweencstbat+0x668)
#2 0x7f7f50d97df8 (CMDbatBETWEEN+0x788)
#3 0x7f7f50c0f29f (runMALsequence+0xf0f)
#4 0x7f7f50c14933 (DFLOWworker+0x4a3)
#5 0x7f7f51a968a7 (thread_starter+0xc7)
#6 0x7f7f505b1609 (start_thread+0xd9)
#7 0x7f7f504d4133 (clone+0x43)
```
**Software versions**
- MonetDB version number: v11.47.11 (Jun2023-SP2)
- OS and version: Ubuntu 20.04
- From docker image monetdb/monetdb:Jun2023-SP2
An example of steps to reproduce in docker container (**write the poc into /tmp/test.sql first**):
```bash
docker container rm monetdb_test -f # remove the old one
docker run -e MDB_DB_ADMIN_PASS=monetdb --name monetdb_test -itd monetdb/monetdb:Jun2023-SP2
# start monetdb in docker
docker exec monetdb_test bash -c 'echo -n -e "user=monetdb\npassword=monetdb\n" > /root/.monetdb'
# set username and password
sleep 10 # wait the server start
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR"
# check the existence of mserver5 process
cat /tmp/test.sql | docker exec -i monetdb_test mclient monetdb # run test case
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR" || { echo "[CRASH] Mserver5 process does NOT exist."; exit 1; }
# check the existence of mserver5 process
echo "[INFO] Server normal."
```
It can also be reproduced on MonetDB Dec2023_root, self-compiled by `CC=clang-12 CXX=clang++-12 cmake /root/monetdb -DCMAKE_BUILD_TYPE=RelWithDebInfo`.
**Issue labeling**
bug | MonetDB server crashes in `BATcalcbetween_intern` | https://api.github.com/repos/MonetDB/MonetDB/issues/7413/comments | 1 | 2023-11-15T16:34:18Z | 2024-06-27T13:18:48Z | https://github.com/MonetDB/MonetDB/issues/7413 | 1,995,133,934 | 7,413 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes in `vscanf`.
**To Reproduce**
```sql
SELECT CAST ( '::192.168.1.226' AS INTERVAL HOUR ( 3 ) TO SECOND );
```
**Backtrace of the Crash**
```c
#0 0x7f79b2a8af81 (vscanf+0x131)
#1 0x7f79b2a60df6 (__snprintf+0x96)
#2 0x7f79b2eb416d (parse_interval_+0x54d)
#3 0x7f79b2eb4218 (parse_interval_+0x5f8)
#4 0x7f79b2eb3a22 (parse_interval+0x612)
#5 0x7f79b2eb44d5 (interval_from_str+0x245)
#6 0x7f79b2dd8643 (second_interval_str+0x273)
#7 0x7f79b325929f (runMALsequence+0xf0f)
#8 0x7f79b325c2af (reenterMAL+0x5f)
#9 0x7f79b3489861 (OPTevaluateImplementation+0x671)
#10 0x7f79b34b97a2 (OPTwrapper+0x2c2)
#11 0x7f79b3281a7f (optimizeMALBlock+0x1cf)
#12 0x7f79b2d6bb63 (SQLoptimizeQuery+0x353)
#13 0x7f79b2d0563d (SQLparser+0x10dd)
#14 0x7f79b2d03cbc (SQLengine_+0xa5c)
#15 0x7f79b2d014fe (SQLengine+0x3e)
#16 0x7f79b327f2cf (runScenario+0x6f)
#17 0x7f79b32804de (MSscheduleClient+0xb6e)
#18 0x7f79b33b7182 (doChallenge+0x132)
#19 0x7f79b40e08a7 (thread_starter+0xc7)
#20 0x7f79b2bfb609 (start_thread+0xd9)
#21 0x7f79b2b1e133 (clone+0x43)
```
**Software versions**
- MonetDB version number: v11.47.11 (Jun2023-SP2)
- OS and version: Ubuntu 20.04
- From docker image monetdb/monetdb:Jun2023-SP2
An example of steps to reproduce in docker container (**write the poc into /tmp/test.sql first**):
```bash
docker container rm monetdb_test -f # remove the old one
docker run -e MDB_DB_ADMIN_PASS=monetdb --name monetdb_test -itd monetdb/monetdb:Jun2023-SP2
# start monetdb in docker
docker exec monetdb_test bash -c 'echo -n -e "user=monetdb\npassword=monetdb\n" > /root/.monetdb'
# set username and password
sleep 10 # wait the server start
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR"
# check the existence of mserver5 process
cat /tmp/test.sql | docker exec -i monetdb_test mclient monetdb # run test case
docker exec monetdb_test bash -c "grep '/usr/bin/[m]server5' /proc/*/cmdline -lR" || { echo "[CRASH] Mserver5 process does NOT exist."; exit 1; }
# check the existence of mserver5 process
echo "[INFO] Server normal."
```
It can also be reproduced on MonetDB Dec2023_root, self-compiled by `CC=clang-12 CXX=clang++-12 cmake /root/monetdb -DCMAKE_BUILD_TYPE=RelWithDebInfo`.
**Issue labeling**
bug | MonetDB server crashes in `vscanf` | https://api.github.com/repos/MonetDB/MonetDB/issues/7412/comments | 3 | 2023-11-15T16:33:15Z | 2024-06-27T13:18:47Z | https://github.com/MonetDB/MonetDB/issues/7412 | 1,995,132,142 | 7,412 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB fails to build Debian packages because build dependency `openssl-dev` does not exist. Perhaps you mean `libssl-dev`.
**To Reproduce**
git clone --depth 1 https://github.com/MonetDB/MonetDB.git
cd MonetDB
apt-get build-dep .
**Software versions**
- MonetDB current master (d63db2e37d1)
- Debian Bookworm (Docker image)
| FTBFS on Debian: no openssl-dev | https://api.github.com/repos/MonetDB/MonetDB/issues/7411/comments | 1 | 2023-11-02T14:24:33Z | 2023-11-16T17:03:29Z | https://github.com/MonetDB/MonetDB/issues/7411 | 1,974,375,941 | 7,411 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
It happens a bit too often that a SIGSEGV crash then makes the database unusable.
Unfortunately this is not simple to reproduce, but no matter the cause of the crash, the database should not get corrupt.
I can exclude "disk full" as a possible cause.
From this log excerpt:
- a SIGSEGV happens
- the database is restarted but crashed again at start
- the database is restarted but crashed again at start, this time showing that it is corrupt beyond repair
```
2023-10-27 10:48:19 MSG merovingian[8]: database 'db01' (442387) has crashed with signal SIGSEGV (dumped core)
2023-10-27 10:48:19 MSG merovingian[8]: database 'db01' has crashed after start on 2023-10-27 09:36:42, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 0.10 0.03 (1-0=1)
2023-10-27 10:48:19 MSG db01[456921]: arguments: /opt/monetdb/bin/mserver5 --dbpath=/var/lib/monetdb/dbfarm/db01 --set=merovingian_uri=mapi:monetdb://1ae0b3e9fec4:50000/db01 --set=mapi_listenaddr=none --set=mapi_usock=/var/lib/monetdb/dbfarm/db01/.mapi.sock --set=monet_vault_key=/var/lib/monetdb/dbfarm/db01/.vaultkey --set=gdk_nr_threads=8 --set=tablet_threads=8 --set=max_clients=64 --set=sql_optimizer=sequential_pipe --set=embedded_py=3 --set=mal_for_all=yes
2023-10-27 10:48:19 MSG db01[456921]: # MonetDB 5 server v11.47.12
2023-10-27 10:48:19 MSG db01[456921]: # This is an unreleased version
2023-10-27 10:48:19 MSG db01[456921]: # Serving database 'db01', using 8 threads
2023-10-27 10:48:19 MSG db01[456921]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
2023-10-27 10:48:19 MSG db01[456921]: # Found 125.898 GiB available main-memory of which we use 102.607 GiB
2023-10-27 10:48:19 MSG db01[456921]: # Copyright (c) 1993 - July 2008 CWI.
2023-10-27 10:48:19 MSG db01[456921]: # Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved
2023-10-27 10:48:19 MSG db01[456921]: # Visit https://www.monetdb.org/ for further information
2023-10-27 10:48:20 MSG db01[456921]: # MonetDB/GIS module loaded
2023-10-27 10:48:20 MSG db01[456921]: # MonetDB/Python3 module loaded
2023-10-27 10:48:27 MSG db01[456921]: # MonetDB/SQL module loaded
2023-10-27 10:48:27 MSG db01[456921]: # Listening for UNIX domain connection requests on mapi:monetdb:///var/lib/monetdb/dbfarm/db01/.mapi.sock
2023-10-27 10:48:32 MSG merovingian[8]: database 'db01' (456921) has crashed with signal SIGSEGV (dumped core)
2023-10-27 10:48:36 MSG merovingian[8]: database 'db01' has crashed after start on 2023-10-27 10:48:19, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 0.20 0.07 (2-0=2)
2023-10-27 10:48:36 MSG db01[456940]: arguments: /opt/monetdb/bin/mserver5 --dbpath=/var/lib/monetdb/dbfarm/db01 --set=merovingian_uri=mapi:monetdb://1ae0b3e9fec4:50000/db01 --set=mapi_listenaddr=none --set=mapi_usock=/var/lib/monetdb/dbfarm/db01/.mapi.sock --set=monet_vault_key=/var/lib/monetdb/dbfarm/db01/.vaultkey --set=gdk_nr_threads=8 --set=tablet_threads=8 --set=max_clients=64 --set=sql_optimizer=sequential_pipe --set=embedded_py=3 --set=mal_for_all=yes
2023-10-27 10:48:37 MSG db01[456940]: # MonetDB 5 server v11.47.12
2023-10-27 10:48:37 MSG db01[456940]: # This is an unreleased version
2023-10-27 10:48:37 MSG db01[456940]: # Serving database 'db01', using 8 threads
2023-10-27 10:48:37 MSG db01[456940]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
2023-10-27 10:48:37 MSG db01[456940]: # Found 125.898 GiB available main-memory of which we use 102.607 GiB
2023-10-27 10:48:37 MSG db01[456940]: # Copyright (c) 1993 - July 2008 CWI.
2023-10-27 10:48:37 MSG db01[456940]: # Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved
2023-10-27 10:48:37 MSG db01[456940]: # Visit https://www.monetdb.org/ for further information
2023-10-27 10:48:37 MSG db01[456940]: # MonetDB/GIS module loaded
2023-10-27 10:48:37 MSG db01[456940]: # MonetDB/Python3 module loaded
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6246) transient
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6250) transient
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6247) transient
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6248) transient
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6249) transient
2023-10-27 10:48:37 MSG db01[456940]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(6251) transient
2023-10-27 10:48:37 ERR db01[456940]: #main thread: decref: ERROR: BBPrelease: tmp_14146 does not have logical references.
2023-10-27 10:48:37 ERR db01[456940]: #main thread: log_find_bat: ERROR: logger_find_bat failed to find bid for object 22078
2023-10-27 10:48:37 ERR db01[456940]: #main thread: store_load: CRITICAL: Cannot load catalog tables
2023-10-27 10:48:41 MSG merovingian[8]: database 'db01' (456940) has crashed with signal SIGSEGV (dumped core)
```
**Software versions**
- MonetDB version number 11.47.12
- OS and version: Fedora 38
- self-installed and compiled
| SIGSEGV cause database corruption | https://api.github.com/repos/MonetDB/MonetDB/issues/7410/comments | 3 | 2023-10-27T10:32:46Z | 2024-06-27T13:18:46Z | https://github.com/MonetDB/MonetDB/issues/7410 | 1,965,238,064 | 7,410 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
While numpy UDFs allow variadic arguments with * table returning numpy UDFs do not work properly (perhaps it is a feature request but it seems more like a bug).
**To Reproduce**
The UDF below :
CREATE FUNCTION python_table(arg2 string)
RETURNS TABLE (name STRING, country STRING, age INTEGER)
LANGUAGE PYTHON
{
result = dict()
result['name'] = ['Henk' , 'John' , 'Elizabeth']
result['country'] = ['NL' , 'USA' , 'UK']
result['age'] = [25, 30, 33]
return result
};
works with a query like: select * from python_table((select col from table));
but if I have:
CREATE FUNCTION python_table2(*)
RETURNS TABLE (name STRING, country STRING, age INTEGER)
LANGUAGE PYTHON
{
result = dict()
result['name'] = ['Henk' , 'John' , 'Elizabeth']
result['country'] = ['NL' , 'USA' , 'UK']
result['age'] = [25, 30, 33]
return result
};
the query
select * from python_table2((select col from table));
returns error: Scalar value expected
**Expected behavior**
It works when I have select * from python_table2('value'), but I cannot create numpy table returning UDFs with variadic arguments that takes as input a subquery, while I can do it only with static defined args (for other UDF types like aggregates and scalars this also works properly). The same happens also with C UDFs (while the C code produced automatically and stored at TEMP_DATA folder of the database is exactly the same in both cases).
| Numpy table returning UDFs with variadic arguments | https://api.github.com/repos/MonetDB/MonetDB/issues/7409/comments | 4 | 2023-10-26T09:43:23Z | 2024-06-27T13:18:45Z | https://github.com/MonetDB/MonetDB/issues/7409 | 1,963,122,282 | 7,409 |
[
"MonetDB",
"MonetDB"
] | It's impossible to handle a constant parameter in an aggregate function. I hope it's a bug, not the by design behaviour. (E.g. say, I want to evaluate a truncated mean and need to pass the upper and lower bounds as constants).
**To Reproduce**
Create an aggregate using the attached [source file](https://github.com/MonetDB/MonetDB/files/13168867/test.tgz).
Execute the following statements:
```sql
create table test(id int, value int);
insert into test(id, value) values(1, 1);
select myagg(id, 1) from test group by value;
```
**Expected behavior**
```
+-------------------------------------------------------------------------------------------+
| %1 |
+===========================================================================================+
| 00010203 |
+-------------------------------------------------------------------------------------------+
```
**Actual behavior**
```
TypeException:user.main[15]:'aggr.submyagg' undefined in: X_0:bat[:blob] := aggr.submyagg(X_1:bat[:int], X_2:bat[:int], X_3:bat[:oid], X_4:bat[:oid], true:bit);
```
So I have to do some workaround: accept the second parameter as `bat*`, create an iterator for it and do `BUNtail(it, 0)`. I think it's nor graceful neither very efficient.
And it does work for the ungrouped case, but I can't get the proper parameter value. It looks like there is some random number there.
```sql
select myagg(id, 1) from test;
```
**Expected behavior (in merovingian.log)**
```
#DFLOWworker1019: myagg: ERROR: COL2: 1
```
**Actual behavior (in merovingian.log)**
```
#DFLOWworker1019: myagg: ERROR: COL2: 1298
```
**Software versions**
- MonetDB v11.47.3 (hg id: 79dbf838f044 88683)
- Almalinux 8
- self-installed and compiled | It's impossible to handle a constant parameter in an aggregate function | https://api.github.com/repos/MonetDB/MonetDB/issues/7408/comments | 1 | 2023-10-25T17:21:52Z | 2023-10-25T19:04:27Z | https://github.com/MonetDB/MonetDB/issues/7408 | 1,961,890,836 | 7,408 |
[
"MonetDB",
"MonetDB"
] | An aggregate returns an error: `cannot use non GROUP BY column '...' in query results without an aggregate function`. But I don't have any columns in the SELECT list except my aggregate!
**To Reproduce**
Restore the database from the attached [snapshot](https://github.com/MonetDB/MonetDB/files/13162079/mydb3_20231007T141503UTC.tgz).
Create the aggregate using the attached [source file](https://github.com/MonetDB/MonetDB/files/13168951/test.tgz).
Run it:
```sql
select myagg(bin1, value, bin2, bin3) from test;
```
**Expected behavior**
```
+-------------------------------------------------------------------------------------------+
| %1 |
+===========================================================================================+
| 00010203 |
+-------------------------------------------------------------------------------------------+
```
**Actual behavior**
```
SELECT: cannot use non GROUP BY column 'test.bin3' in query results without an aggregate function
```
**Software versions**
- MonetDB v11.47.3 (hg id: 79dbf838f044 88683)
- Almalinux 8
- self-installed and compiled
| Error executing an aggregate: cannot use non GROUP BY column '...' in query results without an aggregate function | https://api.github.com/repos/MonetDB/MonetDB/issues/7407/comments | 1 | 2023-10-25T06:29:43Z | 2023-10-25T17:25:20Z | https://github.com/MonetDB/MonetDB/issues/7407 | 1,960,642,039 | 7,407 |
[
"MonetDB",
"MonetDB"
] | An aggregate returns an error: `b with s and g must be aligned`.
**To Reproduce**
Restore the database from the attached [snapshot](https://github.com/MonetDB/MonetDB/files/13126671/mydb3_20231007T092259UTC.tgz).
Create an aggregate using the attached [source file](https://github.com/MonetDB/MonetDB/files/13126672/test.tgz).
Run it:
```sql
select myagg(id) from test group by value;
```
**Expected behavior**
```
+-------------------------------------------------------------------------------------------+
| %1 |
+===========================================================================================+
| 00010203 |
+-------------------------------------------------------------------------------------------+
```
**Actual behaviour**
```
b with s and g must be aligned
```
**Software versions**
- MonetDB v11.47.3 (hg id: 79dbf838f044 88683)
- Almalinux 8
- self-installed and compiled
**Additional context**
* The same aggregate works fine if used in an update statement:
```sql
create table result(value blob);
insert into result values(null);
update result set value = (select myagg(id) from test group by value);
```
* The table was initially populated using `copy into` from a csv-file. The bug appears immediately after loading. Removing rows and changing columns doesn't affect the bug (that's what I actually did). | Error executing an aggregate: 'b with s and g must be aligned' | https://api.github.com/repos/MonetDB/MonetDB/issues/7406/comments | 7 | 2023-10-24T19:52:43Z | 2024-07-08T15:32:57Z | https://github.com/MonetDB/MonetDB/issues/7406 | 1,959,973,121 | 7,406 |
[
"MonetDB",
"MonetDB"
] | Just a (probably) outdated piece of documentation, on https://www.monetdb.org/documentation-Jun2023/user-guide/sql-manual/data-types/temporal-types/:
> Min and max years. The maximum and minimum dates and timestamps that can be stored are in the years 5,867,411 and -5,867,411, respectively. Interestingly, the year 0 is not a valid year. The year before 1 is called -1.
Perhaps this used to be the case? Nowadays year 0 is valid:
```
sql>select cast('0000-01-01' as date);
+------------+
| %2 |
+============+
| 0-01-01 |
+------------+
1 tuple
``` | Imprecise documentation about dates | https://api.github.com/repos/MonetDB/MonetDB/issues/7405/comments | 4 | 2023-10-18T17:32:41Z | 2024-06-27T13:18:44Z | https://github.com/MonetDB/MonetDB/issues/7405 | 1,950,294,016 | 7,405 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
When creating a table using as select, the column constraints are not respected.
**To Reproduce**
```
create table t1 (i int, d double not null);
create table t2 (i int default 99, d double);
insert into t1 values (1, pi()), (2, exp(1));
insert into t2 (d) values (pi()), (exp(1));
create table u1 as select * from t1 with data;
create table v1 as select * from t2 with data;
```
**Expected behavior**
Table defintions of `u1` and `v1` should be identical to `t1` and `t2`, resp.
**Software versions**
- Jun2023-SP2
- Fedora 38
- Installed from release package
**Issue labeling**
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
I did not check more combinations for the column definitions or things like casting column to other data type
| Table definitions not fully maintained in `create table select as` | https://api.github.com/repos/MonetDB/MonetDB/issues/7404/comments | 2 | 2023-10-05T09:11:02Z | 2023-10-28T09:29:34Z | https://github.com/MonetDB/MonetDB/issues/7404 | 1,927,776,610 | 7,404 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
When joining two columns that were generated with `row_number()`, a select over cartesian product is generated instead of join.
**To Reproduce**
```
create table a(i int);
create table b(i int);
insert into a values (10), (10);
insert into b values (20), (20);
plan
with
a1 as (select row_number() over() as r, i from a),
b1 as (select row_number() over() as r, i from b)
select a1.i, b1.i
from a1, b1
where a1.r = b1.r;
```
outputs:
```
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| rel |
+======================================================================================================================================================================+
| project ( |
| | select ( |
| | | crossproduct ( |
| | | | project ( |
| | | | | table("spinque"."a") [ "a"."i" MIN "10" MAX "10" NUNIQUES 1.000000 ] COUNT 2 |
| | | | ) [ "sys"."row_number"("sys"."star"(), boolean(1) "false", boolean(1) "false") as "a1"."r", "a"."i" NUNIQUES 1.000000 MIN "10" MAX "10" as "a1"."i" ] COUNT 2, |
| | | | project ( |
| | | | | table("spinque"."b") [ "b"."i" MIN "20" MAX "20" NUNIQUES 1.000000 ] COUNT 2 |
| | | | ) [ "sys"."row_number"("sys"."star"(), boolean(1) "false", boolean(1) "false") as "b1"."r", "b"."i" NUNIQUES 1.000000 MIN "20" MAX "20" as "b1"."i" ] COUNT 2 |
| | | ) [ ] COUNT 4 |
| | ) [ ("a1"."r") = ("b1"."r") ] COUNT 4 |
| ) [ "a1"."i" NUNIQUES 1.000000 MIN "10" MAX "10", "b1"."i" NUNIQUES 1.000000 MIN "20" MAX "20" ] COUNT 4 |
| # push_project_down 0 actions 2 usec |
| # merge_projects 0 actions 2 usec |
| # push_project_up 0 actions 2 usec |
| # split_project 0 actions 2 usec |
| # remove_redundant_join 0 actions 1 usec |
| # simplify_math 0 actions 2 usec |
| # optimize_exps 0 actions 3 usec |
| # optimize_select_and_joins_bottomup 0 actions 2 usec |
| # project_reduce_casts 0 actions 0 usec |
| # optimize_projections 0 actions 2 usec |
| # optimize_joins 0 actions 3 usec |
| # join_order 0 actions 8 usec |
| # optimize_semi_and_anti 0 actions 2 usec |
| # optimize_select_and_joins_topdown 0 actions 4 usec |
| # dce 0 actions 10 usec |
| # push_func_and_select_down 0 actions 3 usec |
| # get_statistics 0 actions 54 usec |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
```
**Software versions**
- MonetDB version number 11.47.12
- OS and version: Fedora 38
- self-installed and compiled
| Join not recognized between two row_number() columns | https://api.github.com/repos/MonetDB/MonetDB/issues/7403/comments | 4 | 2023-09-29T14:34:22Z | 2024-06-27T13:18:43Z | https://github.com/MonetDB/MonetDB/issues/7403 | 1,919,384,749 | 7,403 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A clear and concise description of what the bug is.
Granting select privileges to a user on merge table do not propagated properly to partition table. When set on the merge table a query with where clause on the merge table fails unexpectedly.
**To Reproduce**
Create a setting with minimal input for an external user to demonstrate the buggy behavior.
This includes the relevant part of the database schema description.
Performance trace of the rogue query (using the TRACE command)
1. Start the daemon and server and create the database instance using the `setup-db.sh` script.
2. Run the `run-test.sh` script to setup the schema, create the merge and partition tables, create the user and select privilege, run the allowed queries (of which some fail due to the bug) and denied queries (expected to fail, because of insufficient privileges). The run script also drops a partition table and recreates it again, after which the allowed queries are executed again, to see if they succeed, but they don't.
`setup-db.sh`:
```
monetdb status
monetdb stop bugdb
monetdb destroy -f bugdb
monetdb create bugdb
monetdb start bugdb
monetdb release bugdb
monetdb status
```
`run-test.sh` (note the different credentials):
```
DOTMONETDBFILE=~/.monetdb mclient -d bugdb < setup-schema.sql
DOTMONETDBFILE=~/.adam mclient -d bugdb < setup-tables.sql
DOTMONETDBFILE=~/.adam mclient -d bugdb < setup-user-grants.sql
echo -e "\n..:: This block of queries should *ALL* succeed because of permission allowed. However, ... ::.."
DOTMONETDBFILE=~/.user1 mclient -d bugdb < select-with-priv-allowed.sql
echo -e "..:: End of block of permission allowed queries ::.."
echo -e "\n..:: The next block of queries should *ALL* fail because of permission denied ::.."
DOTMONETDBFILE=~/.user1 mclient -d bugdb < select-with-priv-denied.sql
echo -e "..:: End of block of permission denied queries ::.."
DOTMONETDBFILE=~/.adam mclient -d bugdb < setup-drop-recreate-table.sql
DOTMONETDBFILE=~/.user1 mclient -d bugdb < select-with-priv-allowed.sql
```
`setup-schema.sql`, `setup-tables.sql`, `setup-user-grants.sql`:
```
ALTER USER "monetdb" RENAME TO "adam";
ALTER USER SET PASSWORD 'adam123' USING OLD PASSWORD 'monetdb';
CREATE SCHEMA "myschema" AUTHORIZATION "adam";
ALTER USER "adam" SET SCHEMA "myschema";
create merge table mt (i int, d double);
create table t1 (i int, d double);
create table t2 (i int, d double);
create table t3 (i int, d double);
alter table mt add table t1;
alter table mt add table t2;
alter table mt add table t3;
insert into t1 values (1, pi()),(2, exp(1));
insert into t2 values (10, 300),(20, 400);
insert into t3 values (100, 100.0),(200, 200.01);
create table u1 (i int, d double, t text);
insert into u1 values (1000, 2.3456, 'seven');
create table v1 (i int, j int);
insert into v1 values (10000, 1234);
create user user1 with unencrypted password 'user123' name 'User1' schema "myschema";
grant select on table "myschema".mt to "user1";
grant select on table "myschema".u1 to "user1";
```
`select-with-priv-allowed.sql`, `select-with-priv-denied.sql`:
```
-- These should be allowed. However, query 2-6 fail.
select count(*) from mt;
select count(*) from mt where i = 1;
select * from mt;
select * from mt where i = 1;
select * from mt where i = 10;
select * from mt where i = 100;
select * from u1;
-- These should be denied
select * from t1;
select * from t1 where i = 1;
select * from t2;
select * from t2 where i = 10;
select * from t3;
select * from t3 where i = 100;
select * from v1;
```
`setup-drop-recreate-table.sql`:
```
alter table mt drop table t1;
drop table t1;
create table t1 (i int, d double);
alter table mt add table t1;
insert into t1 values (1, 3.1415), (2, 2.7182), (3, 5.8597);
```
After this the `select-with-priv-allowed.sql` queries should succeed again, but they don't.
**Expected behavior**
A clear and concise description of what you expected to happen.
The `run-test.sh` script has allowed queries which should all succeed
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Software versions**
- MonetDB version number [a milestone label]
- OS and version: [e.g. Ubuntu 18.04]
- Installed from release package or self-installed and compiled
MonetDB version Jun2023-SP1
Fedora 37 (6.4.13)
Installed using cmake
**Issue labeling **
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
Add any other context about the problem here.
Scripts and queries are attached.
| Privileges on merge table not propagated to partition tables | https://api.github.com/repos/MonetDB/MonetDB/issues/7402/comments | 2 | 2023-09-13T09:02:56Z | 2024-06-27T13:18:42Z | https://github.com/MonetDB/MonetDB/issues/7402 | 1,894,073,653 | 7,402 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A slightly naughty (but perfectly valid) usage of aliases in UNION subqueries causes the wrong column being picked for the result.
**To Reproduce**
```sql
create table t(a int, b int);
insert into t values (1,10);
insert into t values (2,20);
select a as a, b as b from t
UNION
select b as a, a as b from t;
```
delivers:
```
+------+------+
| a | b |
+======+======+
| 1 | 10 |
| 2 | 20 |
| 10 | 10 |
| 20 | 20 |
+------+------+
4 tuples
```
**Expected behavior**
```
+------+------+
| a | b |
+======+======+
| 1 | 10 |
| 2 | 20 |
| 10 | 1 |
| 20 | 2 |
+------+------+
4 tuples
```
**Software versions**
- MonetDB version number v11.47.6
- OS and version: Fedora 38
- self-installed and compiled
| Column aliases used incorrectly in UNION subqueries | https://api.github.com/repos/MonetDB/MonetDB/issues/7401/comments | 3 | 2023-09-06T15:34:28Z | 2024-06-27T13:18:41Z | https://github.com/MonetDB/MonetDB/issues/7401 | 1,884,275,789 | 7,401 |
[
"MonetDB",
"MonetDB"
] | I was trying to deploy MonetDB on Azure running on Kubernetes v1.25.6 and it failed with following exception:
```
#2023-09-04 16:15:35: main thread: GDKmalloc_internal: ERROR: allocating too much memory
```
After looking deeper into the source code, it's seems to happen when initializing GDK and checking the max memory available.
In my opinion, the culprit is the following line.
https://github.com/MonetDB/MonetDB/blob/25a2a69633f2e5dc292742cf57dc8809484e2d59/gdk/gdk_utils.c#L701
We are only checking the swap max which is 0 in my case. I guess we should add memory.max and memory.swap.max to get the total of virtual memory.
I also saw that in cgroup v1, the sum of this 2 was available in a single file called memory.memsw.limit_in_bytes but we don't have this file.
I hope my reading of C code is correct, it's been a while ! | VM max memory is not check correctly for cgroups v2 | https://api.github.com/repos/MonetDB/MonetDB/issues/7400/comments | 7 | 2023-09-04T16:51:50Z | 2024-06-27T13:18:40Z | https://github.com/MonetDB/MonetDB/issues/7400 | 1,880,629,445 | 7,400 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Queries for data often experience delays and may take a significant amount of time to provide results.
**To Reproduce**
I rely on monetdb as my data warehouse. However, when BI tools generate large crossjoin queries, monetdb tends to take a long time to process them. I have noticed that during this time, the CPUs are not being utilized. Even simple queries like mclient -dolap also experience significant delays. I have included the query generated by the BI tools below. Could you please provide an explanation or recommend ways to enhance monetdb's processing efficiency?
** Configs
<img width="518" alt="Screenshot 2023-08-10 at 20 03 53" src="https://github.com/MonetDB/MonetDB/assets/73767803/4711fc08-778a-4bf2-9fb6-3a4edb985556">
**Expected behavior**
The queries are free from congestion and can generate results promptly.
**Screenshots**
**Software versions**
OS and version: Ubuntu 20.04.5 LTS (Focal Fossa)
MonetDB Database Server Toolkit v11.47.3 (Jun2023)
Installed from recompiled
[query.txt](https://github.com/MonetDB/MonetDB/files/12313045/query.txt)
| I am experiencing slow performance with MonetDB queries | https://api.github.com/repos/MonetDB/MonetDB/issues/7399/comments | 4 | 2023-08-10T13:09:53Z | 2024-01-26T11:59:54Z | https://github.com/MonetDB/MonetDB/issues/7399 | 1,845,160,462 | 7,399 |
[
"MonetDB",
"MonetDB"
] | Can anyone give me a script to backup the monet db, I was looking to use the sys.hot_snapshot option, does anyone use it that way? is the most suitable? If so, can you provide details of the procedure? | Can anyone give me a script to backup the monet db | https://api.github.com/repos/MonetDB/MonetDB/issues/7398/comments | 3 | 2023-08-04T15:22:58Z | 2023-08-09T11:23:19Z | https://github.com/MonetDB/MonetDB/issues/7398 | 1,836,947,836 | 7,398 |
[
"MonetDB",
"MonetDB"
] | Can anyone guide me about the error above , I believe I have corrupted my data but the monet service does not go up anymore
[root@mdc-prd-pgs02 pgsql]# monetdb start -a
starting database 'olap'... FAILED
start: starting 'olap' failed: database 'olap' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details
[root@mdc-prd-pgs02 pgsql]# tail -f /var/lib/pgsql/monetdb/merovingian.log
2023-08-02 11:01:06 ERR control[1573]: !monetdbd: an internal error has occurred 'database 'olap' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details'
2023-08-02 11:01:11 ERR merovingian[1573]: client error: database 'olap' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details
2023-08-02 11:03:21 ERR discovery[1573]: error while sending broadcast message: Network is unreachable
2023-08-02 11:13:22 ERR discovery[1573]: error while sending broadcast message: Network is unreachable
2023-08-02 11:14:32 MSG control[1573]: (local): served status list
2023-08-02 11:14:32 MSG merovingian[1573]: database 'olap' has crashed after start on 2023-07-30 00:16:05, attempting restart, up min/avg/max: -11384s/17h/6d, crash average: 1.00 1.00 1.00 (5050-1932=3118)
2023-08-02 11:14:33 MSG olap[3198]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/pgsql/monetdb/olap --set merovingian_uri=mapi:monetdb://mdc-prd-pgs02:50000/olap --set mapi_open=false --set mapi_ipv6=false --set mapi_port=0 --set mapi_usock=/var/lib/pgsql/monetdb/olap/.mapi.sock --set monet_vault_key=/var/lib/pgsql/monetdb/olap/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe
2023-08-02 11:14:33 ERR olap[3198]: #main thread: heapinit: !ERROR: "free" value larger than "size" in heap of bat 222093 on line 772
2023-08-02 11:14:36 MSG merovingian[1573]: database 'olap' (-1) has exited with exit status 1
2023-08-02 11:14:36 ERR control[1573]: (local): failed to fork mserver: database 'olap' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details | #main thread: heapinit: !ERROR: "free" value larger than "size" in heap of bat 222093 on line 772 | https://api.github.com/repos/MonetDB/MonetDB/issues/7397/comments | 5 | 2023-08-02T14:12:39Z | 2023-10-28T09:31:53Z | https://github.com/MonetDB/MonetDB/issues/7397 | 1,833,272,902 | 7,397 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
When I execute a complex query, this error appears.
**Screenshots**
**Software versions**
- MonetDB Database Server Toolkit v11.47.3 (Jun2023)
- OS and version: Ubuntu 20.04.5 LTS (Focal Fossa)
- Installed from compiled
| GDKextendf: CRITICAL: could not extend file: File too large | https://api.github.com/repos/MonetDB/MonetDB/issues/7396/comments | 1 | 2023-07-26T16:20:53Z | 2023-08-10T09:12:01Z | https://github.com/MonetDB/MonetDB/issues/7396 | 1,822,760,384 | 7,396 |
[
"MonetDB",
"MonetDB"
] | Can't start a DB with C UDFs after update to Jun 2023 release. Everything works fine on Sep 2022 SP2 release OR without C UDF library.
**To Reproduce**
Create a test UDF library:
```C
#include <monetdb_config.h>
#include <mal_exception.h>
#include "mel.h"
#include "mal_import.h"
#include "sql_import.h"
char* pm_echo(int32_t* res, int32_t* n)
{
if (n)
*res = *n;
else
*res = 0;
return MAL_SUCCEED;
}
static char pm_sql[] =
"create function pm_echo(n int) "
"returns int external name pm.echo; ";
static mel_func pm_init_funcs[] = {
command("pm", "echo", pm_echo, false,
"Echo a number",
args(1, 2, arg("", int), arg("n", int))),
{ .imp = NULL } /* sentinel */
};
LIB_STARTUP_FUNC(init_pm)
{
mal_module("pm", NULL, pm_init_funcs);
sql_register("pm", pm_sql);
}
```
Compile it and copy to the destination directory:
```
gcc -O3 -DNDEBUG -g \
-shared -fPIC -DPIC -o lib_pm.so \
-I/usr/include/monetdb \
*.c \
-lmonetdb5
cp lib_pm.so /usr/local/lib64/monetdb5/
```
Create a DB and start it:
```
monetdbd create mydbfarm
monetdbd start mydbfarm
monetdb create mydb
monetdb release mydb
monetdb set embedc=yes mydb
monetdb set loadmodules=pm mydb
monetdb start mydb
```
**Expected behavior**
```
starting database 'mydb'... done
```
**Actual behavior**
```
starting database 'mydb'... FAILED
start: starting 'mydb' failed: database 'mydb' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details
```
**Log**
```
2023-07-26 07:00:24 MSG merovingian[3958]: database 'mydb' has crashed after start on 2023-07-26 07:00:08, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 0.10 0.03 (1-0=1)
2023-07-26 07:00:24 MSG mydb[4046]: arguments: /usr/local/bin/mserver5 --dbpath=/home/almalinux/mydbfarm/mydb --set=merovingian_uri=mapi:monetdb://almalinux8.linuxvmimages.local:50000/mydb --set=mapi_listenaddr=none --set=mapi_usock=/home/almalinux/mydbfarm/mydb/.mapi.sock --set=monet_vault_key=/home/almalinux/mydbfarm/mydb/.vaultkey --set=gdk_nr_threads=8 --set=tablet_threads=8 --set=max_clients=64 --set=sql_optimizer=default_pipe --set=embedded_c=true --loadmodule=pm
2023-07-26 07:00:24 MSG mydb[4046]: # MonetDB 5 server v11.47.3 (hg id: 79dbf838f044 88683)
2023-07-26 07:00:24 MSG mydb[4046]: # This is an unreleased version
2023-07-26 07:00:24 MSG mydb[4046]: # Serving database 'mydb', using 8 threads
2023-07-26 07:00:24 MSG mydb[4046]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
2023-07-26 07:00:24 MSG mydb[4046]: # Found 7.581 GiB available main-memory of which we use 6.178 GiB
2023-07-26 07:00:24 MSG mydb[4046]: # Copyright (c) 1993 - July 2008 CWI.
2023-07-26 07:00:24 MSG mydb[4046]: # Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved
2023-07-26 07:00:24 MSG mydb[4046]: # Visit https://www.monetdb.org/ for further information
2023-07-26 07:00:28 MSG merovingian[3958]: database 'mydb' (4046) has crashed with signal SIGSEGV (dumped core)
```
**Stack trace**
```
#0 STRprelude ()
at /home/almalinux/MonetDB-Sep2022_SP2_release/monetdb5/modules/atoms/str.c:2931
#1 STRprelude ()
at /home/almalinux/MonetDB-Sep2022_SP2_release/monetdb5/modules/atoms/str.c:2915
#2 0x00007fc9bb8ea337 in malPrelude (mapi=<optimized out>, sql=<optimized out>,
listing=<optimized out>, c=<optimized out>)
at /home/almalinux/MonetDB-Jun2023_release/monetdb5/mal/mal_prelude.c:488
#3 malIncludeModules (c=c@entry=0xbe87e0, modules=modules@entry=0x7ffcb6d99c20,
listing=listing@entry=0, no_mapi_server=no_mapi_server@entry=false,
initpasswd=initpasswd@entry=0x0)
at /home/almalinux/MonetDB-Jun2023_release/monetdb5/mal/mal_prelude.c:510
#4 0x00007fc9bb8e734e in malBootstrap (modules=modules@entry=0x7ffcb6d99c20,
embedded=embedded@entry=false, initpasswd=initpasswd@entry=0x0)
at /home/almalinux/MonetDB-Jun2023_release/monetdb5/mal/mal_session.c:63
#5 0x00007fc9bb8c9b6b in mal_init (modules=modules@entry=0x7ffcb6d99c20,
embedded=embedded@entry=false, initpasswd=initpasswd@entry=0x0,
caller_revision=caller_revision@entry=0x405b30 <revision> "79dbf838f044 88683")
at /home/almalinux/MonetDB-Jun2023_release/monetdb5/mal/mal.c:89
#6 0x0000000000402aa5 in main (argc=<optimized out>, av=<optimized out>)
at /home/almalinux/MonetDB-Jun2023_release/tools/mserver/mserver5.c:804
```
**Software versions**
- MonetDB Database Server Toolkit v11.47.3 (hg id: 79dbf838f044 88683)
- AlmaLinux 8.6 (Sky Tiger)
- Compiled from: https://www.monetdb.org/hg/MonetDB/rev/Jun2023_release
**Issue labeling**
C UDF so library
| C UDF library isn't loaded | https://api.github.com/repos/MonetDB/MonetDB/issues/7395/comments | 2 | 2023-07-26T11:10:38Z | 2024-06-27T13:18:38Z | https://github.com/MonetDB/MonetDB/issues/7395 | 1,822,169,450 | 7,395 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
**To Reproduce**
Restarting the database, or restarting the server all get the above error.
**Expected behavior**
Can restart the database normally
**Screenshots**
**Software versions**
- MonetDB Database Server Toolkit v11.47.3 (Jun2023)
- OS and version: Ubuntu 20.04.5 LTS (Focal Fossa)
- Installed from release package
**Issue labeling **
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
Add any other context about the problem here.
`2023-06-28 03:06:33 ERR control[8178]: (local): failed to release database 'ebiz_olap': database 'ebiz_olap' is not under maintenance
2023-06-28 03:06:58 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:03 MSG merovingian[8178]: database 'ebiz_olap' (-1) has exited with exit status 1
2023-06-28 03:07:03 ERR control[8178]: !monetdbd: an internal error has occurred 'database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:07:03 ERR merovingian[8178]: client error: database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:07:03 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:08 MSG merovingian[8178]: database 'ebiz_olap' (-1) has exited with exit status 1
2023-06-28 03:07:08 ERR control[8178]: !monetdbd: an internal error has occurred 'database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:10:50 ERR control[8178]: (local): received stop signal for non running database: ebiz_olap
2023-06-28 03:10:57 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:04 ERR ebiz_olap[30908]: message repeated 4 times: #main thread: heapinit: CRITICAL: invalid format for BBP.dir on line 258
2023-06-28 03:10:59 ERR ebiz_olap[30908]: unexpected file BBP.bak, leaving /opt/data_monetdb/ebiz_olap/bat/LEFTOVERS.
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: log_load: ERROR: there is no logger catalog, but there is a log file.
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: mvc_init: CRITICAL: Unable to create system tables
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: createExceptionInternal: ERROR: SQLException:SQLinit:42000!Catalogue initialization failed
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: SQLprelude: CRITICAL: Fatal error during initialization: SQLException:SQLinit:42000!Catalogue initialization failed
2023-06-28 03:10:57 MSG ebiz_olap[30908]: message repeated 10 times: arguments: /usr/bin/mserver5 --dbpath=/opt/data_monetdb/ebiz_olap --set=merovingian_uri=mapi:monetdb://FHS-MoentDB-Local:50000/ebiz_olap --dbextra=/monetdbextra/ebiz_olap --set=mapi_listenaddr=none --set=mapi_usock=/opt/data_monetdb/ebiz_olap/.mapi.sock --set=monet_vault_key=/opt/data_monetdb/ebiz_olap/.vaultkey --set=gdk_nr_threads=128 --set=max_clients=500 --set=sql_optimizer=default_pipe --set=embedded_py=3`
File: merovingian.log
| BBPextend: ERROR: trying to extend BAT pool beyond the limit (163840000) | https://api.github.com/repos/MonetDB/MonetDB/issues/7394/comments | 9 | 2023-07-14T08:43:32Z | 2024-06-27T13:18:37Z | https://github.com/MonetDB/MonetDB/issues/7394 | 1,804,473,477 | 7,394 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
1. Statistical time appears sql+opt+run < clk.
2.Whether Monetdb statistics the time from disk copy to memory in Trace or -t.
**To Reproduce**
TPCH-Q1
**Expected behavior**
1. It is described in document that “The large difference of the clk:6.435 ms compared to the sum of sql + opt + run = 1.797 ms stems from the client-server protocol. In the embedded version of MonetDB these numbers will be much more close.”，but in the actual measurement there is a case where sql + opt + run > clk.
2. Looking at tracelog via Trace does not reveal a MAL about reading disk data, nor does it have a corresponding time. Is this because Monetdb does not count the time spent scan data?
**Screenshots**
non
**Software versions**
- MonetDB 5 server 11.47.3
- Ubuntu 20.04.6 LTS
- self-installed and compiled
**Issue labeling **
Performance, Trace
**Additional context**
non
| Doubts about the execution time of the system statistics | https://api.github.com/repos/MonetDB/MonetDB/issues/7393/comments | 3 | 2023-07-06T15:52:36Z | 2024-06-28T09:31:01Z | https://github.com/MonetDB/MonetDB/issues/7393 | 1,791,821,594 | 7,393 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
Not exactly a problem - just an idea of how to (possibly) improve the performance.
**Describe the solution you'd like**
Recently I tested a lot of software with PGO and measured the performance improvements from PGO - the results are [here](https://github.com/zamazan4ik/awesome-pgo/). Since my results show interesting improvements on a lot of databases I think it would be a good idea to measure PGO effects on MonetDB as well. If the results will show an improvement - would be great to see a note in the documentation about PGO.
I think for MonetDB the most interesting experience would be from SQLite with PGO - https://sqlite.org/forum/forumpost/7ce7a5f03d .
| Evaluate Profile-Guided Optimization | https://api.github.com/repos/MonetDB/MonetDB/issues/7392/comments | 2 | 2023-07-06T10:38:34Z | 2024-06-27T13:18:35Z | https://github.com/MonetDB/MonetDB/issues/7392 | 1,791,287,227 | 7,392 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
As of today, greatest and least functions are limited to two arguments while in the new SQL 2023 norm, there is no limit to the number of arguments
https://sgbd.developpez.com/actu/345162/La-norme-SQL-2023-est-finalisee-et-livree-avec-de-nouvelles-fonctionnalites-pour-le-format-JSON-des-modifications-du-langage-SQL-existant-et-les-requetes-sur-les-graphes-de-proprietes/
**Describe the solution you'd like**
Obviously an unimited argument number for least and greatest
**Describe alternatives you've considered**
nested several current greatest/least but that's ugly
**Additional context**
Best regards,
Simon
| SQL 2023 : greatest/least functions with unlimited arguments (not only 2) | https://api.github.com/repos/MonetDB/MonetDB/issues/7391/comments | 1 | 2023-07-01T18:50:55Z | 2024-06-27T13:18:34Z | https://github.com/MonetDB/MonetDB/issues/7391 | 1,784,150,404 | 7,391 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
The are 40 crashes found in MonetDB (node 95dba4e85799). **Some of them may be duplicate bugs.**
You can browse them here: [https://github.com/fuboat/BugList-MonetDB-95dba4e85799](https://github.com/fuboat/BugList-MonetDB-95dba4e85799)
The SQL statements to trigger them and the corresponding backtrace are shown in files listed in the `pocs` dir of the repository (01.sql ~ 40.sql).
I am not sure whether it is an appropriate way to report these bugs; if more information needs to be provide, or there are some questions or suggestions, please tell me.
**Software versions**
- MonetDB 5 server v11.48.0 (hg id: 95dba4e85799 88693) (download from the default branch of https://www.monetdb.org/hg/MonetDB/)
- MonetDB client version: version 11.48.0 (hg id: 95dba4e85799 88693)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The full command line of compilation is as follow:
```bash
wget https://www.monetdb.org/hg/MonetDB/archive/default.zip
unzip ./default.zip
cd MonetDB-default/
mkdir build
cd build
CC=clang-12 CXX=clang++-12 cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo
make install -j20
```
**To Reproduce**
- Start the server in memory: `/usr/local/bin/mserver5 --in-memory`
- Execute the files in the `pocs` dir of [this repository](https://github.com/fuboat/BugList-MonetDB-95dba4e85799) through mclient. For example: `/usr/local/bin/mclient < ./pocs/00.sql`
- Check whether the server crashed: `pgrep mserver5 || echo "Server crashed."`
**Issue labeling**
bug
**Additional context**
None | Some MonetDB Server crashes found | https://api.github.com/repos/MonetDB/MonetDB/issues/7390/comments | 2 | 2023-06-28T20:11:07Z | 2024-06-27T13:18:33Z | https://github.com/MonetDB/MonetDB/issues/7390 | 1,779,680,277 | 7,390 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
On the server, I have 4 databases, but after restarting the server, I can't start up one of them.
```
2023-06-28 02:43:57 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 02:44:00 MSG merovingian[8178]: database 'ebiz_olap' (-1) has exited with exit status 1
```
This situation has happened many times, every time I restart after having data, I get this error.
**To Reproduce**
Restarting the database, or restarting the server all get the above error.
**Expected behavior**
Can restart the database normally
**Screenshots**
**Software versions**
- MonetDB version number v11.45.13 (Sep2022-SP2)
- OS and version: Ubuntu 20.04
- Installed from release package
**Issue labeling **
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
Add any other context about the problem here.
```
2023-06-28 03:06:33 ERR control[8178]: (local): failed to release database 'ebiz_olap': database 'ebiz_olap' is not under maintenance
2023-06-28 03:06:58 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:03 MSG merovingian[8178]: database 'ebiz_olap' (-1) has exited with exit status 1
2023-06-28 03:07:03 ERR control[8178]: !monetdbd: an internal error has occurred 'database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:07:03 ERR merovingian[8178]: client error: database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:07:03 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:08 MSG merovingian[8178]: database 'ebiz_olap' (-1) has exited with exit status 1
2023-06-28 03:07:08 ERR control[8178]: !monetdbd: an internal error has occurred 'database 'ebiz_olap' appears to shut itself down after starting
2023-06-28 03:10:50 ERR control[8178]: (local): received stop signal for non running database: ebiz_olap
2023-06-28 03:10:57 MSG merovingian[8178]: starting database 'ebiz_olap', up min/avg/max: 0s/2d/4d, crash average: 0.00 0.00 0.00 (2-2=0)
2023-06-28 03:07:04 ERR ebiz_olap[30908]: message repeated 4 times: #main thread: heapinit: CRITICAL: invalid format for BBP.dir on line 258
2023-06-28 03:10:59 ERR ebiz_olap[30908]: unexpected file BBP.bak, leaving /opt/data_monetdb/ebiz_olap/bat/LEFTOVERS.
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: log_load: ERROR: there is no logger catalog, but there is a log file.
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: mvc_init: CRITICAL: Unable to create system tables
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: createExceptionInternal: ERROR: SQLException:SQLinit:42000!Catalogue initialization failed
2023-06-28 03:10:59 ERR ebiz_olap[30908]: #main thread: SQLprelude: CRITICAL: Fatal error during initialization: SQLException:SQLinit:42000!Catalogue initialization failed
2023-06-28 03:10:57 MSG ebiz_olap[30908]: message repeated 10 times: arguments: /usr/bin/mserver5 --dbpath=/opt/data_monetdb/ebiz_olap --set=merovingian_uri=mapi:monetdb://FHS-MoentDB-Local:50000/ebiz_olap --dbextra=/monetdbextra/ebiz_olap --set=mapi_listenaddr=none --set=mapi_usock=/opt/data_monetdb/ebiz_olap/.mapi.sock --set=monet_vault_key=/opt/data_monetdb/ebiz_olap/.vaultkey --set=gdk_nr_threads=128 --set=max_clients=500 --set=sql_optimizer=default_pipe --set=embedded_py=3
```
merovingian.log
`2023-06-28 02:33:41 ERR ebiz_olap[3840]: #main thread: heapinit: CRITICAL: invalid format for BBP.dir on line 259`
| #main thread: heapinit: CRITICAL: invalid format for BBP.dir | https://api.github.com/repos/MonetDB/MonetDB/issues/7389/comments | 1 | 2023-06-28T00:39:58Z | 2023-06-30T15:30:36Z | https://github.com/MonetDB/MonetDB/issues/7389 | 1,777,954,682 | 7,389 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A query that works fie on 11.43 results in a large crossproduct (or, a normal crossproduct that tries to allocate too much memory?) in 11.47.
```
2023-06-17 19:04:48 ERR 291[12779]: #client1: createExceptionInternal: ERROR: MALException:algebra.crossproduct:GDK reported error: GDKextendf: could not extend file: No space left on device
2023-06-17 19:04:48 ERR 291[12779]: #client1: createExceptionInternal: ERROR: !ERROR: HEAPalloc: Insufficient space for HEAP of 2439655325696 bytes.
2023-06-17 19:04:48 ERR 291[12779]: #client1: createExceptionInternal: ERROR: !ERROR: GDKextendf: could not extend file: No space left on device
2023-06-17 19:04:48 ERR 291[12779]: #client1: createExceptionInternal: ERROR: !ERROR: HEAPalloc: Insufficient space for HEAP of 2439655325696 bytes.
```
**To Reproduce**
I will send a script and data in private.
**Software versions**
- MonetDB version number 11.47.0
- OS and version: Fedora 38
- self-installed and compiled
| Query results in large cross product | https://api.github.com/repos/MonetDB/MonetDB/issues/7388/comments | 1 | 2023-06-17T17:13:07Z | 2024-06-27T13:18:32Z | https://github.com/MonetDB/MonetDB/issues/7388 | 1,761,928,497 | 7,388 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes in `rel_sequences` after executing SQL statements through mclient.
**To Reproduce**
```sql
ALTER SEQUENCE x INCREMENT BY 2;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7ff49bdd36d0 (rel_sequences+0x830)
#1 0x7ff49bdb10c1 (rel_semantic+0xc1)
#2 0x7ff49bc8eb53 (sql_symbol2relation+0x73)
#3 0x7ff49bca810d (SQLparser+0x37d)
#4 0x7ff49bca787b (SQLengine_+0x59b)
#5 0x7ff49bca6343 (SQLengine+0x23)
#6 0x7ff49c0356cf (runScenario+0x4f)
#7 0x7ff49c03616c (MSscheduleClient+0x68c)
#8 0x7ff49c0ddc2b (doChallenge+0xfb)
#9 0x7ff49c75cba0 (THRstarter+0x100)
#10 0x7ff49c7cccc4 (thread_starter+0x34)
#11 0x7ff49bb41609 (start_thread+0xd9)
#12 0x7ff49ba66133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes in `rel_sequences` | https://api.github.com/repos/MonetDB/MonetDB/issues/7387/comments | 2 | 2023-06-16T18:46:26Z | 2024-06-27T13:18:31Z | https://github.com/MonetDB/MonetDB/issues/7387 | 1,761,141,292 | 7,387 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes in `rel_deps` after executing SQL statements through mclient.
**To Reproduce**
```sql
CREATE VIEW t2 AS SELECT 1 UNION ALL SELECT 1;
CREATE VIEW v2 AS SELECT * FROM t2;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7fc48d1c68d1 (rel_deps+0x191)
#1 0x7fc48d1c6997 (rel_deps+0x257)
#2 0x7fc48d1c670a (rel_dependencies+0x4a)
#3 0x7fc48d072b25 (create_table_or_view+0x865)
#4 0x7fc48d0aab57 (SQLcreate_view+0xe7)
#5 0x7fc48d404c63 (runMALsequence+0x763)
#6 0x7fc48d40431e (runMAL+0x9e)
#7 0x7fc48d08b9f9 (SQLrun+0xd9)
#8 0x7fc48d08cbee (SQLengineIntern+0x4e)
#9 0x7fc48d08a8c2 (SQLengine_+0x5e2)
#10 0x7fc48d089343 (SQLengine+0x23)
#11 0x7fc48d4186cf (runScenario+0x4f)
#12 0x7fc48d41916c (MSscheduleClient+0x68c)
#13 0x7fc48d4c0c2b (doChallenge+0xfb)
#14 0x7fc48db3fba0 (THRstarter+0x100)
#15 0x7fc48dbafcc4 (thread_starter+0x34)
#16 0x7fc48cf24609 (start_thread+0xd9)
#17 0x7fc48ce49133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes in `rel_deps` | https://api.github.com/repos/MonetDB/MonetDB/issues/7386/comments | 1 | 2023-06-16T18:43:11Z | 2024-06-27T13:18:30Z | https://github.com/MonetDB/MonetDB/issues/7386 | 1,761,137,805 | 7,386 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes in `GDKfree` after executing SQL statements through mclient.
**To Reproduce**
1. Use mclient to connect MonetDB server;
2. Try to execute the following SQL statements **multiple times**. Sometimes they will crash the server. (On my machine, the server crashes after repeating executing these SQLs with at most 4 times)
```sql
DROP SCHEMA test CASCADE;
CREATE SCHEMA test;
SET SCHEMA test;
CREATE TABLE src (src_c1_pkey INT, c1 VARCHAR(100));
START TRANSACTION;
DELETE FROM src;
ALTER TABLE src DROP src_c1_pkey;
INSERT INTO src VALUES(1,1),(2,2),(3,3),(4,4),(6,6),(7,7),(8,8),(9,9),(10,10);
COMMIT;
SET SCHEMA sys;
DROP SCHEMA test CASCADE;
CREATE SCHEMA test;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f280338000b (gsignal+0xcb)
#1 0x7f280335f859 (abort+0x12b)
#2 0x7f28033ca26e (__fsetlocking+0x42e)
#3 0x7f28033d22fc (pthread_attr_setschedparam+0x54c)
#4 0x7f28033d3f6d (pthread_attr_setschedparam+0x21bd)
#5 0x7f280414f765 (GDKfree+0x25)
#6 0x7f280377af7b (destroy_delta+0x7b)
#7 0x7f280377576d (destroy_col+0x2d)
#8 0x7f2803745345 (column_destroy+0x45)
#9 0x7f2803761ec2 (list_destroy2+0xa2)
#10 0x7f2803760d14 (ol_destroy+0x34)
#11 0x7f2803745450 (table_destroy+0x90)
#12 0x7f280375ec17 (objectversion_destroy+0x77)
#13 0x7f280375eb4f (os_destroy+0xcf)
#14 0x7f2803750cdc (schema_destroy+0x7c)
#15 0x7f280375ec17 (objectversion_destroy+0x77)
#16 0x7f280376065d (objectversion_destroy_recursive+0x3d)
#17 0x7f2803760345 (tc_gc_objectversion+0x75)
#18 0x7f280374a307 (store_pending_changes+0x307)
#19 0x7f280374ea87 (sql_trans_commit+0x567)
#20 0x7f2803759353 (sql_trans_end+0x83)
#21 0x7f280379c10c (mvc_commit+0x4fc)
#22 0x7f280369d564 (SQLengine_+0x284)
#23 0x7f280369c343 (SQLengine+0x23)
#24 0x7f2803a2b6cf (runScenario+0x4f)
#25 0x7f2803a2c16c (MSscheduleClient+0x68c)
#26 0x7f2803ad3c2b (doChallenge+0xfb)
#27 0x7f2804152ba0 (THRstarter+0x100)
#28 0x7f28041c2cc4 (thread_starter+0x34)
#29 0x7f2803537609 (start_thread+0xd9)
#30 0x7f280345c133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`.
If the crash cannot be reproduced easily, please tell me. I will try to provide the whole steps to trigger the crash as possible. | MonetDB server 11.46.0 crashes in `GDKfree` | https://api.github.com/repos/MonetDB/MonetDB/issues/7385/comments | 3 | 2023-06-16T18:40:11Z | 2023-09-18T07:58:41Z | https://github.com/MonetDB/MonetDB/issues/7385 | 1,761,134,477 | 7,385 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes at `__nss_database_lookup` after executing SQL statements through mclient.
**To Reproduce**
Use the `mclient` binary to connect MonetDB server and execute the following stmts:
```sql
create schema test;
drop schema test cascade;
create schema test;
set schema test;
CREATE TABLE test (sect int NOT NULL auto_increment, PRIMARY KEY (sect));
create trigger count after delete on test for each row insert into test values (1);
delete from test;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f76ea76ebee (__nss_database_lookup+0x2078e)
#1 0x7f76eadf66fd (OPTemptybindImplementation+0x4fd)
#2 0x7f76eae124f1 (OPTwrapper+0x191)
#3 0x7f76eacdae23 (optimizeMALBlock+0x1a3)
#4 0x7f76ea98391f (SQLoptimizeQuery+0x1df)
#5 0x7f76ea94c57b (SQLparser+0x7eb)
#6 0x7f76ea94b87b (SQLengine_+0x59b)
#7 0x7f76ea94a343 (SQLengine+0x23)
#8 0x7f76eacd96cf (runScenario+0x4f)
#9 0x7f76eacda16c (MSscheduleClient+0x68c)
#10 0x7f76ead81c2b (doChallenge+0xfb)
#11 0x7f76eb400ba0 (THRstarter+0x100)
#12 0x7f76eb470cc4 (thread_starter+0x34)
#13 0x7f76ea7e5609 (start_thread+0xd9)
#14 0x7f76ea70a133 (clone+0x43)
```
**Screenshots**
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`.
Using the mlient or unixODBC with command line like `isql monetdb -e` can reproduce the crash. But command line `isql monetdb` (without the -e option) cannot reproduce it. | MonetDB server 11.46.0 crashes at `__nss_database_lookup` | https://api.github.com/repos/MonetDB/MonetDB/issues/7384/comments | 2 | 2023-06-16T18:25:56Z | 2024-06-27T13:18:29Z | https://github.com/MonetDB/MonetDB/issues/7384 | 1,761,117,903 | 7,384 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes at `list_append` after executing SQL statements through mclient.
**To Reproduce**
```sql
create table t1(c1 int auto_increment primary key NOT NULL);
create trigger i1 after insert on t1 for each row insert into t1 values(NULL);
insert into t1 values(NULL);
```
**Expected behavior**
This crash is strange. From the backtrace as follows, we can know that the crash is caused by infinite recursion.
However, if we change the first statement into `create table t1(c1 int);`, the MonetDB will return the message `Query too complex: running out of stack space` when executing the third stmt. So, MonetDB handles out of stack space, but it does not work with some special table definitions?
What's more, the definition of the table contains the `NOT NULL` constraint, which should fail the third stmt. If we remove the create trigger statement, MonetDB will return the message `INSERT INTO: NOT NULL constraint violated for column t1.c1` when executing the insert stmt. But with the create trigger stmt, it crashes instead.
Anyway, I think the expected behavior is to return the error message `Query too complex: running out of stack space` or `INSERT INTO: NOT NULL constraint violated for column t1.c1`, instead of crashing straightly.
**Backtrace**
```
#0 0x7f0c3760dbda (list_append+0x1a)
#1 0x7f0c376669c6 (rel_insert+0x196)
#2 0x7f0c3766abb3 (rel_updates+0x1ce3)
#3 0x7f0c376c6c11 (sequential_block+0x121)
#4 0x7f0c376c52dc (rel_psm+0x131c)
#5 0x7f0c37653091 (rel_semantic+0x91)
#6 0x7f0c37652e6a (rel_parse+0x19a)
#7 0x7f0c37563102 (sql_insert_triggers+0x232)
#8 0x7f0c3755bb5e (rel2bin_insert+0x148e)
#9 0x7f0c37554539 (subrel_bin+0xd69)
#10 0x7f0c3755f218 (exp_bin+0x29e8)
#11 0x7f0c37558567 (subrel_bin+0x4d97)
#12 0x7f0c37563162 (sql_insert_triggers+0x292)
#13 0x7f0c3755bb5e (rel2bin_insert+0x148e)
#14 0x7f0c37554539 (subrel_bin+0xd69)
#15 0x7f0c3755f218 (exp_bin+0x29e8)
#16 0x7f0c37558567 (subrel_bin+0x4d97)
#17 0x7f0c37563162 (sql_insert_triggers+0x292)
...
#7407 0x7f0c37563162 (sql_insert_triggers+0x292)
#7408 0x7f0c3755bb5e (rel2bin_insert+0x148e)
#7409 0x7f0c37554539 (subrel_bin+0xd69)
#7410 0x7f0c3755373b (output_rel_bin+0x6b)
#7411 0x7f0c3757f9d9 (backend_dumpstmt+0x199)
#7412 0x7f0c3754a367 (SQLparser+0x5d7)
#7413 0x7f0c3754987b (SQLengine_+0x59b)
#7414 0x7f0c37548343 (SQLengine+0x23)
#7415 0x7f0c378d76cf (runScenario+0x4f)
#7416 0x7f0c378d816c (MSscheduleClient+0x68c)
#7417 0x7f0c3797fc2b (doChallenge+0xfb)
#7418 0x7f0c37ffeba0 (THRstarter+0x100)
#7419 0x7f0c3806ecc4 (thread_starter+0x34)
#7420 0x7f0c373e3609 (start_thread+0xd9)
#7421 0x7f0c37308133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes at `list_append` | https://api.github.com/repos/MonetDB/MonetDB/issues/7383/comments | 2 | 2023-06-16T17:58:27Z | 2024-06-27T13:18:28Z | https://github.com/MonetDB/MonetDB/issues/7383 | 1,761,077,451 | 7,383 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes at `gc_col` after executing SQL statements through ODBC.
**To Reproduce**
1. Configure the unixODBC with MonetDB ODBC drivers
2. Use the command line like `isql monetdb -v -e` to connect (**to trigger the crash, the '-e' option is necessary.** But I don't know why)
3. Execute the following SQL statements:
```sql
START TRANSACTION;
CREATE TEMPORARY TABLE t1 (keyc INT, c1 VARCHAR(100), c2 VARCHAR(100), PRIMARY KEY(keyc));
CREATE TABLE c1(c2 DECIMAL(9,4) NOT NULL);
SAVEPOINT a_a;
TRUNCATE TABLE t1;
DELETE FROM w;
COMMIT;
SELECT 1;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7ff2e7285dd6 (gc_col+0x26)
#1 0x7ff2e7282cd5 (tc_gc_col+0x15)
#2 0x7ff2e7251307 (store_pending_changes+0x307)
#3 0x7ff2e7255a87 (sql_trans_commit+0x567)
#4 0x7ff2e7260353 (sql_trans_end+0x83)
#5 0x7ff2e72a310c (mvc_commit+0x4fc)
#6 0x7ff2e71a4564 (SQLengine_+0x284)
#7 0x7ff2e71a3343 (SQLengine+0x23)
#8 0x7ff2e75326cf (runScenario+0x4f)
#9 0x7ff2e753316c (MSscheduleClient+0x68c)
#10 0x7ff2e75dac2b (doChallenge+0xfb)
#11 0x7ff2e7c59ba0 (THRstarter+0x100)
#12 0x7ff2e7cc9cc4 (thread_starter+0x34)
#13 0x7ff2e703e609 (start_thread+0xd9)
#14 0x7ff2e6f63133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`.
If the crash cannot be reproduced easily, please tell me. I will try to provide the whole steps to trigger the crash as possible. | MonetDB server 11.46.0 crashes at `gc_col` | https://api.github.com/repos/MonetDB/MonetDB/issues/7382/comments | 2 | 2023-06-16T17:28:01Z | 2024-06-27T13:18:27Z | https://github.com/MonetDB/MonetDB/issues/7382 | 1,761,035,852 | 7,382 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes at `log_create_delta` after executing SQL statements through mclient.
**To Reproduce**
```sql
CREATE TABLE t1(unique_constraint INT PRIMARY KEY);
START TRANSACTION;
ALTER TABLE t1 ADD COLUMN uniq_c1_c2_c3 INT;
ALTER TABLE t1 DROP COLUMN uniq_c1_c2_c3;
COMMIT;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f19dc711703 (log_create_delta+0x23)
#1 0x7f19dc7116bd (log_create_col+0x1d)
#2 0x7f19dc6e088e (sql_trans_commit+0x36e)
#3 0x7f19dc6eb353 (sql_trans_end+0x83)
#4 0x7f19dc72e10c (mvc_commit+0x4fc)
#5 0x7f19dc65532c (SQLtransaction_commit+0x9c)
#6 0x7f19dc9a9c63 (runMALsequence+0x763)
#7 0x7f19dc9a931e (runMAL+0x9e)
#8 0x7f19dc6309f9 (SQLrun+0xd9)
#9 0x7f19dc631bee (SQLengineIntern+0x4e)
#10 0x7f19dc62f8c2 (SQLengine_+0x5e2)
#11 0x7f19dc62e343 (SQLengine+0x23)
#12 0x7f19dc9bd6cf (runScenario+0x4f)
#13 0x7f19dc9be16c (MSscheduleClient+0x68c)
#14 0x7f19dca65c2b (doChallenge+0xfb)
#15 0x7f19dd0e4ba0 (THRstarter+0x100)
#16 0x7f19dd154cc4 (thread_starter+0x34)
#17 0x7f19dc4c9609 (start_thread+0xd9)
#18 0x7f19dc3ee133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes at `log_create_delta` | https://api.github.com/repos/MonetDB/MonetDB/issues/7381/comments | 2 | 2023-06-16T17:04:12Z | 2024-06-27T13:18:27Z | https://github.com/MonetDB/MonetDB/issues/7381 | 1,761,007,588 | 7,381 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server 11.46.0 crashes at `BLOBcmp` after executing SQL statements through mclient.
**To Reproduce**
```sql
CREATE TABLE a (p_id INT, p_name BLOB);
INSERT INTO a VALUES (1,NULL);
TRACE select * from a where p_name='Lilu';
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f2b15259d39 (BLOBcmp+0x19)
#1 0x7f2b14b2a171 (prepareMalEvent+0x541)
#2 0x7f2b14b2b10f (sqlProfilerEvent+0x6f)
#3 0x7f2b14b152ec (runtimeProfileExit+0x11c)
#4 0x7f2b14b1ab01 (runMALsequence+0x1601)
#5 0x7f2b14b1d5d4 (DFLOWworker+0x2c4)
#6 0x7f2b15254ba0 (THRstarter+0x100)
#7 0x7f2b152c4cc4 (thread_starter+0x34)
#8 0x7f2b14639609 (start_thread+0xd9)
#9 0x7f2b1455e133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB client version: mclient, version 11.48.0 (hg id: 63a42c2)
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling**
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes at `BLOBcmp` | https://api.github.com/repos/MonetDB/MonetDB/issues/7380/comments | 2 | 2023-06-16T16:57:43Z | 2024-06-27T13:18:26Z | https://github.com/MonetDB/MonetDB/issues/7380 | 1,760,998,433 | 7,380 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes at `cs_bind_ubat` after executing SQL statements through ODBC.
**To Reproduce**
```sql
CREATE TABLE t2 (c1 int, t1 int, c2 int);
INSERT INTO t2 VALUES(127,255,1),(127,1,2),(-128,0,3),(-128,2,4),(-1,NULL,5);
INSERT INTO t2 VALUES(200,126,1),(250,-127,2);
INSERT INTO t2 VALUES (-128,0,1),(-1,1,1),(-2,2,2),(-3,3,3),(-4,4,4),(-5,5,5),(-6,6,6),(0,0,7),(1,1,8),(2,NULL,9),(3,NULL,10),(127,255,11);
DELETE FROM t2 WHERE c1 IN (-2, 0);
START TRANSACTION;
UPDATE t2 SET c2 = c2 + 100;
UPDATE t2 SET c2 = c2 + 100;
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f6388374871 (cs_bind_ubat+0x151)
#1 0x7f6388373483 (bind_ubat+0x43)
#2 0x7f638836d860 (bind_updates+0xe0)
#3 0x7f63882854ce (mvc_bind_wrap+0x28e)
#4 0x7f6388614c63 (runMALsequence+0x763)
#5 0x7f63886185d4 (DFLOWworker+0x2c4)
#6 0x7f6388d4fba0 (THRstarter+0x100)
#7 0x7f6388dbfcc4 (thread_starter+0x34)
#8 0x7f6388134609 (start_thread+0xd9)
#9 0x7f6388059133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB ODBC version: 11.46.0
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Issue labeling **
bug
**Additional context**
The MonetDB here runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`. | MonetDB server 11.46.0 crashes at cs_bind_ubat | https://api.github.com/repos/MonetDB/MonetDB/issues/7379/comments | 2 | 2023-06-16T16:52:13Z | 2024-06-27T13:18:25Z | https://github.com/MonetDB/MonetDB/issues/7379 | 1,760,991,161 | 7,379 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
MonetDB server crashes at sql_trans_copy_key after executing SQL statements through ODBC.
**To Reproduce**
```sql
START TRANSACTION;
CREATE TEMPORARY TABLE temptest3(col int PRIMARY KEY) ON COMMIT DROP;
CREATE TEMPORARY TABLE temptest4(col int, FOREIGN KEY (col) REFERENCES temptest3);
```
**Expected behavior**
Executing statements successfully or throwing errors, instead of breaking down the whole MonetDB server.
**Backtrace**
```
#0 0x7f9d8a205eb0 (sql_trans_copy_key+0x1c0)
#1 0x7f9d8a258c7e (mvc_copy_key+0x1e)
#2 0x7f9d8a13fa5c (create_table_or_view+0x79c)
#3 0x7f9d8a1779e1 (SQLcreate_table+0x111)
#4 0x7f9d8a4d1c63 (runMALsequence+0x763)
#5 0x7f9d8a4d131e (runMAL+0x9e)
#6 0x7f9d8a1589f9 (SQLrun+0xd9)
#7 0x7f9d8a159bee (SQLengineIntern+0x4e)
#8 0x7f9d8a1578c2 (SQLengine_+0x5e2)
#9 0x7f9d8a156343 (SQLengine+0x23)
#10 0x7f9d8a4e56cf (runScenario+0x4f)
#11 0x7f9d8a4e616c (MSscheduleClient+0x68c)
#12 0x7f9d8a58dc2b (doChallenge+0xfb)
#13 0x7f9d8ac0cba0 (THRstarter+0x100)
#14 0x7f9d8ac7ccc4 (thread_starter+0x34)
#15 0x7f9d89ff1609 (start_thread+0xd9)
#16 0x7f9d89f16133 (clone+0x43)
```
**Software versions**
- MonetDB server version: 11.46.0 (hg id: 63a42c2) (pulled from the master branch)
- MonetDB ODBC version: 11.46.0
- OS and version: ubuntu 20.04
- Self-installed and compiled. The command line of compilation: `CC=clang-12 CXX=clang++-12 cmake /root/monetdb_master -DCMAKE_BUILD_TYPE=RelWithDebInfo`
**Additional context**
MonetDB runs in-memory database. The command line of starting MonetDB server is `mserver5 --in-memory`.
| MonetDB server crashes at sql_trans_copy_key | https://api.github.com/repos/MonetDB/MonetDB/issues/7378/comments | 2 | 2023-06-16T15:58:24Z | 2024-06-27T13:18:24Z | https://github.com/MonetDB/MonetDB/issues/7378 | 1,760,900,711 | 7,378 |
[
"MonetDB",
"MonetDB"
] | **Bug Description**
There is a memory leak issue when executing a Python UDF. As the UDF runs multiple time and even though the artifacts created are deleted, the memory usage gradually increases over time.
This issue is most noticeable when running the UDF repeatedly.
**To Reproduce**
Setup the database using the database.sql.
Execute the python file leak_case.py.
Monitor the memory usage during the UDFs execution.
Observe that the memory consumption steadily increases over time.
**Expected behavior**
The memory usage during the execution of the Python UDF should remain stable, without any significant memory leaks or continuous memory growth.
**Actual Behavior**
The memory consumption gradually increases during the execution of the Python UDF, indicating the presence of a memory leak.
[leak_case.zip](https://github.com/MonetDB/MonetDB/files/11626969/leak_case.zip)
**Software versions**
MonetDB 11.45.13
Ubuntu 20.04
| Memory Leak Detected during Execution of Python UDF | https://api.github.com/repos/MonetDB/MonetDB/issues/7377/comments | 17 | 2023-06-01T15:23:50Z | 2024-06-28T07:02:54Z | https://github.com/MonetDB/MonetDB/issues/7377 | 1,736,564,160 | 7,377 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Currently, there is a concurrency issue with the Python UDFs where the second UDF execution is delayed until the first UDF completes. This behavior occurs when running a second Python UDF while the first UDF is still running. The second UDF appears to be waiting for the first UDF to finish before executing.
**To Reproduce**
Provided two files containing the UDFs.
Execute the "while_true_udf" function, which will run indefinitely.
On a separate mclient, execute the "simple_udf" query.
**Expected behavior**
The simple_udf function should be able to run independently of the while_true_udf UDF and should not wait for its completion, although it runs in a separate process.
[while_true_udf.txt](https://github.com/MonetDB/MonetDB/files/11615417/while_true_udf.txt)
[simple_udf.txt](https://github.com/MonetDB/MonetDB/files/11615418/simple_udf.txt)
**Software versions**
- MonetDB 11.45.13
- Ubuntu 20.04
| Concurrency Issue: Second Python UDF Awaits Completion of First UDF | https://api.github.com/repos/MonetDB/MonetDB/issues/7376/comments | 19 | 2023-05-31T14:45:39Z | 2024-06-27T13:18:22Z | https://github.com/MonetDB/MonetDB/issues/7376 | 1,734,399,335 | 7,376 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
Manually pivoting or unpivoting the data is a nightmare
**Describe the solution you'd like**
pivot and unpivot support, just like other databases (let's say duckdb)
**Describe alternatives you've considered**
to do it manually but that's a nightmare
**Additional context**
None | Pivot and unpivot support | https://api.github.com/repos/MonetDB/MonetDB/issues/7375/comments | 6 | 2023-05-24T07:13:24Z | 2024-06-27T13:18:21Z | https://github.com/MonetDB/MonetDB/issues/7375 | 1,723,332,152 | 7,375 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
I identified 3 cases that I think are BUGs.
Case 1: The cast alters the result.
set time zone interval '-3' hour;
select current_timestamp, cast(current_timestamp as date);
Case 2: The cast alters the result.
set time zone interval '-3' hour;
select current_time, cast(current_time as time);
Case 3: The values are different and I think they should be the same.
set time zone interval '-3' hour;
select current_date, current_timestamp;
These commands need to be executed between 23:00 and 23:30 hours to ensure that the problems will occur.
Below you can see the result:
**To Reproduce**
Read the description and see the image above.
**Expected behavior**
The results of the two columns should always be the same (same date and time returned).
**Software versions**
- MonetDB version number: 11.45.13
- OS and version: Windows 10 64 bits | Different date and time returns | https://api.github.com/repos/MonetDB/MonetDB/issues/7374/comments | 6 | 2023-05-19T18:51:11Z | 2024-06-27T13:18:20Z | https://github.com/MonetDB/MonetDB/issues/7374 | 1,717,676,854 | 7,374 |
[
"MonetDB",
"MonetDB"
] | Currently, I'm working on a project that requires me to determine the number of null values in a dataset.
I have searched through statistical tables and previous issues, but unfortunately, I haven't found any relevant information.
One possible calculation method could be taking the simple average of the column, such as (column_null_count) divided by (column_rows_count).
This is similar to the column "null_frac" in the "pg_stats" table in PostgreSQL.
Would that information be somewhere in the database? | Calculate the null percentage | https://api.github.com/repos/MonetDB/MonetDB/issues/7373/comments | 6 | 2023-05-19T14:49:33Z | 2023-06-19T13:04:41Z | https://github.com/MonetDB/MonetDB/issues/7373 | 1,717,379,188 | 7,373 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
The check for ambiguous identifiers does not seem to work consistently. In particular, its behaviour changes depending on the the number/order of joins and presence of aggregations.
**To Reproduce**
Schema:
```
create table test (a INT);
```
Ambiguous identifier `a` not identified:
```
-- a, b, c, d, e, with SUM
sql>select SUM(a) from test a, test b, test c, test d, test e;
+------+
| %1 |
+======+
| null |
+------+
1 tuple
```
Ambiguous identifier `a` correctly identified:
```
-- a, b, c, d, e (removed SUM)
sql>select a from test a, test b, test c, test d, test e;
SELECT: identifier 'a' ambiguous
-- a, c, d, e (removed b)
sql>select SUM(a) from test a, test c, test d, test e;
SELECT: identifier 'a' ambiguous
```
**Expected behavior**
Identifier `a` is semantically ambiguous in all the queries above. The ambiguity should not depend on the specific plan generated.
**Software versions**
- MonetDB version number 11.43.26
- Fedora 38
- self-installed and compiled | Inconsistent behaviour with ambiguous identifiers | https://api.github.com/repos/MonetDB/MonetDB/issues/7372/comments | 2 | 2023-05-19T09:31:07Z | 2023-06-19T19:59:42Z | https://github.com/MonetDB/MonetDB/issues/7372 | 1,716,938,012 | 7,372 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A column cannot be found for GROUP BY after a join clause with USING.
**To Reproduce**
Run these queries:
```
CREATE TABLE t0 (c0 INT);
SELECT 1 FROM t0 JOIN t0 tx USING (c0) GROUP BY t0.c0;
--error, SELECT: no such column 't0.c0'
```
**Expected behavior**
The SELECT query should run successfully, instead it cannot find the column 't0.c0'
**Software versions**
- MonetDB Jun2023
- OS and version: Ubuntu 22.04
- Self-installed and compiled
| Grouping scope issue | https://api.github.com/repos/MonetDB/MonetDB/issues/7371/comments | 4 | 2023-05-09T08:57:19Z | 2023-06-20T10:51:59Z | https://github.com/MonetDB/MonetDB/issues/7371 | 1,701,650,420 | 7,371 |
[
"MonetDB",
"MonetDB"
] | timestamp_to_str function is not outputting, defaults to server time, which is UTC.
**To Reproduce**
select timestamp_to_str(current_timestamp, '%d/%m/%Y %H:%M:%S');
**Expected behavior**
Output localtime
Kepp in mind that my time at the moment of the screenshot is 1:48 PM CEST (UTC+2) (+2 due to DST).
**Software versions**
- MonetDB default branch
- OS and version: Fedora 37
- Self-installed and compiled | timestamp_to_str function not aware of timezone | https://api.github.com/repos/MonetDB/MonetDB/issues/7370/comments | 3 | 2023-05-04T11:53:36Z | 2024-06-27T13:18:19Z | https://github.com/MonetDB/MonetDB/issues/7370 | 1,695,859,868 | 7,370 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
I just noticed that `SELECT count(*);` returns 1. It doesn't really make sense though. All DBMSs I tested give back a syntax error.
It's a pretty minor bug, I would say, though potentially misleading: I found out by forgetting a `FROM` in `SELECT count(*) FROM t;`:
```
sql>select count(*) t;
+------+
| t |
+======+
| 1 |
+------+
1 tuple
```
What happened is that `t` has become an alias to the result of `select count(*)`. Of course this was my fault, but it induced me to think that the count of `t` was 1 and only after a careful look I noticed the mistake.
Bottom line though is that `SELECT count(*);` shouldn't be allowed - I think - as a valid statement.
**To Reproduce**
```
sql>select count(*);
+------+
| %2 |
+======+
| 1 |
+------+
1 tuple
```
**Expected behavior**
Syntax error
**Software versions**
- MonetDB version number 11.43.26
- OS and version: Fedora
- self-installed and compiled
| select count(*); returns 1 | https://api.github.com/repos/MonetDB/MonetDB/issues/7369/comments | 3 | 2023-05-01T16:07:21Z | 2023-06-19T20:05:43Z | https://github.com/MonetDB/MonetDB/issues/7369 | 1,691,011,486 | 7,369 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
I'm running two instances in monetdb, and when I start my dbfarm, they sometimes go to 50001 and 50002, and other times they go to 50000 and 50001.
I don't really care for which port the instances run, but I would like to know if there is a way to find it out without trial and error. When I run monetdbd status, it always shows both instances on port 50000. And I'm using monetdb through a container
| Is there a way to find which port my instance is using? | https://api.github.com/repos/MonetDB/MonetDB/issues/7368/comments | 5 | 2023-04-29T03:35:22Z | 2023-06-19T20:07:10Z | https://github.com/MonetDB/MonetDB/issues/7368 | 1,689,345,063 | 7,368 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Not a bug, possibly an improvement in the build scripts.
I am not a `cmake` expert, but I have the impression some of the `CMakeLists.txt`s could be improved.
All the `target_link_libraries` sections use the `PRIVATE` scope keyword for all items. I think this may in some cases result in the same libraries linked more than once.
For example:
```
target_link_libraries(sql
PRIVATE
monetdb_config_header
sqlstorage
sqlcommon
sqlserver
sqlinclude
mcrypt
batstore
copybinary
monetdb5
bat)
```
could very well be:
```
target_link_libraries(sql
PRIVATE
monetdb_config_header
sqlstorage
sqlcommon
sqlserver
sqlinclude
mcrypt
batstore
copybinary
INTERFACE
monetdb5
bat)
```
How I noticed this: in my own module `spinque`, I used to have
```
target_link_libraries(spinque
PRIVATE
monetdb_config_header
mutils
bat
atoms
monetdb5)
```
This would link a second copy of `atoms` to `spinque`, resulting in `atoms` being loaded twice, which triggers `STRprelude()` twice - which fails the second time, because it tries to create a second time the bats needed for case conversion. I have actually no idea why this failure didn't happen with Jan2022.
Changing the above to
```
target_link_libraries(spinque
PRIVATE
monetdb_config_header
INTERFACE
mutils
bat
atoms
monetdb5)
```
fixed the issue, and the `spinque` library went from 2.5MB to 0.5MB (while staying fully functional).
**Software versions**
- MonetDB version number 11.47.0
- OS and version: Fedora 37
- self-installed and compiled
| Libraries linked more than once? | https://api.github.com/repos/MonetDB/MonetDB/issues/7367/comments | 3 | 2023-04-28T15:00:44Z | 2024-06-27T13:18:17Z | https://github.com/MonetDB/MonetDB/issues/7367 | 1,688,710,891 | 7,367 |
[
"MonetDB",
"MonetDB"
] | I first create a schema name test for example and create and insert some data in version 11.41.5
after that, I install 11.43.23. It occurs an error below, In this case, how can we fix it as fast as possible? :
[ERROR]: #main thread: BBPrename: !ERROR: name is in use: 'sql_seqs_val'.
[ERROR]: #main thread: mvc_init: !ERROR: Unable to create system tables
[ERROR]: #main thread: createExceptionInternal: !ERROR: SQLException:SQLinit:42000!Catalogue initialization failed
[ERROR]: #main thread: SQLprelude: !ERROR: Fatal error during initialization: SQLException:SQLinit:42000!Catalogue initialization failed | [Upgrade Error] 11.41.5 to 11.43.23 | https://api.github.com/repos/MonetDB/MonetDB/issues/7366/comments | 1 | 2023-04-10T05:45:28Z | 2023-06-19T20:08:37Z | https://github.com/MonetDB/MonetDB/issues/7366 | 1,660,270,812 | 7,366 |
[
"MonetDB",
"MonetDB"
] | the query
```sql
select * from f where f.c in (select b.c from b);
```
translates to a SEMIJOIN operator between tables `f`(left) and `b` (right)
```
project (
| semijoin (
| | table("sys"."f") [ "f"."n", "f"."c" ],
| | project (
| | | table("sys"."b") [ "b"."c" ]
| | ) [ "b"."c" as "%4"."%4" ]
| ) [ ("f"."c") any = ("%4"."%4") ]
) [ "f"."n", "f"."c" ]
```
the MAL plan though indicates a JOIN between `f` and `b` before the `leftjoin` (done by the `intersect()`)
```
function user.main():void;
X_1:void := querylog.define("explain select * from f where f.c in (select b.c from b);":str, "default_pipe":str, 26:int);
barrier X_103:bit := language.dataflow();
X_4:int := sql.mvc();
C_5:bat[:oid] := sql.tid(X_4:int, "sys":str, "f":str);
X_8:bat[:int] := sql.bind(X_4:int, "sys":str, "f":str, "n":str, 0:int);
X_15:bat[:str] := sql.bind(X_4:int, "sys":str, "f":str, "c":str, 0:int);
C_20:bat[:oid] := sql.tid(X_4:int, "sys":str, "b":str);
X_22:bat[:str] := sql.bind(X_4:int, "sys":str, "b":str, "c":str, 0:int);
X_27:bat[:str] := algebra.projection(C_20:bat[:oid], X_22:bat[:str]);
X_28:bat[:oid] := algebra.join(X_15:bat[:str], X_27:bat[:str], C_5:bat[:oid], nil:BAT, false:bit, nil:lng);
C_33:bat[:oid] := bat.mirror(X_8:bat[:int]);
C_34:bat[:oid] := algebra.intersect(C_33:bat[:oid], X_28:bat[:oid], C_5:bat[:oid], nil:BAT, false:bit, false:bit, nil:lng);
X_105:void := language.pass(C_5:bat[:oid]);
X_35:bat[:int] := algebra.projection(C_34:bat[:oid], X_8:bat[:int]);
X_106:void := language.pass(X_8:bat[:int]);
X_36:bat[:str] := algebra.projection(C_34:bat[:oid], X_15:bat[:str]);
X_107:void := language.pass(C_34:bat[:oid]);
X_108:void := language.pass(X_15:bat[:str]);
X_38:bat[:str] := bat.pack("sys.f":str, "sys.f":str);
X_39:bat[:str] := bat.pack("n":str, "c":str);
X_40:bat[:str] := bat.pack("int":str, "clob":str);
X_41:bat[:int] := bat.pack(32:int, 0:int);
X_42:bat[:int] := bat.pack(0:int, 0:int);
exit X_103:bit;
X_37:int := sql.resultSet(X_38:bat[:str], X_39:bat[:str], X_40:bat[:str], X_41:bat[:int], X_42:bat[:int], X_35:bat[:int], X_36:bat[:str]);
end user.main;
```
the `join` probably should not appear since it has a high performance cost and we do not really need it
tested on default at `b0f51c763c66` (mercurial changeset)
| semijoin query generates suboptimal mal plan | https://api.github.com/repos/MonetDB/MonetDB/issues/7365/comments | 1 | 2023-03-31T13:37:15Z | 2024-06-27T13:18:16Z | https://github.com/MonetDB/MonetDB/issues/7365 | 1,649,372,138 | 7,365 |
[
"MonetDB",
"MonetDB"
] | the GROUP BY common sub-expression elimination (CSE) optimizer is not acting upon
```
select f.n, b.n from f join b on f.n = b.n group by f.n, b.n;
```
the PLAN indicates two grouping columns even though they are going to have same values
```
project (
| group by (
| | join (
| | | table("sys"."f") [ "f"."n" ],
| | | table("sys"."b") [ "b"."n" ]
| | ) [ ("f"."n") = ("b"."n") ]
| ) [ "b"."n", "f"."n" ] [ "f"."n", "b"."n" ]
) [ "f"."n", "b"."n" ]
```
this is going to be probably tricky since the optimizer need to parse the subrelation operator's expression tree and understand the semantics
tested on `default` at `b0f51c763c66` (mercurial changeset) | missed GROUP BY optimization on JOIN with simple equality condition | https://api.github.com/repos/MonetDB/MonetDB/issues/7364/comments | 0 | 2023-03-24T17:01:56Z | 2024-06-27T13:18:15Z | https://github.com/MonetDB/MonetDB/issues/7364 | 1,639,747,917 | 7,364 |
[
"MonetDB",
"MonetDB"
] | in case that two tables are having a double alias the NATURAL JOIN seems to not eliminating the common columns e.g.
```
select * from (select n n1, n n2, c from f) as fs natural join (select n n1, n n2, c from b) as bs;
```
the PLAN output is
```
project (
| join (
| | table("sys"."f") [ "f"."n", "f"."c" ],
| | table("sys"."b") [ "b"."n", "b"."c" ]
| ) [ ("f"."n") = ("b"."n"), ("f"."n") = ("b"."n"), ("f"."c") = ("b"."c") ]
) [ "f"."n" as "fs"."n1", "f"."n" as "fs"."n2", "f"."c" as "fs"."c" ]
```
also by examining the EXPLAIN output I see the bat comparison operator `batcalc.==(<name>:bat[:int], <name>:bat[:int]);` appear twice
i was expecting the duplicate `("f"."n") = ("b"."n")` expression of the JOIN operator to be eliminated
in any case i think a double alias on the same column in both tables is a really rare case
tested on `default` at b0f51c763c66 (mercurial changeset) | optimization of join operator on tables with double aliases | https://api.github.com/repos/MonetDB/MonetDB/issues/7363/comments | 0 | 2023-03-24T16:45:04Z | 2024-06-27T13:18:14Z | https://github.com/MonetDB/MonetDB/issues/7363 | 1,639,720,971 | 7,363 |
[
"MonetDB",
"MonetDB"
] | I've previously had issues in MonetDB when shutting down the database mid-SELECT. This has previously caused corruption in the DB.
I was wondering... is there a way to gracefully cancel a SELECT query before shutting down?
If not, this also doubles as a feature request.
Best,
Seán | Is there a way to cancel and/or view running jobs in MonetDB? | https://api.github.com/repos/MonetDB/MonetDB/issues/7362/comments | 6 | 2023-03-23T12:38:29Z | 2023-08-02T21:24:01Z | https://github.com/MonetDB/MonetDB/issues/7362 | 1,637,465,989 | 7,362 |
[
"MonetDB",
"MonetDB"
] | I'm working with a database that has a few very long tables (lots of rows, only 3 columns).
I copy the CSV data for these tables into their MonetDB counterpart tables, i.e. via the MonetDB `COPY` command.
After doing this, I stop MonetDB (both the DB and the dbfarm), and then when I subsequently restart the DB, something strange happens: most of the tables are fine, but for any table with >= 2147483647 rows, the data becomes lost.
Given the proximity of 2147483647 to 2 ^ 31, I assume there is a misused 32 bit variable in the codebase.
To reproduce this bug:
```
monetdbd create overflow_dataloss_example
monetdbd start overflow_dataloss_example
monetdb create db
monetdb start db
monetdb release db
mclient db <<<"create table test_table(test_column int not null);"
mkfifo /tmp/data_pipe
mclient db <<<"copy into test_table from '/tmp/data_pipe' on client using delimiters ',', E'\n', E'\x06' no escape;" &
seq 2147483647 > /tmp/data_pipe
wait
mclient db <<<"select count(1) from test_table;"
# Should print 2147483647
monetdb stop db
monetdbd stop overflow_dataloss_example
monetdbd start overflow_dataloss_example
monetdb start db
mclient db <<<"select count(1) from test_table;"
# On my machine, this now prints 0 rather than the expected 2147483647
```
To re-iterate the "expected versus actual" behaviour: In the above example, rather than the last line printing 0, the expected behaviour would be for it to continue printing 2147483647 (i.e. no data loss).
You can repeat the experiment with one less row (214748364**6**), and you'll notice that the data is not lost in that case.
What's more, if data is loaded using a chunked approach (i.e. load in 2147483646 rows, restart the server, then repeat until all your data is loaded), then this issue does not arise. If one of those chunks passes the 2147483646 mark, however, that part of the table data is again lost after the next restart. This is somewhat encouraging because it means large tables can still be loaded in via a hacky chunked approach, but it would be nice to avoid the issue entirely, of course.
Software version: 11.45.7
I use an Intel i7 x86_64 processor, if that's relevant. | Table data is lost on DB restart, but only when a table has 2147483647 or more rows. | https://api.github.com/repos/MonetDB/MonetDB/issues/7361/comments | 1 | 2023-03-18T22:48:26Z | 2024-06-27T13:18:13Z | https://github.com/MonetDB/MonetDB/issues/7361 | 1,630,655,672 | 7,361 |
[
"MonetDB",
"MonetDB"
] | It's impossible to implement a C/C++ UDF returning a string and taking integral arguments. With aggregates things are even worse. It's impossible to implement an aggregate returning a string at all.
The following example works fine:
```sql
create or replace function my_test(stub string)
returns string
language c {
#include <stdlib.h>
result->initialize(result, stub.count);
for (int i = 0; i < stub.count; i++) {
result->data[i] = malloc(4);
result->data[i][0] = 'a';
result->data[i][1] = 'b';
result->data[i][2] = 'c';
result->data[i][3] = '\0';
}
};
select pm_test('');
```
The same code crashes if we just change the parameter type to `int`:
```sql
create or replace function my_test(stub int)
returns string
language c {
#include <stdlib.h>
result->initialize(result, stub.count);
for (int i = 0; i < stub.count; i++) {
result->data[i] = malloc(4);
result->data[i][0] = 'a';
result->data[i][1] = 'b';
result->data[i][2] = 'c';
result->data[i][3] = '\0';
}
};
select pm_test(1);
```
**Actual behaviour**
```
2023-03-12 16:34:50 ERR mydb[3386]: munmap_chunk(): invalid pointer
2023-03-12 16:34:53 MSG merovingian[3106]: database 'mydb' (-1) has crashed with signal SIGABRT (dumped core)
```
**Expected behavior**
```
+------+
| %2 |
+======+
| abc |
+------+
1 tuple
```
Now let's try an aggregate. And, ok, let it takes a string:
```sql
create or replace aggregate my_test2(stub string)
returns string
language c {
result->initialize(result, aggr_group.count);
for (int i = 0; i < aggr_group.count; i++) {
result->data[i] = malloc(4);
result->data[i][0] = 'a';
result->data[i][1] = 'b';
result->data[i][2] = 'c';
result->data[i][3] = '\0';
}
};
select my_test2('') from any_table;
```
**Actual behaviour:**
```
2023-03-12 16:40:29 MSG merovingian[3106]: database 'mydb' (-1) has crashed with signal SIGSEGV (dumped core)
```
**Expected behavior**
```
+------+
| %2 |
+======+
| abc |
+------+
1 tuple
```
**Software versions**
```
[vagrant@centos8 mydbfarm]$ mserver5 --version
MonetDB 5 server 11.45.13 (hg id: 22b3cd795d) (64-bit, 128-bit integers)
This is an unreleased version
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 7.6GiB available memory, 16 available cpu cores
Libraries:
libpcre: 8.42 2018-03-20
libxml2: 2.9.7
Compiled by: vagrant@centos8.localdomain (x86_64-pc-linux-gnu)
Compilation: /usr/bin/cc
Linking : /usr/bin/ld
```
- OS and version: Centos 8
- Compiled MonetDB from code
| Aggregates returning string crash | https://api.github.com/repos/MonetDB/MonetDB/issues/7360/comments | 13 | 2023-03-12T16:46:16Z | 2024-06-27T13:18:12Z | https://github.com/MonetDB/MonetDB/issues/7360 | 1,620,431,411 | 7,360 |
[
"MonetDB",
"MonetDB"
] | The following query takes approx 50% longer after upgrading from 11.39 to 11.45. I believe 11.41 introduced the regression but am not 100% sure as it has taken a huge amount of debugging/diagnostics to come to this point already.
``` sql
select "stack", "measures" from (
select "product_subcategory_" as "stack",
(median("line_price_") - median(- "line_price_")) / cast(2 as double) as "measures"
from "311f739f527DM_FULFile___2M__"
where (
"product_category_" = 'Health foods'
and "customer_region_" = 'ANZ' and "customer_gender_" = 'M'
and "customer_date_of_birth_" <= timestamp '1970-04-28 00:00:00.000'
and "customer_date_of_birth_" >= timestamp '1937-08-01 23:00:00.000'
)
group by "stack" order by "measures" desc, "stack" asc limit 101
) as "q"
order by "stack" asc, "measures" desc;
```
This is being executed on 2 million rows of "line item" (standardised/generated) data.
Diffing the TRACE outputs highlights the differences below. (Note there is a marked difference between running immediately after creating data, and subsequently restarting mserver5 then running the query on already-existing data. In each of the 4 cases below I ran the trace query several times for numbers to stabilise.)
### 11.39
```
| 28806 | C_60=[243537]:bat[:oid] := algebra.thetaselect(X_31=[2000000]:bat[:str], C_54=[1143152]:bat[:oid], "Health foods":str, "==":str); # hashselect |
| 344 | C_64=[670]:bat[:oid] := algebra.thetaselect(X_19=[2000000]:bat[:str], C_60=[243537]:bat[:oid], "ANZ":str, "==":str); # hashselect |
| 254 | C_67=[381]:bat[:oid] := algebra.thetaselect(X_10=[2000000]:bat[:str], C_64=[670]:bat[:oid], "M":str, "==":str); # select: fullscan equi strelim |
```
_Here, restarting mserver5 makes no difference; it's around 30ms to apply these 3 string filters. The Gender field consistently uses `fullscan`._
### 11.45
#### (a) immediately after inserting
```
| 5640 | C_59=[243537]:bat[:oid] := algebra.thetaselect(X_29=[2000000]:bat[:str], C_53=[1143152]:bat[:oid], "Health foods":str, "==":str); # select: fullscan equi strelim |
| 841 | C_63=[670]:bat[:oid] := algebra.thetaselect(X_17=[2000000]:bat[:str], C_59=[243537]:bat[:oid], "ANZ":str, "==":str); # select: fullscan equi strelim |
| 41 | C_66=[381]:bat[:oid] := algebra.thetaselect(X_10=[2000000]:bat[:str], C_63=[670]:bat[:oid], "M":str, "==":str); # select: fullscan equi strelim |
```
#### (b) after restarting mserver5
```
| 31381 | C_59=[243537]:bat[:oid] := algebra.thetaselect(X_29=[2000000]:bat[:str], C_53=[1143152]:bat[:oid], "Health foods":str, "==":str); # hashselect on parent |
| 368 | C_63=[670]:bat[:oid] := algebra.thetaselect(X_17=[2000000]:bat[:str], C_59=[243537]:bat[:oid], "ANZ":str, "==":str); # hashselect on parent |
| 28199 | C_66=[381]:bat[:oid] := algebra.thetaselect(X_10=[2000000]:bat[:str], C_63=[670]:bat[:oid], "M":str, "==":str); # hashselect on parent |
```
_Before restarting, it's actually faster than 11.39, around 16ms. **But**, after restarting, it's twice as slow at around 60ms, consistently. The Gender field is now consistently using `hashselect` in the new version post-restart._
I believe this is down to the change introduced in
https://github.com/MonetDB/MonetDB/commit/c3ef00e6d24d9dc37a49124ac6c25493aae755a2 with the wanthash/needhash logic in gdk_select.c, but I'm not sure. I'm trying to find a way to trick Monetdb to always use fullscan as per the older version, without luck. I've tried playing with `mserver5 --set no_hash_select_fraction=1` arg (and others) to no effect. | 50% performance degradation from 11.39 to 11.41 | https://api.github.com/repos/MonetDB/MonetDB/issues/7359/comments | 2 | 2023-02-23T14:44:12Z | 2024-06-27T13:18:11Z | https://github.com/MonetDB/MonetDB/issues/7359 | 1,596,993,661 | 7,359 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
upcon connection to server recieving "Server challenge string unusable! It contains too few (1) tokens: "
**To Reproduce**
final String dbUrl = "jdbc:monetdb://vuatmdb:50000/trg?so_timeout=10000";
final String userName = "monetdb";
final String password = "xxxxx";
Class.forName("org.monetdb.jdbc.MonetDriver");
Connection conn = DriverManager.getConnection(dbUrl, userName, password);
java.sql.SQLNonTransientConnectionException: Server challenge string unusable! It contains too few (1) tokens:
at org.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:354)
at org.monetdb.jdbc.MonetDriver.connect(MonetDriver.java:152)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247
**Expected behavior**
to get a valid connection
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Software versions**
MonetDB 5 server v11.45.13 (Sep2022-SP2)
centos 3.10.0-1160.83.1.el7.x86_64
**Issue labeling **
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
Add any other context about the problem here.
| updated MonetDB jdbc driver version 3.2 (Liberica 20230221) cant connect to server | https://api.github.com/repos/MonetDB/MonetDB/issues/7358/comments | 12 | 2023-02-21T14:09:17Z | 2023-02-22T14:40:53Z | https://github.com/MonetDB/MonetDB/issues/7358 | 1,593,552,845 | 7,358 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Running a simple cycle of queries (create, select, drop) makes MonetDB consume a lot of memory and when it reaches it's limit it starts throwing exceptions.
**To Reproduce**
I am assigning `vmmaxsize=2000000` but I don't think this is required.
Then I run the following script:
```
from time import sleep
import pymonetdb
def get_sql_queries():
return [
"DROP VIEW IF EXISTS temp_view1;",
"DROP VIEW IF EXISTS temp_view2;",
"DROP TABLE IF EXISTS temp; ",
"CREATE TABLE IF NOT EXISTS temp (c1 INT, c2 INT, c3 INT);",
"INSERT INTO temp (c1, c2, c3) VALUES (1, 2, 3),(1,2,3); ",
"CREATE OR REPLACE VIEW temp_view1 AS SELECT c1, c2, c3 FROM temp;"
"CREATE OR REPLACE VIEW temp_view2 AS SELECT c1, c2, c3 FROM temp;"
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"INSERT INTO temp SELECT * FROM temp_view1;",
"SELECT * FROM temp_view1, temp_view2;"
"DROP VIEW IF EXISTS temp_view1;",
"DROP VIEW IF EXISTS temp_view2;",
"DROP TABLE IF EXISTS temp; ",
]
def create_connection():
return pymonetdb.connect(
hostname="localhost",
port="50000",
username="monetdb",
password="monetdb",
database="db",
)
def execute_query(_connection, query):
cur = _connection.cursor()
cur.execute(query)
cur.close()
_connection.commit()
def execute_query_loop():
connection = create_connection()
for i in range(1000):
try:
for query in get_sql_queries():
execute_query(connection, query)
print(f"Done! {i}")
except (BrokenPipeError) as exc:
connection = create_connection()
print(exc)
sleep(1)
except Exception as exc:
print(exc)
if connection:
connection.rollback()
sleep(1)
connection.close()
if __name__ == '__main__':
execute_query_loop()
```
**Expected behavior**
Since the queries are actually a cycle leaving no tables behind I would expect that these queries could run in a never ending cycle.
**Software versions**
- MonetDB version number `Sep2022-SP2 Bugfix Release (11.45.13)`
- OS and version: Ubuntu 20.04
- Installed from release package
| Cyclic queries (create, select, drop) exhausting memory and throwing errors | https://api.github.com/repos/MonetDB/MonetDB/issues/7357/comments | 8 | 2023-02-10T13:00:24Z | 2024-07-13T13:30:07Z | https://github.com/MonetDB/MonetDB/issues/7357 | 1,579,646,991 | 7,357 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Cann't create a table which has a column name starts with %
**To Reproduce**
CREATE TABLE wyn.newtable24 ("% of Completion" varchar(100));
**Expected behavior**
create table successfully.
**Screenshots**
**Software versions**
v11.45.13
windows 10
| Cann't create a table which has a column name starts with % | https://api.github.com/repos/MonetDB/MonetDB/issues/7356/comments | 3 | 2023-02-02T08:51:29Z | 2024-06-27T13:18:09Z | https://github.com/MonetDB/MonetDB/issues/7356 | 1,567,594,569 | 7,356 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
I have 62 databases running in a docker container.
When using `monetdb status`, everything works fine.
When using `monetdb -h <host> -p <port> -P <passphrase> status` (pointing at localhost), 11 out of those 62 databases are not listed. For all the others, there is no difference.
I couldn't find anything different in the missing databases' metadata.
When using the host explicitly on one of the problematic databases, I get a warning, for example:
```
# monetdb status demo06_default01
name state health remarks
demo06_default01 R 1d 55% 3d mapi:monetdb://d06bc7103e02:50000/demo06_default01
# monetdb -h localhost -p 50000 -P <passphrase> status demo06_default01
WARNING: failed to parse response from monetdbd: string does not contain scenarios: (null)
status: no such database: demo06_default01
```
With others databases I get different warnings: `string does not contain uri`, or `should not happen`.
**Software versions**
- MonetDB v11.43.26
- OS and version: Fedora 35
- self-installed and compiled | monetdb - monetdbd communication behaves strange when using -h <host> | https://api.github.com/repos/MonetDB/MonetDB/issues/7355/comments | 3 | 2023-02-01T12:02:42Z | 2023-02-01T16:49:26Z | https://github.com/MonetDB/MonetDB/issues/7355 | 1,565,987,449 | 7,355 |
[
"MonetDB",
"MonetDB"
] | build: debug x64 windows from the current master branch
Running (say) example1 in the debugger results in an indefinite hang.
It is triggered by the lock owner check when in DEBUG mode:
#define LOCK_OWNER 1
I have traced the hang to the call/expansion of MT_lock_unset (MT_thread_del_mylock) made in BBPinsert per below:
gdk_bpp.c
` i = BBP_free;
assert(i > 0);
BBP_free = BBP_next(i);
if (lock) {
MT_lock_unset(&GDKcacheLock); // hanging
}
/* rest of the work outside the lock */
/* fill in basic BBP fields for the new bat */
bn->batCacheid = i;
bn->creator_tid = pid;
`
MT_thread_del_mylock:
...
`
for (MT_Lock *l = w->mylocks; l; l = l->nxt) {
if (l->nxt == lock) {
l->nxt = lock->nxt;
break;
}
}
`
...
| MT_thread_del_mylock hanging in debug mode (win x64) | https://api.github.com/repos/MonetDB/MonetDB/issues/7354/comments | 3 | 2023-01-31T22:48:51Z | 2023-02-01T16:44:31Z | https://github.com/MonetDB/MonetDB/issues/7354 | 1,565,110,107 | 7,354 |
[
"MonetDB",
"MonetDB"
] | Consider the following query
```
SELECT
value AS v,
CAST(CAST(value AS TEXT) AS INTERVAL HOUR) AS h,
CAST(CAST(value AS TEXT) AS INTERVAL SECOND) AS s
FROM sys.generate_series(1, 2);
```
I would expect the following result:
```
+------+----------+-------+
| v | h | s |
+======+==========+=======+
| 1 | 3600.000 | 1.000 |
+------+----------+-------+
```
But I get
```
+------+----------+----------+
| v | h | s |
+======+==========+==========+
| 1 | 3600.000 | 3600.000 |
+------+----------+----------+
```
As you can see the 3600.000 gets duplicated from the h column to the s column.
Looking in the EXPLAIN output I notice
```
X_12:bat[:lng] := batcalc.second_interval(X_10:bat[:str], nil:BAT, 8:int, 0:int);
. . .
X_15:int := sql.resultSet( . . ., X_9:bat[:bte], X_12:bat[:lng], X_12:bat[:lng]);
^^^^ ^^^^
```
The result of a single batcalc.second_interval() call gets reused for both columns. I quickly checked opt_CommonTerms.c but at first glance the damage already seemed to be done by the time we got there.
**Software versions**
MonetDB commit c56826b78db5d53b36ea62d4c0d6f11dcecbc9e9 on the Sep2022 branch. Running under Debian11 (bullseye).
| INTERVAL SECOND columns become incorrect when an INTERVAL HOUR column is present | https://api.github.com/repos/MonetDB/MonetDB/issues/7353/comments | 3 | 2023-01-27T12:52:13Z | 2024-07-08T15:37:48Z | https://github.com/MonetDB/MonetDB/issues/7353 | 1,559,721,694 | 7,353 |
[
"MonetDB",
"MonetDB"
] | In postgresql, when I need to get the schema of a database usually I use the pg_dump with the flag --schema-only to generate a short .sql file.
I searched but couldn't find anything like in monetdb and I think it wound be very usefull. | Dump only the schema of the database | https://api.github.com/repos/MonetDB/MonetDB/issues/7352/comments | 2 | 2023-01-25T13:42:00Z | 2023-01-25T13:48:50Z | https://github.com/MonetDB/MonetDB/issues/7352 | 1,556,680,813 | 7,352 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
After MonetDB reaches its specified limit in memory it is restarted by the daemon and gets into a corrupted unrecoverable state.
We use MonetDB containerized. In order for MonetDB not to use unlimited memory, we limit it with `memory-reservation` of docker.
We run queries through a "db_handler" and in case a query fails with `pymonetdb.Exceptions.Error`, we rerun it a specific amount of times. When we stress MonetDB, at some point the max limit of the memory is reached and the database restarts.
In most cases this works and the query succeeds after MonetDB gets back up and running but in some cases it gets into a corrupted state.
The problem is that in some cases the monetdb will not recover properly and a specific error will prevent any further query from being executed.
Error: monetdbd: internal error while starting mserver 'database 'db' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details'.
The logs that show the problem:
```
2023-01-19 13:14:13 ERR db[1903]: #logmanager: logbat_new: CRITICAL: creating new BAT[void:int]#19250 failed
2023-01-19 13:14:13 ERR db[1903]: #logmanager: GDKmmap: ERROR: requested too much virtual memory; memory requested: 131072, memory in use: 510246968, virtual memory in use: 629129272
2023-01-19 13:14:13 ERR db[1903]: #logmanager: HEAPalloc: ERROR: Insufficient space for HEAP of 77824 bytes.
2023-01-19 13:14:13 ERR db[1903]: #logmanager: logbat_new: CRITICAL: creating new BAT[void:int]#19250 failed
2023-01-19 13:14:13 ERR db[1903]: #logmanager: GDKmmap: ERROR: requested too much virtual memory; memory requested: 196608, memory in use: 510246968, virtual memory in use: 629129272
2023-01-19 13:14:13 ERR db[1903]: #logmanager: HEAPalloc: ERROR: Insufficient space for HEAP of 155648 bytes.
2023-01-19 13:14:13 ERR db[1903]: #logmanager: logbat_new: CRITICAL: creating new BAT[void:lng]#19250 failed
2023-01-19 13:14:13 ERR db[1903]: #logmanager: GDKmmap: ERROR: requested too much virtual memory; memory requested: 196608, memory in use: 510246968, virtual memory in use: 629129272
2023-01-19 13:14:13 ERR db[1903]: #logmanager: HEAPalloc: ERROR: Insufficient space for HEAP of 155648 bytes.
2023-01-19 13:14:13 ERR db[1903]: #logmanager: logbat_new: CRITICAL: creating new BAT[void:lng]#19250 failed
2023-01-19 13:14:38 ERR db[1903]: #client957: GDKmmap: ERROR: requested too much virtual memory; memory requested: 65536, memory in use: 510395816, virtual memory in use: 629081512
2023-01-19 13:14:38 ERR db[1903]: #client957: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client965: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client960: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client965: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client965: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client960: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client965: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client962: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client962: createExceptionInternal: ERROR: MALException:optmizer.remap:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client962: createExceptionInternal: ERROR: MALException:remap:42000!Error in optimizer remap: MALException:optmizer.remap:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client962: createExceptionInternal: ERROR: MALException:remap:42000!Error in optimizer remap: MALException:optmizer.remap:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client959: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client959: createExceptionInternal: ERROR: MALException:optimizer.addOptimizerPipe:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client977: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client957: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client977: createExceptionInternal: ERROR: MALException:optimizer.addOptimizerPipe:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client997: GDKmmap: ERROR: requested too much virtual memory; memory requested: 65536, memory in use: 510403312, virtual memory in use: 629089008
2023-01-19 13:14:38 ERR db[1903]: #client997: GDKmmap: ERROR: requested too much virtual memory; memory requested: 65536, memory in use: 510410872, virtual memory in use: 629096568
2023-01-19 13:14:38 ERR db[1903]: #client997: createExceptionInternal: ERROR: SQLException:sql.initClient:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client998: GDKmmap: ERROR: requested too much virtual memory; memory requested: 65536, memory in use: 510409696, virtual memory in use: 629095392
2023-01-19 13:14:38 ERR db[1903]: #client998: createExceptionInternal: ERROR: SQLException:sql.initClient:HY013!Could not allocate space
2023-01-19 13:14:38 ERR db[1903]: #client978: GDKmalloc_internal: ERROR: allocating too much memory
2023-01-19 13:14:38 ERR db[1903]: #client978: createExceptionInternal: ERROR: MALException:initClientPrg:HY013!Could not allocate space
2023-01-19 13:14:39 MSG merovingian[10]: database 'db' (-1) has crashed with signal SIGSEGV (dumped core)
2023-01-19 13:14:39 MSG merovingian[10]: database 'db' has crashed after start on 2023-01-19 13:11:41, attempting restart, up min/avg/max: 31s/59s/1m, crash average: 1.00 0.90 0.87 (36-4=32)
```
**To Reproduce**
It's a bit hard to reproduce since it does not happen often.
But you can reproduce it by lowering the database memory limit and stress it with a lot of queries.
Once the memory limit is reached, most of the time the Daemon will properly restart the database but in some cases it ends up in a corrupted state.
**Corrupted DB**
[corruptedac.backup.tar.gz](https://github.com/MonetDB/MonetDB/files/10466205/corruptedac.backup.tar.gz)
[corruptedab.backup.tar.gz](https://github.com/MonetDB/MonetDB/files/10466209/corruptedab.backup.tar.gz)
[corruptedaa.backup.tar.gz](https://github.com/MonetDB/MonetDB/files/10466215/corruptedaa.backup.tar.gz)
**Expected behavior**
MonetDB should be able to recover after the max memory capacity has been reached.
**Software versions**
MonetDB version number 11.45.11
OS and version: Ubuntu 22.04
Using a [docker image](https://github.com/madgik/MIP-Engine/blob/master/monetdb/Dockerfile), compiling the source. | MonetDB gets in a corrupted state after memory limit exceptions. | https://api.github.com/repos/MonetDB/MonetDB/issues/7351/comments | 10 | 2023-01-19T14:34:15Z | 2023-10-28T09:38:46Z | https://github.com/MonetDB/MonetDB/issues/7351 | 1,549,284,813 | 7,351 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Setup:
1) MonetDB is inside a docker container with a `memory-reservation` limit (if memory exceeds the limit, the process is killed).
2) There are 2 types of queries running in parallel.
- A query creating a table.
- Some queries that require a lot of memory.
The events leading to the error are the following:
1) A query starts running increasing the monetdb memory consumption.
2) A `CREATE TABLE` query starts running.
3) Another query runs requesting more memory and docker, following the `memory-reservation` policy, kills the process.
4) The client that executed the `CREATE TABLE` query receives a `BrokenPipeError` with message `Server closed connection`.
5) The monetdbd restarts monetdb.
6) The client tries executing the `CREATE TABLE` query again and receives a `Table already exists` error, even though the previous query didn't succeed.
Is this an expected behavior? To receive a `BrokenPipeError` even though the table was created?
| Create table returns "BrokenPipeError" but table is created. | https://api.github.com/repos/MonetDB/MonetDB/issues/7350/comments | 1 | 2023-01-10T17:47:43Z | 2023-01-11T12:11:16Z | https://github.com/MonetDB/MonetDB/issues/7350 | 1,527,783,485 | 7,350 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Disk space of dropped tables is only released when no transaction exists, no matter when the transactions were started or what they do.
**To Reproduce**
With an empty DB, open 3 mclient sessions, and somewhere else keep a `watch du -sh <dbfolder>`.
Reproduce the following sequence:
| sequence | Session 1 | Session 2 | Session 3 | `du -sh <dbfolder>` (after command) |
| ---- | --------- | --------- | --------- | --------- |
| 0 | | | | 4K |
| 1 | `create table t as select * from generate_series(1, 10 * 1000 * 1000);` | | | 45M |
| 2 | | `start transaction`; | | 45M |
| 3 | `drop table t`; | | | 45M |
| 4 | | | `start transaction;` | 45M |
| 5 | | `rollback;` | | 45M |
| 6 | | | `rollback;` | 4K |
The `rollback` at time 5 should allow disk space to be released, because the only transaction that starts before the `DROP TABLE t` ends. I waited for very long after issuing the `rollback`, but nothing happened.
Instead, disk space is released only when NO transactions exist, i.e. at time 6 (after few seconds from the `rollback`).
Note: If you keep opening a new transaction before the last active one ends, thus never leaving a moment with no transactions active, then disk space from table `t` is never released.
**Expected behavior**
Disk space is released after the `rollback` at time 5.
**Software versions**
- MonetDB version number 11.43.14
- OS and version: Fedora 37
- self-installed and compiled
| Disk space not released unless NO transaction exists | https://api.github.com/repos/MonetDB/MonetDB/issues/7349/comments | 6 | 2022-12-30T13:01:49Z | 2023-06-05T06:51:52Z | https://github.com/MonetDB/MonetDB/issues/7349 | 1,514,507,675 | 7,349 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Hello everyone! A small optimization opportunity is missing here. In a case statement with an uncorrelated subquery, the subquery is being always evaluated when it shouldn't.
**To Reproduce**
Run the statements:
```
CREATE TABLE t0 (c0 BOOLEAN);
INSERT INTO t0(c0) VALUES (FALSE),(TRUE),(FALSE),(FALSE),(TRUE),(FALSE);
SELECT (CASE 0.0 WHEN 1.0 THEN (SELECT 1.0 FROM t0) END) FROM t0;
```
The SELECT query will trigger:
GDK reported error: BATsubcross: more than one match
**Expected behavior**
The subquery shouldn't be evaluated in this case and the query should output 6 NULL rows.
**Software versions**
- MonetDB version number Sep2022
- OS and version: Ubuntu 22.04
- Installed from release package or self-installed and compiled
| Subquery inside case always evaluated | https://api.github.com/repos/MonetDB/MonetDB/issues/7348/comments | 3 | 2022-12-23T11:41:00Z | 2024-06-27T13:18:06Z | https://github.com/MonetDB/MonetDB/issues/7348 | 1,509,248,319 | 7,348 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
An error occurs in the case of a merge table that contain remote tables. When executing a select query with the same column name and alias
**Server environment and version**
beestore server (server accessing remote table)
- MonetDB 5 server 11.45.11 (Sep2022-SP1) (64-bit, 128-bit integers)
beestore1 server (server serving remote table)
- MonetDB 5 server 11.45.11 (Sep2022-SP1) (64-bit, 128-bit integers)
**To Reproduce**
1. DDL in beestore1 server
sql>
-- Create local table
CREATE TABLE alias_test (
dest String null,
dep_delay int null,
arr_delay String null
);
sql>
-- insert sample data
insert into alias_test values('AA', 20,5);
insert into alias_test values('AB', 30,6);
insert into alias_test values('AC', 40,7);
sql>
select
dest as category,
dep_delay as dep_delay,
arr_delay as arr_delay
from alias_test
order by dest desc limit 1
_There is no error._
2. DDL in beestore server
sql>
-- Create remote table
create remote TABLE alias_test (
dest String null,
dep_delay int null,
arr_delay String null
) on 'mapi:monetdb://beestore1:50000/bcsdb';
sql>
-- insert sample data
insert into alias_test values('AA', 20,5);
insert into alias_test values('AB', 30,6);
insert into alias_test values('AC', 40,7);
sql>
-- Checking the inserted data from remote table (same as above)
select
dest as category,
dep_delay as dep_delay,
arr_delay as arr_delay
from alias_test
order by dest desc limit 1
error occurred
> Error: Exception occurred in the remote server, please check the log there
> SQLState: 22000
> ErrorCode: 0
here is the merovingian.log
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker1004: createExceptionInternal: ERROR: SQLException:remote.exec:(mapi:monetdb://monetdb@beestore2/bcsdb0) Identifier dep_delay doesn't exist
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker994: createExceptionInternal: ERROR: SQLException:remote.exec:(mapi:monetdb://monetdb@beestore3/bcsdb0) Identifier dep_delay doesn't exist
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker995: createExceptionInternal: ERROR: SQLException:remote.exec:(mapi:monetdb://monetdb@beestore1/bcsdb0) Identifier dep_delay doesn't exist
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker994: createExceptionInternal: ERROR: MALException:user.%3[37]:Exception occurred in the remote server, please check the log there
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker1004: createExceptionInternal: ERROR: MALException:user.%2[37]:Exception occurred in the remote server, please check the log there
> 2022-12-21 15:32:21 ERR bcsdb[40441]: #DFLOWworker995: createExceptionInternal: ERROR: MALException:user.%1[37]:Exception occurred in the remote server, please check the log there
>
but,If the column name and alias are different, no error occurs.
select
dest as category,
dep_delay as dep_delay_diff,
arr_delay as arr_delay_diff
from alias_test
order by dest desc limit 1
**Expected behavior**
I would expect there is no error even if the column name and alias are the same in the merge table.
**Software versions**
- MonetDB 11.45.11
- OS and version:CentOS Linux release 7.4.1708
- Installed from release package or self-installed and compiled : both
| A bug where an exception occurs even though it is a query with normal syntax (Merge Table) | https://api.github.com/repos/MonetDB/MonetDB/issues/7347/comments | 1 | 2022-12-22T01:17:04Z | 2024-06-27T13:18:05Z | https://github.com/MonetDB/MonetDB/issues/7347 | 1,507,113,565 | 7,347 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
We got the following error, when executing SELECT col_1 FROM table; Where col_1 is BLOB
other tabels with BLOB columns working fine.
Select other columns of that table is working fine, too.
Error: protocol violation: unexpected line in data block: !45000!Result set construction failed: Could not allocate space
SQLState: M0M10
ErrorCode: 0
**To Reproduce**
tried with JDBC driver 2.29 and 3.2
I installed 11.45.11 just yesterday. updated from (11.45.7)
**Expected behavior**
no SQL exception
**Screenshots**
**Software versions**
- MonetDB version number 11.45.11
- OS and version: Ubuntu 20]
- Installed from release package
**Issue labeling **
**Additional context**
| JDBC ERROR: Could not allocate space SQLState: M0M10 | https://api.github.com/repos/MonetDB/MonetDB/issues/7346/comments | 8 | 2022-12-16T15:22:17Z | 2024-06-27T13:18:04Z | https://github.com/MonetDB/MonetDB/issues/7346 | 1,500,414,019 | 7,346 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A Path Traversal I found while google dorking the following
inurl: index of /logs/
montedb showed up in it and it lead me to the following
https://www.monetdb.org/testweb/logs/86808:219c3300d4b9/
if we go back to " /testweb/"
it takes us here
https://www.monetdb.org/testweb/web/status.php
if we view the source of that page we are lead to here
https://www.monetdb.org/testweb/logs/87291:1a90a1b5b1b4/MdoServer
Below are the containments of the above page
Begin code
# 2022-12-13 21:33:44 -- /export/scratch1/home/monet/testweb/logs/2022-12-13_21:33/MdoServer
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 1.8T 402G 1.3T 24% /export/scratch1
~/testweb/source/monetdb-java ~/testweb/TestTools
updating the sources for monetdb-java
pulling from https://www.monetdb.org/hg/monetdb-java/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-java sources updated to revision 21fd1eebbd0e
~/testweb/source/monetdb-perl ~/testweb/TestTools
updating the sources for monetdb-perl
pulling from https://www.monetdb.org/hg/monetdb-perl/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-perl sources updated to revision 7a8311219f2f
~/testweb/source/monetdb-php ~/testweb/TestTools
updating the sources for monetdb-php
pulling from https://www.monetdb.org/hg/monetdb-php/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-php sources updated to revision 9de229e8cb8d
~/testweb/source/monetdb-ruby ~/testweb/TestTools
updating the sources for monetdb-ruby
pulling from https://www.monetdb.org/hg/monetdb-ruby/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-ruby sources updated to revision c2070750ad20
~/testweb/source/monetdb-test-data ~/testweb/TestTools
updating the sources for monetdb-test-data
pulling from https://www.monetdb.org/hgtt/monetdb-test-data/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-test-data sources updated to revision 855b4c5aa368
~/testweb/source/monetdb-external-tests ~/testweb/TestTools
updating the sources for monetdb-external-tests
pulling from https://www.monetdb.org/hgtt/monetdb-external-tests/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-external-tests sources updated to revision 1c488a273181
~/testweb/source/MonetDB ~/testweb/TestTools
updating the sources for MonetDB, switching to default
pulling from https://www.monetdb.org/hg/MonetDB/
searching for changes
no changes found
1907 files updated, 0 files merged, 445 files removed, 0 files unresolved
MonetDB sources updated to revision 1a90a1b5b1b4
finding previous run for branch default
previous run was: 87263:a1628f8fbfb3
# 2022-12-13 21:34:50 == changing logdir from /export/scratch1/home/monet/testweb/logs/2022-12-13_21:33 to /export/scratch1/home/monet/testweb/logs/87291:1a90a1b5b1b4, delta time: 66s
storing incoming commits
~/testweb/source/MonetDB ~/testweb/TestTools
moving sources into staging area
creating MonetDB-1a90a1b5b1b4.tar.bz2
creating monetdb-java-21fd1eebbd0e.tar.bz2
creating monetdb-test-data-855b4c5aa368.tar.bz2
creating monetdb-external-tests-1c488a273181.tar.bz2
creating TestTools-ed509f4dfbd8.tar.bz2
# 2022-12-13 21:35:14 == gathering workers, delta time: 24s
in directory /export/scratch1/home/monet/testweb/TestTools/config/workers:
lab01 (config/workers/lab01.da.cwi.nl)
lab03 (config/workers/lab03.ins.cwi.nl)
lab04 (config/workers/lab04.da.cwi.nl)
lab05 (config/workers/lab05.da.cwi.nl)
lab05 is disabled by configuration
lab06 (config/workers/lab06.da.cwi.nl)
macmini (config/workers/mac-mini.scilens.private)
power8 (config/workers/power8.scilens.private)
win2k22 (config/workers/win2k22.virt.private)
# 2022-12-13 21:35:14 == gathering targets, delta time: 0s
processing target: Int-Fedora-x86_64-assert-propcheck
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-dbfarm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-sanitize
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-undefined
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-nowal
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-assert-debug=65536
found worker: lab01
found worker: lab04
found worker: lab06
processing target: Cla-Fedora-x86_64
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-notint128-dbfarm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=1-assert
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=1-propcheck
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=32-propcheck-rpm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-powerpc64-thrs=8-assert-propcheck-dbfarm
found worker: power8
processing target: GNU-Fedora-powerpc64-thrs=8-notint128-assert-propcheck-dbfarm
found worker: power8
processing target: Cla-Darwin-x86_64
found worker: macmini
processing target: Cla-Darwin-x86_64-assert-propcheck
found worker: macmini
processing target: Mic-Windows7-x86_64-assert-propcheck
found worker: lab03
processing target: Mic-Windows2022-i386-installer-notest
found worker: win2k22
processing target: Mic-Windows2022-i386-assert-propcheck
found worker: win2k22
processing target: Mic-Windows2022-x86_64-installer
found worker: win2k22
# 2022-12-13 21:35:14 == final workqueues for workers, delta time: 0s
(final execution based on workers themselves):
lab01: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
lab03: Mic-Windows7-x86_64-assert-propcheck
lab04: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
lab06: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
macmini: Cla-Darwin-x86_64 Cla-Darwin-x86_64-assert-propcheck
power8: GNU-Fedora-powerpc64-thrs=8-assert-propcheck-dbfarm GNU-Fedora-powerpc64-thrs=8-notint128-assert-propcheck-dbfarm
win2k22: Mic-Windows2022-i386-installer-notest Mic-Windows2022-i386-assert-propcheck Mic-Windows2022-x86_64-installer
# 2022-12-13 23:57:52 == all workers finished, delta time: 8558s
# 2022-12-13 23:57:53 -- /export/scratch1/home/monet/testweb/logs/87291:1a90a1b5b1b4/MdoServer, elapsed time: 8649s | Critical Path Traversal | https://api.github.com/repos/MonetDB/MonetDB/issues/7345/comments | 4 | 2022-12-14T08:55:40Z | 2022-12-15T09:53:41Z | https://github.com/MonetDB/MonetDB/issues/7345 | 1,496,101,802 | 7,345 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
When a database contains user objects (such as procedures/functions/views) which references system objects which need to be replaced (via DROP and CREATE) during an upgrade of a database (e.g. from Jan2022 to Sep2022) than the upgrade process fails. The database is not completely upgraded, resulting in an inconsistent db state. It appears the database can not be used anymore, server fails to startup.
**To Reproduce**
1) create an empty Jan2022 SP5 database.
2) via mclient execute sql:
create procedure sys.dump_table_data(sch string)
begin
declare sid int;
set sid = (select min(id) from sys.schemas where name = sch);
if sid is not null then
declare i int;
set i = (select min(t.id) from sys.tables t, sys.table_types ts where t.type = ts.table_type_id and ts.table_type_name = 'TABLE' and not t.system and t.schema_id = sid);
if i is not null then
declare m int;
set m = (select max(t.id) from sys.tables t, sys.table_types ts where t.type = ts.table_type_id and ts.table_type_name = 'TABLE' and not t.system and t.schema_id = sid);
declare tbl string;
while i is not null and i <= m do
set tbl = (select t.name from sys.tables t where t.schema_id = sid and t.id = i);
call sys.dump_table_data(sch, tbl);
set i = (select min(t.id) from sys.tables t, sys.table_types ts where t.type = ts.table_type_id and ts.table_type_name = 'TABLE' and not t.system and t.schema_id = sid and t.id > i);
end while;
end if;
end if;
end;
This procedure calls sys.dump_table_data(sch, tbl); so adds an extra dependency.
3) stop Jan2022 SP5 server
4) upgrade MonetDB server code to Sep2022
5) start this db with Sep2022 server. It will automatically start the upgrade code.
In the console or merovingian log you will get following upgrade errors:
#2022-11-30 20:12:57: main thread: createExceptionInternal: ERROR: SQLException:sql.drop_func:42000!DROP PROCEDURE: there are database objects dependent on procedure dump_table_data;
#2022-11-30 20:12:57: main thread: SQLupgrades: CRITICAL: SQLException:sql.drop_func:42000!DROP PROCEDURE: there are database objects dependent on procedure dump_table_data;
It will not be possible to connect to the server.
Also stopping and restarting the server will fail (due to inconsistent database state).
**Expected behavior**
1) the database should NOT be left in a state that it cannot be started.
2) the upgrade code should detect and report that user objects exist which prevented the upgrade of system objects. If possible dump the user objects (and cascading dependent objects) to an .sql file, so it can be re-executed after the database upgrade.
3) the upgrade code should use CASCADE for all the DROP PROCEDURE / FUNCTION / VIEW / ... commands, such that upgrades are always completed. This however does mean that some user objects will need to be removed during the upgrade process.
4) Ideally those removed user objects (as part of executing the CASCADE) should be recreated after the upgrade has been completed. Potentially the saved .sql dump file can be used for that.
**Software versions**
- MonetDB 11.43.23 Jan2022 SP5 and MonetDB 11.45.9 Sep2022 SP1
- OS and version: Fedora 37, x86_64-pc-linux-gnu/64bit with 128bit integers
- self-installed and compiled
| Database upgrade failure due to user object dependency on system procedure | https://api.github.com/repos/MonetDB/MonetDB/issues/7344/comments | 1 | 2022-12-01T15:38:34Z | 2024-06-27T13:18:03Z | https://github.com/MonetDB/MonetDB/issues/7344 | 1,471,529,749 | 7,344 |
[
"MonetDB",
"MonetDB"
] | I'm getting the following:
```
2022-11-23 13:27:30 ERR default01[35]: #client1540: MT_mmap: !ERROR: mmap(/var/lib/monetdb/dbfarm/default01/bat/pymmap4.tmp,0) failed: Invalid argument
2022-11-23 13:27:30 ERR default01[35]: #client1540: GDKmmap: !ERROR: requesting virtual memory failed; memory requested: 0, memory in use: 674098824, virtual memory in use: 3572821640
2022-11-23 13:27:30 ERR default01[35]: #client1540: createExceptionInternal: !ERROR: MALException:pyapi3.eval:GDK reported error: MT_mmap: mmap(/var/lib/monetdb/dbfarm/default01/bat/pymmap4.tmp,0) failed: Invalid argument
2022-11-23 13:27:30 ERR default01[35]: #client1540: createExceptionInternal: !ERROR: !ERROR: GDKmmap: requesting virtual memory failed; memory requested: 0, memory in use: 674098824, virtual memory in use: 3572821640
```
Unfortunately I could not make it reproducible yet, as I haven't really found out what triggers it. It only seems obvious that a Python UDF triggers it.
Could it be something similar to b840770 from the Python interface code?
**Software versions**
- MonetDB version number 11.43.24
- OS and version: Fedora 35
- self-installed and compiled
| GDKmmap requesting 0 virtual memory | https://api.github.com/repos/MonetDB/MonetDB/issues/7343/comments | 4 | 2022-11-30T15:21:21Z | 2024-06-27T13:18:02Z | https://github.com/MonetDB/MonetDB/issues/7343 | 1,469,813,436 | 7,343 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A column(data type is double) that has done four operations couldn't group by aggregation. and pops up an error: "Query did not produce a result set."
**To Reproduce**
1) Create a table that has a column(data type is double), and insert some values into this table.
2-1) run the SQL below :
select column1 from (select column +10 as column1 from table ) tmp group by column1
2-2) run the SQL below :
select sum(column1) from (select column +10 as column1 from table ) tmp
**Expected behavior**
Return the correct result set.
**Software versions**
- MonetDB 11.45.7
- Windows 10
| column which datatype is double couldn't group or aggregation in version 11.45.7 | https://api.github.com/repos/MonetDB/MonetDB/issues/7342/comments | 4 | 2022-11-16T01:21:52Z | 2024-06-27T13:18:01Z | https://github.com/MonetDB/MonetDB/issues/7342 | 1,450,652,040 | 7,342 |
[
"MonetDB",
"MonetDB"
] | When I am trying to run command as below I got an error
```
$ sudo rpm --import https://dev.monetdb.org/downloads/MonetDB-GPG-KEY
error: https://dev.monetdb.org/downloads/MonetDB-GPG-KEY: key 1 import failed.
``` | Easy setup from the documentation does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/7341/comments | 9 | 2022-11-15T10:15:56Z | 2022-11-18T14:28:05Z | https://github.com/MonetDB/MonetDB/issues/7341 | 1,449,524,009 | 7,341 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
I'm trying to get the table schemas of my database with \d <table_name>, but the following error message appear in all of them (I'm using "matricula" as example):
```
CREATE TABLE "sys"."matricula" (
MAPI = (monetdb) /tmp/.s.monetdb.50000
QUERY = SELECT c.name, c.type, c.type_digits, c.type_scale, c."null", c."default", c.number FROM sys._columns c, sys._tables t, sys.schemas s WHERE c.table_id = t.id AND t.name = 'matricula' AND t.schema_id = s.id AND s.name = 'sys' ORDER BY c.number
ERROR = !GDK reported error: project_sht: does not match always
malloc failure
```
Apparently the issue is in sys.__columns table, because when I try to select the data from it the same error appears.
```
sql>select * from sys._columns
more>;
GDK reported error: project_sht: does not match always
```
**To Reproduce**
1) Create example table
```
create table fonte(
id integer not null,
tabela char(38) not null,
fonte char(128) not null
);
```
2) Show the table schema with \d
`\d fonte`
**Expected behavior**
The table schema should appear
**Actual behavior**
The error message appears
**Software versions**
- MonetDB version: MonetDB Database Server Toolkit v11.41.11 (Jul2021-SP1)
- OS and version: Debian GNU/Linux 10
- Installed from release package
**Issue labeling**
Schema error
| \d <table> doesn't work | https://api.github.com/repos/MonetDB/MonetDB/issues/7340/comments | 7 | 2022-11-11T13:45:38Z | 2022-11-16T12:26:04Z | https://github.com/MonetDB/MonetDB/issues/7340 | 1,445,498,512 | 7,340 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
After MonetDB received a SIGKILL, it gets into a corrupted unrecoverable state.
We use MonetDB containerized and k8s for orchestration. In order for MonetDB not to use unlimited memory we limit the memory from [k8s](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/). After continuous usage MonetDB surpasses the limit and k8s shuts down the process sending a SIGKILL. This is an acceptable scenario for us since k8s will restart the container and MonetDB will start again.
The problem is that MonetDB doesn't recover after the SIGKILL.
The logs that show the problem:
```
2022-11-10 10:16:16 MSG merovingian[12]: starting a proxy failed: could not receive initial byte: Connection reset by peer
2022-11-10 10:16:16 ERR control[12]: !monetdbd: an internal error has occurred 'could not receive initial byte: Connection reset by peer'
2022-11-10 10:16:16 ERR merovingian[12]: client error: could not receive initial byte: Connection reset by peer
2022-11-10 10:16:16 MSG merovingian[12]: database 'db' (-1) was killed by signal SIGKILL
2022-11-10 10:16:16 MSG merovingian[12]: database 'db' has crashed after start on 2022-11-10 08:38:11, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 0.20 0.07 (2-0=2)
2022-11-10 10:16:16 MSG db[23379]: arguments: /usr/local/bin/monetdb/bin/mserver5 --dbpath=/home/monetdb/db --set=merovingian_uri=mapi:monetdb://mipengine-globalnode-deployment-7c9f6fffb9-rzbnv:50000/db --set=mapi_listenaddr=none --set=mapi_usock=/home/monetdb/db/.mapi.sock --set=monet_vault_key=/home/monetdb/db/.vaultkey --set=gdk_nr_threads=4 --set=max_clients=320 --set=sql_optimizer=default_pipe --set=embedded_py=3
2022-11-10 10:16:22 MSG merovingian[12]: database 'db' (-1) has crashed with signal SIGSEGV (dumped core)
2022-11-10 10:16:22 ERR control[12]: !monetdbd: an internal error has occurred 'database 'db' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details'
```
I am not really sure from where the initial logs about `Connection reset by peer` are generated.
**To Reproduce**
It's a bit hard to reproduce since it requires k8s but I am attaching the corrupted state of the database.
Maybe it can be reproduced on a native deployment sending SIGKILL while monetDB is loaded with requests.
**Corrupted DB**
[crashed_monetdb.tar.gz](https://github.com/MonetDB/MonetDB/files/9981286/crashed_monetdb.tar.gz)
**Expected behavior**
MonetDB should be able to recover after a SIGKILL.
**Software versions**
- MonetDB version number 11.45.7
- OS and version: Ubuntu 20.04
- Using a [docker image](https://github.com/madgik/MIP-Engine/blob/master/monetdb/Dockerfile), compiling the source.
| MonetDB corrupted state after SIGKILL | https://api.github.com/repos/MonetDB/MonetDB/issues/7339/comments | 1 | 2022-11-10T13:54:28Z | 2024-06-27T13:18:00Z | https://github.com/MonetDB/MonetDB/issues/7339 | 1,443,951,048 | 7,339 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
A python UDF cannot have space in a column name.
**To Reproduce**
Run the following queries:
```
CREATE TABLE table4("row id" INT);
INSERT INTO table4("row id") VALUES (1);
CREATE OR REPLACE FUNCTION
func1("row id" INT)
RETURNS
TABLE("transfer" CLOB)
LANGUAGE PYTHON
{
import json
return json.dumps({"x":1})
};
SELECT * FROM func1((SELECT "row id" FROM table4));
```
The problem is caused from the space in the "row id" in the column name, in the signature of the udf.
**Expected behavior**
We should be able to provide a column in the udf signature that contains special characters, since it's inside double quotes.
**Software versions**
- MonetDB version number [11.45.7] | Python UDF cannot have space in column names | https://api.github.com/repos/MonetDB/MonetDB/issues/7338/comments | 2 | 2022-11-08T14:08:51Z | 2024-06-27T13:17:59Z | https://github.com/MonetDB/MonetDB/issues/7338 | 1,440,274,869 | 7,338 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Getting an error, when creating a prepared statement
"resultBlocks[1] should have been fetched by now"
**To Reproduce**
Creating a table with 480 columns.
CREATE TABLE IF NOT EXISTS table_temp (ID BIGINT AUTO_INCREMENT PRIMARY KEY, column1 VARCHAR(256),column2 VARCHAR(256), ... )
Then, use a prepared Statement to insert data.
I use java JDBC connection in Java like:
```
String inserSqlString = "INSERT INTO table_temp (column1, column2, ...) VALUES (?,?,....)"; //480 columns!
PreparedStatement ps = connection.prepareStatement(insertSqlString);
```
**Expected behavior**
No errors or exceptions.
We dont consider exceptions like this with older version of MonetDB (Jul 2021)
**Screenshots**
**Software versions**
- MonetDB 5 server v11.45.7 (Sep2022)
- Windows 10
- Installed from release package
| resultBlocks[1] should have been fetched by now | https://api.github.com/repos/MonetDB/MonetDB/issues/7337/comments | 6 | 2022-11-08T09:05:33Z | 2024-06-28T09:30:15Z | https://github.com/MonetDB/MonetDB/issues/7337 | 1,439,774,298 | 7,337 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Selecting from a literal-value table mixes up values.
**To Reproduce**
```
select a,b,c
from (values (10, 20, 0.5),
(20, 10, 0.5)
) as (a,b,c);
```
delivers:
```
+------+------+------+
| a | b | c |
+======+======+======+
| 10 | 10 | 0.5 |
| 20 | 20 | 0.5 |
+------+------+------+
2 tuples
```
**Expected behavior**
```
+------+------+------+
| a | b | c |
+======+======+======+
| 10 | 20 | 0.5 |
| 20 | 10 | 0.5 |
+------+------+------+
2 tuples
```
**Software versions**
- MonetDB version number 11.43.24
- OS and version: Fedora 35
- self-installed and compiled
| Selecting from a literal-value table returns wrong values | https://api.github.com/repos/MonetDB/MonetDB/issues/7336/comments | 2 | 2022-11-04T16:51:42Z | 2024-06-27T13:17:56Z | https://github.com/MonetDB/MonetDB/issues/7336 | 1,436,369,269 | 7,336 |
[
"MonetDB",
"MonetDB"
] | I am trying to deploy MonetDB to an OpenShift cluster. OpenShift does not run containers as root (for security reasons). It uses random uids instead, but gid is always zero (root group). File permissions must therefore be arranged via the group. So, I made my own Docker image (based on `monetdb/vesselai`) and set `umask 7` before starting MonetDB. Unfortunately MonetDB still creates its database files with mode 600, i.e., no group access. This is problematic if the pod is restarted and gets a new uid, which can no longer access the database (which is on a persistent volume).
Generally, applications are not expected to change umask. | Respect umask | https://api.github.com/repos/MonetDB/MonetDB/issues/7335/comments | 3 | 2022-11-03T16:04:45Z | 2022-11-07T09:04:22Z | https://github.com/MonetDB/MonetDB/issues/7335 | 1,434,912,598 | 7,335 |
[
"MonetDB",
"MonetDB"
] | Division of 2 decimal numbers result to a "overflow in conversion DECIMAL(18,12)" exception
**To Reproduce**
```
CREATE TABLE table1(
num1 decimal(18, 6),
num2 decimal(18, 6)
)
INSERT INTO table1(num1, num2)
VALUES(1000000, 1000)
SELECT (num1 / num2) as result
FROM table1
```
**Result**
ERROR [22003] [MonetDB][ODBC Driver 11.45.7]overflow in conversion to DECIMAL(18,12).
**Expected behavior**
```
result
---------
1000
```
The same exception occurs when 2 numbers are casted and then divided
`SELECT CAST(1000000 AS decimal(18,6)) / CAST(1000 AS decimal(18,6)) as result`
**Result:**
ERROR [22003] [MonetDB][ODBC Driver 11.45.7]overflow in conversion to DECIMAL(18,12).
**Software versions**
- MonetDB 5 server v11.45.7 (Sep2022)
- Windows 10 Pro / and Windows Server
- ODBC
- Installed from release package | division results in "overflow in conversion to DECIMAL(18,12)" exception | https://api.github.com/repos/MonetDB/MonetDB/issues/7334/comments | 3 | 2022-11-02T10:42:40Z | 2024-02-09T10:40:44Z | https://github.com/MonetDB/MonetDB/issues/7334 | 1,432,913,487 | 7,334 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
mserver5 fails to start when installed at a path containing accented characters on Windows.
```
#2022-11-01 09:42:03: main thread: createExceptionInternal: !ERROR: LoaderException:loadLibrary:Loading error failed to open library generator (from within file 'C:\Users\Xxxéxxx\AppData\Local\XXX\MonetDb\MonetDB5\lib\monetdb5\_generator.dll'): Le module sp?cifi? est introuvable.
```
**To Reproduce**
Install/extract MonetDb on Windows to a folder within the user profile, where the username (and the profile folder) has an accented character (in this case "é") within it. (Also seen with Simplified Chinese characters).
Attempt to start mserver5. It will fail with an error similar to the above.
**Expected behavior**
I expect the LoadLibrary calls to be able to handle non-ASCII characters correctly.
**Software versions**
- MonetDB version number: 11.43.21 Jan2022-SP4
- OS and version: Windows 10 10.0 amd64
- Installed by extracting MSI to a folder within the user profile.
| DLLs fail to load on Windows with accented characters in path | https://api.github.com/repos/MonetDB/MonetDB/issues/7333/comments | 7 | 2022-11-02T08:26:29Z | 2024-06-27T13:17:55Z | https://github.com/MonetDB/MonetDB/issues/7333 | 1,432,702,725 | 7,333 |
[
"MonetDB",
"MonetDB"
] | *Non SQL standard*
To compare two datatypes treating at the same time `NULL` as a comparable value some databases implement the `IS [NOT] DISTINCT FROM`. This means that any not-null valued datatype can be safely compared with `NULL` e.g. `SELECT 3 IS DISTINCT FROM NULL -> true`. Note that `NULL` values can be compared `SELECT NULL IS DISTINCT FROM NULL -> false` and `SELECT NULL NOT DISTINCT FROM NULL -> true`
Implemented in [postgres](https://www.postgresql.org/docs/15/functions-comparison.html#FUNCTIONS-COMPARISON-PRED-TABLE), [sqlserver](https://learn.microsoft.com/en-us/sql/t-sql/queries/is-distinct-from-transact-sql?view=sql-server-ver16)
| Support IS [NOT] DISTINCT FROM predicate | https://api.github.com/repos/MonetDB/MonetDB/issues/7332/comments | 2 | 2022-10-19T10:42:13Z | 2024-06-27T13:17:54Z | https://github.com/MonetDB/MonetDB/issues/7332 | 1,414,734,773 | 7,332 |
[
"MonetDB",
"MonetDB"
] | *Non SQL standard*
Ops like `INSERT`, `UPDATE` and `DELETE` could return the same number of rows as the ones affected so a second `SELECT` query is not needed.
It is implemented by most popular dbs [postgres](https://www.postgresql.org/docs/current/dml-returning.html), [sqlite](https://www.sqlite.org/lang_returning.html), [mariadb](https://mariadb.com/kb/en/insertreturning/)...
It is also a point of performance improvement for driver and ORM libs (see the relative discussion in SQLAlchemy 2.0 Beta [release notes](https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html#optimized-orm-bulk-insert-now-implemented-for-all-backends-other-than-mysql))
| Support RETURNING clause | https://api.github.com/repos/MonetDB/MonetDB/issues/7331/comments | 0 | 2022-10-18T15:53:08Z | 2024-06-27T13:17:53Z | https://github.com/MonetDB/MonetDB/issues/7331 | 1,413,468,455 | 7,331 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Creating of a temporary table fails after reconnect.
**To Reproduce**
```
~$ sudo -u monetdb monetdb create test_bug
created database in maintenance mode: test_bug
~$ sudo -u monetdb monetdb release test_bug
taken database out of maintenance mode: test_bug
~$ mclient -d test_bug -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Sep2022)
Database: MonetDB v11.45.7 (Sep2022), 'mapi:monetdb://luna:50000/test_bug'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TEMP TABLE tmp.test (id bigint NOT NULL PRIMARY KEY);
operation successful
sql>exit
~$ mclient -d test_bug -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Sep2022)
Database: MonetDB v11.45.7 (Sep2022), 'mapi:monetdb://luna:50000/test_bug'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TEMP TABLE tmp.test (id bigint NOT NULL PRIMARY KEY);
CONSTRAINT PRIMARY KEY: key test_id_pkey already exists
```
Stopping the database seem to heal the problem:
```
~$ sudo -u monetdb monetdb stop test_bug
stopping database 'test_bug'... done
~$ mclient -d test_bug -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Sep2022)
Database: MonetDB v11.45.7 (Sep2022), 'mapi:monetdb://luna:50000/test_bug'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TEMP TABLE tmp.test (id bigint NOT NULL PRIMARY KEY);
operation successful
sql>exit
```
**Expected behavior**
The second attempt of creating the temporary table should not fail.
Here the same test with an older version of MonetDB:
```
~$ sudo -u monetdb monetdb create test_bug
created database in maintenance mode: test_bug
~$ sudo -u monetdb monetdb release test_bug
taken database out of maintenance mode: test_bug
~$ mclient -d test_bug -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Nov2019-SP1)
Database: MonetDB v11.35.9 (Nov2019-SP1), 'mapi:monetdb://bigone1:50000/test_bug'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TEMP TABLE tmp.test (id bigint NOT NULL PRIMARY KEY);
operation successful
sql>exit
~$ mclient -d test_bug -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Nov2019-SP1)
Database: MonetDB v11.35.9 (Nov2019-SP1), 'mapi:monetdb://bigone1:50000/test_bug'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TEMP TABLE tmp.test (id bigint NOT NULL PRIMARY KEY);
operation successful
sql>exit
```
**Software versions**
- MonetDB v11.45.7 (Sep2022)
- Ubuntu 20.04
- Installed from release package
**Additional context**
Using **pymonetdb** shows same behavior.
| Creating temporary table fails after reconnect | https://api.github.com/repos/MonetDB/MonetDB/issues/7330/comments | 4 | 2022-10-18T09:50:17Z | 2024-06-27T13:17:53Z | https://github.com/MonetDB/MonetDB/issues/7330 | 1,412,912,186 | 7,330 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
Insecure Path That Leads To Critical Data Exposure
**To Reproduce**
intxturl: "/usr/local/opt/bison/bin:/usr/local/opt/openjdk/bin:/usr/local/opt/bison/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin"
https://www.monetdb.org/testweb/logs/86580:5f17d2f9b5b0/Cla-Darwin-x86_64/MdoClient.identify
https://www.monetdb.org/testweb/logs/86580:5f17d2f9b5b0/Cla-Darwin-x86_64/
**Expected behavior**
Path Traversal
# 2022-10-12 19:08:03 -- /export/scratch1/home/monet/testweb/logs/2022-10-12_19:08/MdoServer
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 1.8T 281G 1.4T 17% /export/scratch1
~/testweb/source/monetdb-java ~/testweb/TestTools
updating the sources for monetdb-java
pulling from https://www.monetdb.org/hg/monetdb-java/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-java sources updated to revision 7ec8d469fd0b
~/testweb/source/monetdb-perl ~/testweb/TestTools
updating the sources for monetdb-perl
pulling from https://www.monetdb.org/hg/monetdb-perl/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-perl sources updated to revision a2a23aa2bf8e
~/testweb/source/monetdb-php ~/testweb/TestTools
updating the sources for monetdb-php
pulling from https://www.monetdb.org/hg/monetdb-php/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-php sources updated to revision 9de229e8cb8d
~/testweb/source/monetdb-ruby ~/testweb/TestTools
updating the sources for monetdb-ruby
pulling from https://www.monetdb.org/hg/monetdb-ruby/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-ruby sources updated to revision c2070750ad20
~/testweb/source/monetdb-test-data ~/testweb/TestTools
updating the sources for monetdb-test-data
pulling from https://www.monetdb.org/hgtt/monetdb-test-data/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-test-data sources updated to revision 855b4c5aa368
~/testweb/source/monetdb-external-tests ~/testweb/TestTools
updating the sources for monetdb-external-tests
pulling from https://www.monetdb.org/hgtt/monetdb-external-tests/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-external-tests sources updated to revision 1c488a273181
~/testweb/source/MonetDB ~/testweb/TestTools
updating the sources for MonetDB, switching to Jan2022
pulling from https://www.monetdb.org/hg/MonetDB/
searching for changes
no changes found
716 files updated, 0 files merged, 74 files removed, 0 files unresolved
MonetDB sources updated to revision 830c006f2c77
error: aborting MdoServer run, as a log directory for 86802:830c006f2c77 already exists: identical sources have been tested already
# 2022-10-12 19:08:57 -- /export/scratch1/home/monet/testweb/logs/2022-10-12_19:08/MdoServer
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 1.8T 281G 1.4T 17% /export/scratch1
~/testweb/source/monetdb-java ~/testweb/TestTools
updating the sources for monetdb-java
pulling from https://www.monetdb.org/hg/monetdb-java/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-java sources updated to revision 7ec8d469fd0b
~/testweb/source/monetdb-perl ~/testweb/TestTools
updating the sources for monetdb-perl
pulling from https://www.monetdb.org/hg/monetdb-perl/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-perl sources updated to revision a2a23aa2bf8e
~/testweb/source/monetdb-php ~/testweb/TestTools
updating the sources for monetdb-php
pulling from https://www.monetdb.org/hg/monetdb-php/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-php sources updated to revision 9de229e8cb8d
~/testweb/source/monetdb-ruby ~/testweb/TestTools
updating the sources for monetdb-ruby
pulling from https://www.monetdb.org/hg/monetdb-ruby/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-ruby sources updated to revision c2070750ad20
~/testweb/source/monetdb-test-data ~/testweb/TestTools
updating the sources for monetdb-test-data
pulling from https://www.monetdb.org/hgtt/monetdb-test-data/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-test-data sources updated to revision 855b4c5aa368
~/testweb/source/monetdb-external-tests ~/testweb/TestTools
updating the sources for monetdb-external-tests
pulling from https://www.monetdb.org/hgtt/monetdb-external-tests/
searching for changes
no changes found
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
monetdb-external-tests sources updated to revision 1c488a273181
~/testweb/source/MonetDB ~/testweb/TestTools
updating the sources for MonetDB, switching to Jul2021
pulling from https://www.monetdb.org/hg/MonetDB/
searching for changes
no changes found
1871 files updated, 0 files merged, 258 files removed, 0 files unresolved
MonetDB sources updated to revision 219c3300d4b9
finding previous run for branch Jul2021
previous run was: 86544:c8b5a0a4e270
# 2022-10-12 19:09:57 == changing logdir from /export/scratch1/home/monet/testweb/logs/2022-10-12_19:08 to /export/scratch1/home/monet/testweb/logs/86808:219c3300d4b9, delta time: 60s
storing incoming commits
~/testweb/source/MonetDB ~/testweb/TestTools
moving sources into staging area
creating MonetDB-219c3300d4b9.tar.bz2
creating monetdb-java-7ec8d469fd0b.tar.bz2
creating monetdb-test-data-855b4c5aa368.tar.bz2
creating monetdb-external-tests-1c488a273181.tar.bz2
creating TestTools-88f215894731.tar.bz2
# 2022-10-12 19:10:19 == gathering workers, delta time: 22s
in directory /export/scratch1/home/monet/testweb/TestTools/config/workers:
lab01 (config/workers/lab01.da.cwi.nl)
lab03 (config/workers/lab03.ins.cwi.nl)
lab04 (config/workers/lab04.da.cwi.nl)
lab05 (config/workers/lab05.da.cwi.nl)
lab05 is disabled by configuration
lab06 (config/workers/lab06.da.cwi.nl)
macmini (config/workers/mac-mini.scilens.private)
power8 (config/workers/power8.scilens.private)
win2k22 (config/workers/win2k22.virt.private)
# 2022-10-12 19:10:19 == gathering targets, delta time: 0s
processing target: Int-Fedora-x86_64-assert-propcheck
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-dbfarm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-sanitize
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-undefined
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-nowal
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-assert-debug=65536
found worker: lab01
found worker: lab04
found worker: lab06
processing target: Cla-Fedora-x86_64
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-notint128-dbfarm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=1-assert
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=1-propcheck
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=32-propcheck-rpm
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
found worker: lab01
found worker: lab04
found worker: lab06
processing target: GNU-Fedora-powerpc64-thrs=8-assert-propcheck-dbfarm
found worker: power8
processing target: GNU-Fedora-powerpc64-thrs=8-notint128-assert-propcheck-dbfarm
found worker: power8
processing target: Cla-Darwin-x86_64
found worker: macmini
processing target: Cla-Darwin-x86_64-assert-propcheck
found worker: macmini
processing target: Mic-Windows7-x86_64-assert-propcheck
found worker: lab03
processing target: Mic-Windows2022-i386-installer-notest
found worker: win2k22
processing target: Mic-Windows2022-i386-assert-propcheck
found worker: win2k22
processing target: Mic-Windows2022-x86_64-installer
found worker: win2k22
# 2022-10-12 19:10:19 == final workqueues for workers, delta time: 0s
(final execution based on workers themselves):
lab01: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
lab03: Mic-Windows7-x86_64-assert-propcheck
lab04: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
lab06: Int-Fedora-x86_64-assert-propcheck GNU-Fedora-x86_64-dbfarm GNU-Fedora-x86_64-assert-propcheck-multifarm-coverage GNU-Fedora-x86_64-sanitize GNU-Fedora-x86_64-undefined GNU-Fedora-x86_64-nowal GNU-Fedora-x86_64-assert-debug=65536 Cla-Fedora-x86_64 GNU-Fedora-x86_64-notint128-dbfarm GNU-Fedora-x86_64-thrs=1-assert GNU-Fedora-x86_64-thrs=1-propcheck GNU-Fedora-x86_64-thrs=32-propcheck-rpm GNU-Fedora-x86_64-thrs=53-assert-tcmalloc
macmini: Cla-Darwin-x86_64 Cla-Darwin-x86_64-assert-propcheck
power8: GNU-Fedora-powerpc64-thrs=8-assert-propcheck-dbfarm GNU-Fedora-powerpc64-thrs=8-notint128-assert-propcheck-dbfarm
win2k22: Mic-Windows2022-i386-installer-notest Mic-Windows2022-i386-assert-propcheck Mic-Windows2022-x86_64-installer
# 2022-10-12 21:43:25 == all workers finished, delta time: 9186s
# 2022-10-12 21:43:26 -- /export/scratch1/home/monet/testweb/logs/86808:219c3300d4b9/MdoServer, elapsed time: 9269s | Critical Path Traversal Logs Exposed | https://api.github.com/repos/MonetDB/MonetDB/issues/7329/comments | 1 | 2022-10-13T16:05:25Z | 2022-12-14T09:56:26Z | https://github.com/MonetDB/MonetDB/issues/7329 | 1,408,070,970 | 7,329 |
[
"MonetDB",
"MonetDB"
] | The *dependency_columns_on_functions* view shows all (table's) columns.
To demonstrate, run following example
```
CREATE TABLE mmtest01 ( id int, name text)
;
CREATE OR REPLACE FUNCTION mmtest02()
RETURNS int
BEGIN
INSERT INTO mmtest01(id) VALUES (1);
RETURN 1;
END
;
-- the following SELECT returns both columns
-- not just the one actually used by the function
SELECT c.*
FROM sys.dependency_columns_on_functions c
WHERE c.function_name LIKE 'mmtest02'
ORDER BY table_name
;
```
So in fact this view has no real value (looks to me but of course i may be wrong). What would be really helpfull is to get list of the columns that are really used by the function - in the example above the SELECT would return just 1 column (the _ID_). Which is btw what the view name hints.
Just as a side note - looks like the function_id is missing in the _sys.dependency_tables_on_functions_. To get table name for the column (dependency) a join condition by the function name may not help when there is an overloaded function.
thanks & best regards
budulinek dejmihrasek | sys.dependency_columns_on_functions view lists all table columns, not just the actually used by the function | https://api.github.com/repos/MonetDB/MonetDB/issues/7328/comments | 4 | 2022-10-03T13:29:52Z | 2024-06-27T13:17:51Z | https://github.com/MonetDB/MonetDB/issues/7328 | 1,394,738,677 | 7,328 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
I am getting sql syntax errors with insert statements into a table. The insert statements work fine in other DBMSs such as DuckDB, MS SQL Server, MySQL, PostgreSQL, etc.
The insert sql script has 822 sql insert statements, all succeed in MonetDB except for the attached 10 statements.
**To Reproduce**
1 connect to MonetDB via ODBC
2 create the table
**create table in_sync_dbms_object (
DBMS_CD CHAR(8) not null,
OBJECT_TYPE_CD CHAR(8) not null,
SQL_TYPE_CD CHAR(8) not null,
REF_DBMS_CD CHAR(8),
REF_OBJECT_TYPE_CD CHAR(8),
REF_SQL_TYPE_CD CHAR(8),
OBJECT_SQL CHARACTER LARGE OBJECT,
OBJECT_SCRIPT CHARACTER LARGE OBJECT,
OBJECT_SQL_CAT_COL VARCHAR(128),
OBJECT_SQL_SCHEM_COL VARCHAR(128),
OBJECT_SQL_PARENT_NAME_COL VARCHAR(128),
OBJECT_SQL_NAME_COL VARCHAR(128),
OBJECT_SQL_SIG_COL VARCHAR(128),
OBJECT_SQL_SUBTYPE_COL VARCHAR(128),
OBJECT_SQL_ORD_POSITION_COL VARCHAR(128),
OBJECT_SQL_TEXT_COL VARCHAR(128),
SIDE_EFFECT_DESC VARCHAR(80),
CTRL_INS_DTM TIMESTAMP default CURRENT_TIMESTAMP not null,
CTRL_UPD_DTM TIMESTAMP not null,
CTRL_USR_ID VARCHAR(256) not null,
constraint PK_IN_SYNC_DBMS_OBJECT primary key (DBMS_CD, OBJECT_TYPE_CD, SQL_TYPE_CD)
)**
3 run the attached sql script that has 10 insert statements (all fail).
(change the attached file extension from .txt to .sql as not allowed to attach .sql file).
**Expected behavior**
The 10 attached sql statements are valid sql and should execute with no error.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Software versions**
- MonetDB 11.43
- Windows 10 64-bit
- Installed from release package
**Issue labeling **
SQL parse error
**Additional context**
Add any other context about the problem here.
[parse_errors.txt](https://github.com/MonetDB/MonetDB/files/9630074/parse_errors.txt)
| SQL insert statement syntax error | https://api.github.com/repos/MonetDB/MonetDB/issues/7327/comments | 8 | 2022-09-23T00:07:41Z | 2024-06-27T13:17:51Z | https://github.com/MonetDB/MonetDB/issues/7327 | 1,383,141,235 | 7,327 |
[
"MonetDB",
"MonetDB"
] | I am running MacOs 12.5.1
I have installed the latest version of monetdb from the archive as documented here: https://www.monetdb.org/downloads//MacOSX/
When I attempt to start mserver5 I get the following error
```
# MonetDB 5 server v11.43.21 (Jan2022-SP4)
# Serving database 'test', using 4 threads
# Compiled for x86_64-pc-darwin-appleclang/64bit with 128bit integers
# Found 8.000 GiB available main-memory of which we use 6.520 GiB
# Copyright (c) 1993 - July 2008 CWI.
# Copyright (c) August 2008 - 2022 MonetDB B.V., all rights reserved
# Visit https://www.monetdb.org/ for further information
#2022-09-15 14:37:14: main thread: createExceptionInternal: !ERROR: LoaderException:loadLibrary:Loading error failed to open library geom (from within file '/usr/local/monetdb/lib/monetdb5/lib_geom.so'): dlopen(/usr/local/monetdb/lib/monetdb5/lib_geom.so, 0x000A): Library not loaded: '@rpath/libgeos.3.11.0.dylib'
#2022-09-15 14:37:14: main thread: createExceptionInternal: !ERROR: Referenced from: '/usr/local/monetdb/lib/monetdb/external/libgeos_c.1.dylib'
#2022-09-15 14:37:14: main thread: createExceptionInternal: !ERROR: Reason: tried: '/usr/local/monetdb/lib/monetdb/external/../lib/libgeos.3.11.0.dylib' (no such file), '/usr/local/monetdb/lib/libgeos.3.11.0.dylib' (no such file), '/usr/local/monetdb/lib/libgeos.3.11.0.dylib' (no such file), '/usr/local/monetdb/lib/libgeos.3.11.0.dylib' (no such file), '/usr/local/monetdb/lib/libgeos.3.11.0.dylib' (no such file), '/u
#2022-09-15 14:37:14: main thread: mal_init: !ERROR: LoaderException:loadLibrary:Loading error failed to open library geom (from within file '/usr/local/monetdb/lib/monetdb5/lib_geom.so'): dlopen(/usr/local/monetdb/lib/monetdb5/lib_geom.so, 0x000A): Library not loaded: '@rpath/libgeos.3.11.0.dylib'```
It looks like the library needed for computational geometry isn't bundled with the installer. | Broken Mac installer - missing libgeos | https://api.github.com/repos/MonetDB/MonetDB/issues/7326/comments | 4 | 2022-09-15T13:45:11Z | 2022-09-19T07:11:21Z | https://github.com/MonetDB/MonetDB/issues/7326 | 1,374,556,640 | 7,326 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
sentences is a common function you can find in Hive or Databricks
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-StringFunctions
sentences(string str, string lang, string locale)
Tokenizes a string of natural language text into words and sentences, where each sentence is broken at the appropriate sentence boundary and returned as an array of words. The 'lang' and 'locale' are optional arguments. For example, sentences('Hello there! How are you?') returns ( ("Hello", "there"), ("How", "are", "you") ).
https://docs.microsoft.com/en-us/azure/databricks/sql/language-manual/functions/sentences
sentences(str [, lang, country] )
Arguments
str: A STRING expression to be parsed.
lang: An optional STRING expression with a language code from ISO 639 Alpha-2 (e.g. ‘DE’) , Alpha-3, or a language subtag of up to 8 characters.
country: An optional STRING expression with a country code from ISO 3166 alpha-2 country code or a UN M.49 numeric-3 area code.
Returns an Array
**Describe the solution you'd like**
same function that described before
**Describe alternatives you've considered**
N/A | sentences function | https://api.github.com/repos/MonetDB/MonetDB/issues/7325/comments | 3 | 2022-09-14T06:21:44Z | 2024-07-19T08:50:23Z | https://github.com/MonetDB/MonetDB/issues/7325 | 1,372,410,619 | 7,325 |
[
"MonetDB",
"MonetDB"
] | **Is your feature request related to a problem? Please describe.**
I would like to use several different methods to calculate distance between two strings :
-levenshtein (already exists)
-hamming
-jaro winkler
-damerau levenshtein
-...
**Describe the solution you'd like**
a generic function string_distance('method',str1, str2) with useful error messages about methods when incorrect
**Describe alternatives you've considered**
several functions : seems too much for a simple usage
Best regards,
Simon | string_distance('method',str1, str2) as a generic distance function | https://api.github.com/repos/MonetDB/MonetDB/issues/7324/comments | 5 | 2022-09-14T06:16:56Z | 2024-06-27T13:17:49Z | https://github.com/MonetDB/MonetDB/issues/7324 | 1,372,406,399 | 7,324 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
sys.epoch_ms(timestamp) returns a decimal(18,3) in 11.43 where it previously returned a bigint in 11.41 Also there is now no way to obtain the number of milliseconds since the epoch from a timestamp directly and efficiently as a bigint.
Our use of MonetDB requires the binning of both millisecond accurate timestamps and differences between these timestamps.
On older versions of MonetDB we were using using `select cast(timestamp '1970-01-01 00:00:00.123' as bigint);`
This would yield a result of 123.
We upgraded to 11.41 and have been using the`select sys.epoch_ms(timestamp '1970-01-01 00:00:00.123');` that again returns a bigint result of 123.
In 11.43 it seems that sys.epoch_ms now returns a **decimal(18,3)** with the fractional part as seconds.
This change to an established function (in fact the removal of any way of getting milliseconds since the epoch out of a date time stamp as a bigint) completely breaks our application. We could re-write our SQL queries to functionally achieve with 11.43 what we do with 11.41 at significant development effort. Unfortunately, testing this shows a massive and unsustainable performance penalty for our circumstances - more than doubling of the query time for our typical queries.
Can we please have sys.epoch_ms revert to its 11.41 behaviour or at least some way of getting a bigint count of milliseconds since the epoch out a date time stamp.
**To Reproduce**
In 11.41 run the SQL `sys.epoch_ms(timestamp '1970-01-01 00:00:00.123');`
Result is a bigint 123.
In 11.43 run the SQL `sys.epoch_ms(timestamp '1970-01-01 00:00:00.123');`
Result is a decimal(18,3) 0.123.
**Expected behavior**
In 11.43, the SQL : sys.epoch_ms(timestamp '1970-01-01 00:00:00.123'); should return the bigint 123
**Screenshots**
N/A
**Software versions**
- MonetDB version number 11.43 (cf 11.41)
- OS and version: Debian Buster
- Installed from release package.
**Issue labeling **
Make liberal use of the labels to characterise the issue topics. e.g. identify severity, version, etc..
**Additional context**
Add any other context about the problem here.
| sys.epoch_ms | https://api.github.com/repos/MonetDB/MonetDB/issues/7323/comments | 1 | 2022-09-13T16:29:53Z | 2022-09-18T11:20:00Z | https://github.com/MonetDB/MonetDB/issues/7323 | 1,371,716,533 | 7,323 |
[
"MonetDB",
"MonetDB"
] | Windows 10 x64
MonetDB 11.43.0021
MonetDBODBClib 11.43.0021 Jan2022-SP4
Resultset of ::SQLForeignKeys UPDATE_RULE and DELETE_RULE
do not report cascade, set null or set default.
For test_table2 of test schema, driver reports all foreign keys update_rule and delete_rule as SQL_NO_ACTION.
```
create table TEST_TABLE1 (
COL1 DECIMAL(18, 2) not null,
COL2 VARCHAR(20),
COL3 TIMESTAMP,
COL_USR_ID VARCHAR(128),
TABLE1_CD VARCHAR(8) not null,
DESCRIPTION VARCHAR(20),
constraint PK_TEST_TABLE1 primary key (TABLE1_CD),
constraint AK_TEST_TABLE1_COL2 unique (COL2, COL_USR_ID)
);
/*----------------------------------------------------------------------------*/
/* Table: TEST_TABLE2 */
/*----------------------------------------------------------------------------*/
create table TEST_TABLE2 (
COL1 DECIMAL(18, 2) not null,
COL_DESC VARCHAR(20),
COL_ADD_DTM TIMESTAMP,
COL_USR_ID VARCHAR(128),
TABLE2_CD VARCHAR(8),
TABLE1_CD VARCHAR(8),
DESCRIPTION VARCHAR(20),
COL_RESTRICT VARCHAR(8),
COL_CASCADE VARCHAR(8),
COL_SET_NULL VARCHAR(8),
COL_SET_DEFAULT VARCHAR(8),
COL_INITIALLY VARCHAR(8),
COL_IMMEDIATE VARCHAR(8),
COL_DEFERRED VARCHAR(8),
COL_SYSTEM_NAMED VARCHAR(8),
constraint PK_TEST_TABLE2 primary key (COL1)
);
alter table TEST_TABLE2
add constraint FK_COL_CASCADE foreign key (COL_CASCADE)
references TEST_TABLE1 (TABLE1_CD)
on update cascade
on delete cascade;
alter table TEST_TABLE2
add constraint FK_COL_RESTRICT foreign key (COL_RESTRICT)
references TEST_TABLE1 (TABLE1_CD);
alter table TEST_TABLE2
add constraint FK_COL_SET_DEFAULT foreign key (COL_SET_DEFAULT)
references TEST_TABLE1 (TABLE1_CD)
on delete set default;
alter table TEST_TABLE2
add constraint FK_COL_SET_NULL foreign key (COL_SET_NULL)
references TEST_TABLE1 (TABLE1_CD)
on delete set null;
alter table TEST_TABLE2
add foreign key (COL_SYSTEM_NAMED)
references TEST_TABLE1 (TABLE1_CD);
``` | ODBC Driver does not correctly report ::SQLForeignKeys update or delete rule | https://api.github.com/repos/MonetDB/MonetDB/issues/7322/comments | 2 | 2022-08-26T18:54:04Z | 2024-06-27T13:17:48Z | https://github.com/MonetDB/MonetDB/issues/7322 | 1,352,626,608 | 7,322 |
[
"MonetDB",
"MonetDB"
] | Hi,
After upgrading to version 11.43.21, loading the dump started to hang the server. Downgrading back to 11.43.15 fixed the issue.
the command I am using to load the dump:
mclient -d dbname -f sql < "pathtofile/dump.sql"
sample dump file:
COPY 1 RECORDS INTO tablename FROM stdin USING DELIMITERS '\t','\n','"';
Thank you. | V11.43.21 Copy into From Stdin is blocking the server | https://api.github.com/repos/MonetDB/MonetDB/issues/7321/comments | 2 | 2022-08-26T09:24:10Z | 2023-06-20T11:03:25Z | https://github.com/MonetDB/MonetDB/issues/7321 | 1,352,002,320 | 7,321 |
[
"MonetDB",
"MonetDB"
] | Hi,
I am using v11.43.15 and executing call storagemodelinit(); to have access to the storagemodel table is returning :
Cannot access column descriptor
Thank you. | v11.43.15 storagemodelinit Cannot access column descriptor | https://api.github.com/repos/MonetDB/MonetDB/issues/7320/comments | 1 | 2022-08-26T09:21:12Z | 2022-09-24T10:57:27Z | https://github.com/MonetDB/MonetDB/issues/7320 | 1,351,998,984 | 7,320 |
[
"MonetDB",
"MonetDB"
] | call sys.hot_snapshot('/home/monetdb/mdb_hotbackup_20220824-1355387174998.tar.lz4');
esults in
:0.22000-GDK reported error: snapshot_heap: One of /home/dbFarm/trg/bat/BACKUP/6.theap and /home/dbFarm/trg/bat/6.theap must exist
| Hotbackup fails after lastest update | https://api.github.com/repos/MonetDB/MonetDB/issues/7319/comments | 5 | 2022-08-24T12:01:42Z | 2023-09-13T14:43:31Z | https://github.com/MonetDB/MonetDB/issues/7319 | 1,349,331,768 | 7,319 |
[
"MonetDB",
"MonetDB"
] | **Describe the bug**
When using distinct in subqueries on a **catalog table** the distinct is not working properly, it is ignored.
**To Reproduce**
```
sql>select count(*) from (select distinct table_id from sys.columns) as sq;
+------+
| %6 |
+======+
| 769 |
+------+
1 tuple
```
by using the `count(distinct <COL>)` syntax the result seems to be right
```
sql>select count(distinct table_id) from sys.columns;
+------+
| %6 |
+======+
| 130 |
+------+
1 tuple
```
and the subquery that uses the `select distinct ...` seems to be working fine by itself
```
sql>select distinct table_id from sys.columns;
+----------+
| table_id |
+==========+
| 2001 |
...
...
...
| 7552 |
+----------+
130 tuples
```
please not that the behavior is as expected for user created tables!
**Expected behavior**
the first example should be returning the value 130 e.g.
```
sql>select count(*) from (select distinct table_id from sys.columns) as sq;
+------+
| %6 |
+======+
| 130 |
+------+
1 tuple
```
**Software versions**
- MonetDB 5 server 11.46.0 (hg id: 0d0b43892e84)
- Kernel: 5.18.18-100.fc35.x86_64
Distro: Fedora release 35 (Thirty Five)
- self-installed and compiled
| distinct in a subquery not working properly | https://api.github.com/repos/MonetDB/MonetDB/issues/7318/comments | 3 | 2022-08-22T10:25:23Z | 2024-06-27T13:17:46Z | https://github.com/MonetDB/MonetDB/issues/7318 | 1,346,172,879 | 7,318 |
[
"MonetDB",
"MonetDB"
] | This is my first time using MonetDB and something weird happened.
The procedures often vanish with no reason.
Below is the version I'm using.
MonetDB version : 11.43.15 (Jan2022-SP3)
OS : CentOS8(kernel version : 4.18.0-394.el8.x86_64)
Attach the procedure script for further information.
I erased some comments written in Korean...
CREATE OR REPLACE PROCEDURE DSDMT.SP_PRSN_CUST_MAPPING_SCRT (IN_BQY_CD STRING)
BEGIN
INSERT INTO DSDMT.PRSN_CUST_MAPPING_SCRT
(
CUST_ID
-- , CUST_SRNO
, BQY_CD
-- , LOAD_DTM
, LOAD_PGM_ID
)
SELECT T1.CUST_ID AS CUST_ID
, T1.BQY_CD AS BQY_CD
, 'PRSN_CUST_MAPPING_SCRT.sql' AS LOAD_PGM_ID
FROM DSDMT.PRSN_MKT_ANA_SCRT_SRC T1
LEFT OUTER JOIN DSDMT.PRSN_CUST_MAPPING_SCRT T2
ON T1.CUST_ID = T2.CUST_ID
WHERE 1 = 1
AND T1.BQY_CD = IN_BQY_CD
AND T2.CUST_SRNO IS NULL
;
END;
This is an example of procedures I've made.
There were five procedures and the next day I check, there is only one left. Sometimes two.
What can cause this vanishing?
| Procedure vanishing | https://api.github.com/repos/MonetDB/MonetDB/issues/7317/comments | 5 | 2022-07-25T01:19:36Z | 2023-09-13T14:44:28Z | https://github.com/MonetDB/MonetDB/issues/7317 | 1,316,078,611 | 7,317 |
[
"MonetDB",
"MonetDB"
] | when we perform rsync we are getting below error in DB logs
2022-07-22 23:34:42 ERR DB_PNLSYND_V2_P_B_22JULY2022_BKP[389574]: #client5778: BATproject2: !ERROR: does not match always
2022-07-22 23:34:42 ERR DB_PNLSYND_V2_P_B_22JULY2022_BKP[389574]: #client5778: createExceptionInternal: !ERROR: MALException:algebra.projection:GDK reported error: BATproject2: does not match always
And if we copy rsync and the table are corrupted with bat file error.
we need confirmation that rsync is supported with the below version and tried the scp copy of well.
version - 11.43.5
| ERROR: MALException:algebra.projection:GDK reported error: BATproject2: does not match always | https://api.github.com/repos/MonetDB/MonetDB/issues/7316/comments | 1 | 2022-07-23T10:59:58Z | 2022-07-27T15:44:46Z | https://github.com/MonetDB/MonetDB/issues/7316 | 1,315,631,406 | 7,316 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.