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"
] | Date: 2013-06-17 23:39:39 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-09-27 13:47:19 +0200
## Comment 18856
Date: 2013-06-17 23:39:39 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
sql>SELECT CAST(0.94 AS INTEGER);
+--------------+
| single_value |
+==============+
| 0 |
+--------------+
1 tuple (0.389ms)
sql>SELECT CAST(0.95 AS INTEGER);
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 tuple (0.298ms)
Reproducible: Always
### Steps to Reproduce:
1. See details
2.
3.
### Actual Results:
0.94 -> 0
0.95 -> 1
### Expected Results:
0.94 -> 0
0.95 -> 0
We use this a lot in our code base, which may lead to unexpected results.
## Comment 18857
Date: 2013-06-18 11:30:44 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ee65f3d73109](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ee65f3d73109) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee65f3d73109](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee65f3d73109)
Changeset description:
Fix for bug #3310.
Not entirely the way the bug suggests: we round, we do not truncate.
Whether this is correct is up to Niels.
At least rounding now happens correctly.
## Comment 18858
Date: 2013-06-18 12:29:55 +0200
From: @bartscheers
Shouldn't casting a double to an integer do an intrinsic truncate?
Notice the differences:
sql>select cast(0.98 as integer);
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 tuple (0.143ms)
sql>select cast(cast(0.98 as double) as integer);
+--------------+
| single_value |
+==============+
| 0 |
+--------------+
1 tuple (0.295ms)
where the second one is correct.
## Comment 18859
Date: 2013-06-18 12:46:02 +0200
From: @sjoerdmullender
What does the standard say?
## Comment 18860
Date: 2013-06-18 13:19:57 +0200
From: @bartscheers
I don't know, probably depends on the compiler.
So we have to do an explicit truncate/round/ceil before casting.
## Comment 18861
Date: 2013-06-18 15:47:17 +0200
From: @sjoerdmullender
This is what the standard (SQL 2008) says:
6.12 <cast specification>
[...]
8) If TD is exact numeric, then
Case:
a) If SD is exact numeric or approximate numeric, then
Case:
i) If there is a representation of SV in the data type TD that does not lose any leading significant digits after rounding or truncating if necessary, then TV is that representation. The choice of whether to round or truncate is implementation-defined.
(TD is the target type, SD is the source type.)
Note the last sentence.
This is the case that matches the use case here.
In other words, technically what we're doing is ok. It may not be pretty to have different results for casting from double to integer vs. from decimal to integer.
| Cast value to integer gives wrong result | https://api.github.com/repos/MonetDB/MonetDB/issues/3310/comments | 0 | 2020-11-30T12:32:22Z | 2024-06-27T12:00:16Z | https://github.com/MonetDB/MonetDB/issues/3310 | 753,440,576 | 3,310 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-17 14:50:31 +0200
From: Justin Paston-Cooper <<justin>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-07-31 13:56:30 +0200
## Comment 18854
Date: 2013-06-17 14:50:31 +0200
From: Justin Paston-Cooper <<justin>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.36 Safari/537.36
Build Identifier:
The delimiters used were '|','|\n'. The problem probably lies in the fact that the field separator is a prefix of the line separator.
Reproducible: Always
### Steps to Reproduce:
1. Valid CSV file with delimiters '|','|\n'.
2. copy into clustering_info from '/export/scratch1/justin/DB/tpch-data/dataGen/clusteringInfo.csv' using delimiters '|','|\n';
### Actual Results:
failed to import table
## Comment 18907
Date: 2013-07-08 11:47:13 +0200
From: @sjoerdmullender
This is not a client problem but a SQL problem.
## Comment 18967
Date: 2013-07-31 13:56:30 +0200
From: @njnes
To see the difference between end of file/stream, we indeed require a (complete) row
seperator also at the end of the last row.
| mclient does not load CSVs that do not have newline after last entry | https://api.github.com/repos/MonetDB/MonetDB/issues/3309/comments | 0 | 2020-11-30T12:32:20Z | 2024-06-28T07:23:21Z | https://github.com/MonetDB/MonetDB/issues/3309 | 753,440,546 | 3,309 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-17 02:36:19 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @mlkersten
Last updated: 2019-01-21 16:56:55 +0100
## Comment 18851
Date: 2013-06-17 02:36:19 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.20 Safari/537.36
Build Identifier:
copy (select * from tables order by id) into '/tmp/test.txt';
syntax error, unexpected ORDER, expecting INTERSECT or EXCEPT or UNION or ')' in: "copy (select * from tables order"
Reproducible: Always
MonetDB 5 server v11.15.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18852
Date: 2013-06-17 11:35:34 +0200
From: @sjoerdmullender
Not a bug.
## Comment 18862
Date: 2013-06-19 15:06:18 +0200
From: @mlkersten
SQL 2008 functionality:
The ORDER BY clause is not valid in views, inline functions, derived tables, and subqueries
## Comment 18863
Date: 2013-06-19 15:20:02 +0200
From: @skinkie
It is likely that it is related to their statement in the SELECT INTO functionionality:
"Specifying an ORDER BY clause does not guarantee the rows are inserted in the specified order."
## Comment 26823
Date: 2019-01-21 16:56:55 +0100
From: @sjoerdmullender
The ORDER BY clause can nowadays be used in subqueries, including the COPY query INTO file.
| copy into doesn't allow order by | https://api.github.com/repos/MonetDB/MonetDB/issues/3308/comments | 0 | 2020-11-30T12:32:17Z | 2024-06-27T12:00:14Z | https://github.com/MonetDB/MonetDB/issues/3308 | 753,440,510 | 3,308 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-16 23:13:52 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes
Last updated: 2013-09-27 13:47:15 +0200
## Comment 18849
Date: 2013-06-16 23:13:52 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.20 Safari/537.36
Build Identifier:
I'm currently trying to run some analysis on a table of the following structure; data is available.
CREATE TABLE "sys"."kv6_import" (
"receive" TIMESTAMP NOT NULL,
"message" TIMESTAMP NOT NULL,
"vehicle" TIMESTAMP NOT NULL,
"messagetype" VARCHAR(10) NOT NULL,
"operatingday" DATE NOT NULL,
"dataownercode" VARCHAR(10) NOT NULL,
"lineplanningnumber" VARCHAR(10),
"journeynumber" INTEGER NOT NULL,
"reinforcementnumber" INTEGER NOT NULL,
"userstopcode" VARCHAR(10),
"passagesequencenumber" INTEGER,
"distancesincelastuserstop" INTEGER,
"punctuality" INTEGER,
"rd_x" VARCHAR(11),
"rd_y" VARCHAR(11),
"blockcode" INTEGER,
"vehiclenumber" INTEGER,
"wheelchairaccessible" VARCHAR(5),
"source" VARCHAR(10) NOT NULL,
"numberofcoaches" INTEGER
);
At this moment I have loaded 10 * 10^6 rows - it is about 3 days of data. A very simple question I would like to ask the database:
How many lines were actually monitored given the days available in the database. Other SQL solutions offer SELECT COUNT(DISTINCT column1,columnN)), MonetDB doesn't, so I would rewrite my query in the following structure;
select count(*), dataownercode, lineplanningnumber, operatingday from (select distinct dataownercode, lineplanningnumber, operatingday from kv6_import) as x group by dataownercode, lineplanningnumber, operatingday;
The performance is poor - no results - I have killed the database server over it. Explain as attached. I have also tried to only run the subquery which also doesn't result in output given a reasonable time.
Since MonetDB at first sight doesn't support the count distinct on multiple columns, some TSQL website suggested to use column concat, with a slightly different syntax MonetDB gives a very acceptable performance 2826 tuples (13.2s).
select count(distinct dataownercode||lineplanningnumber||operatingday), dataownercode, lineplanningnumber, operatingday from kv6_import group by dataownercode, lineplanningnumber, operatingday;
Although my implementation cuts edges, adding a unique separator would in fact implement the more common syntax.
What remains is why the select distinct is slow in the first place.
Reproducible: Always
MonetDB 5 server v11.15.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18850
Date: 2013-06-16 23:15:07 +0200
From: @skinkie
Created attachment 203
Explain for slow select distinct
> Attached file: [explainselect.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3307_explainselect.txt_203) (text/plain, 9202 bytes)
> Description: Explain for slow select distinct
## Comment 18877
Date: 2013-06-22 17:17:51 +0200
From: @njnes
Could you send the ddl statements of your query. Also could you try the performance of the distinct, using first numbers (preferably almost unique first) and later strings?
## Comment 18878
Date: 2013-06-22 17:19:23 +0200
From: @njnes
why is lineplanning'number' not a number? Anyway start with date followed by lineplanning.
## Comment 18881
Date: 2013-06-22 23:39:11 +0200
From: @skinkie
Created attachment 207
Trace of date-first
Niels; I have just tried your suggestion by moving the date to the front. The performance is awesome. 2s cold, to 1.4s hot.
select distinct operatingday, dataownercode, lineplanningnumber from kv6_import limit 10;
I have attached the trace of this query. I have validated that moving operatingday to the left again kills the performance.
The reasoning regarding lineplanningnumber is the following: typically the LinePlanningNumber (in Dutch: systeemnummer) is used to identify an individual line. What actually occurs much is that this value is the denormalised representation of the organisational unit (typically the area) and the public linenumber. So for example for Connexxion in the Schiphol area the LinePlanningNumber would be M190.
The reason why the RD coordinates are not integers are sadly due to some very bad data quality. We now prefer to do analyses on what is actually received.
> Attached file: [trace-datefirst.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3307_trace-datefirst.txt_207) (text/plain, 16626 bytes)
> Description: Trace of date-first
## Comment 18882
Date: 2013-06-22 23:45:25 +0200
From: @skinkie
Created attachment 208
Trace of date second
Sounds also pretty handly to be able to compare the performance of this query;
select distinct dataownercode, operatingday, lineplanningnumber from kv6_import limit 10;
> Attached file: [trace-datesecond.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3307_trace-datesecond.txt_208) (text/plain, 16603 bytes)
> Description: Trace of date second
## Comment 18883
Date: 2013-06-23 10:00:49 +0200
From: @njnes
basically we should optimize the order of the distinct. This calls for an extension of the relational optimizer.
## Comment 18884
Date: 2013-06-23 11:28:51 +0200
From: @skinkie
Are you thinking in the direction of finding/storing the column with the most unique values so the number of bins are known?
## Comment 18885
Date: 2013-06-23 11:41:18 +0200
From: @njnes
For group by's we allready reorder the groupby expressions using the rules' of thumb
## Comment 18886
Date: 2013-06-23 11:44:32 +0200
From: @njnes
For group by's we allready reorder the groupby expressions using the rules' of thumb
ordered columns first.
fixed size before variable sized
small size types before larger types
This could indeed be improved using statistics on the data.
## Comment 18887
Date: 2013-06-23 11:45:02 +0200
From: @njnes
So for now I'm looking into rewriting the multi column distinct into a group by.
## Comment 18888
Date: 2013-06-23 11:58:11 +0200
From: @njnes
it seems the (distinct c1, c2 etc) is a mysql extension. So for now at most a feature request.
## Comment 18889
Date: 2013-06-23 12:00:27 +0200
From: @skinkie
Yes, and PostgreSQL. Should I file a separate bug for that?
## Comment 18894
Date: 2013-06-26 13:48:40 +0200
From: @njnes
The distinct is now rewritten into a group by, for which we automatically reorder the group by expressions. This should solve the performance problems.
| distinct multicolumn performance and implementation suggestion for count distinct | https://api.github.com/repos/MonetDB/MonetDB/issues/3307/comments | 0 | 2020-11-30T12:32:14Z | 2024-06-27T12:00:13Z | https://github.com/MonetDB/MonetDB/issues/3307 | 753,440,471 | 3,307 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-15 00:05:58 +0200
From: Tim H. <<monetdb.bug.reporter>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-06-16 14:45:53 +0200
## Comment 18842
Date: 2013-06-15 00:05:58 +0200
From: Tim H. <<monetdb.bug.reporter>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0
Build Identifier:
The mserver5 process segfaults when I run the following statement in the mserver5 console: sql.evalAlgebra("select id from sys._columns;",false);
Reproducible: Always
### Steps to Reproduce:
1. Run: mserver5 --dbpath="/opt/farm/db" --set gdk_nr_threads="2" --set monet_daemon="no"
2. In the mserver5 console enter: sql.evalAlgebra("select id from sys._columns;",false);
### Actual Results:
Segmentation fault
### Expected Results:
Not sure
gdb output:
Program received signal SIGSEGV, Segmentation fault.
0x00007fa525e24575 in RAstatement (cntxt=0x1734410, mb=0x1767d70, stk=0x2c0c210, pci=0x176ac60) at sql.mx:7620
7620 if (!m->sa)
(gdb) where
0 0x00007fa525e24575 in RAstatement (cntxt=0x1734410, mb=0x1767d70, stk=0x2c0c210, pci=0x176ac60) at sql.mx:7620
1 0x00007fa5329fbbfe in runMALsequence (cntxt=0x1734410, mb=0x1767d70, startpc=1, stoppc=0, stk=0x2c0c210, env=0x2c0c210, pcicaller=0x0) at mal_interpreter.c:650
2 0x00007fa5329fac54 in runMAL (cntxt=0x1734410, mb=0x1767d70, mbcaller=0x0, env=0x2c0c210) at mal_interpreter.c:379
3 0x00007fa532a27029 in MALengine (c=0x1734410) at mal_session.c:620
4 0x00007fa532a2529f in runPhase (c=0x1734410, phase=4) at mal_scenario.c:522
5 0x00007fa532a2546f in runScenarioBody (c=0x1734410) at mal_scenario.c:567
6 0x00007fa532a25584 in runScenario (c=0x1734410) at mal_scenario.c:586
7 0x00007fa532a26492 in MSserveClient (dummy=0x1734410) at mal_session.c:431
8 0x0000000000403692 in main (argc=10, av=0x7fff78b94f88) at mserver5.c:664
## Comment 18843
Date: 2013-06-15 09:53:58 +0200
From: @njnes
evalAlgebra expects a string with relational algebra, ie not sql.
## Comment 18844
Date: 2013-06-16 11:49:05 +0200
From: @njnes
we now correctly return when there is no sql context
## Comment 18845
Date: 2013-06-16 14:45:53 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [794344ec919b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=794344ec919b) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=794344ec919b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=794344ec919b)
Changeset description:
fixed crash in RAstatement, bug #3306
fixed bat leak in create table.
| mserver5 segfault while running sql.evalAlgebra | https://api.github.com/repos/MonetDB/MonetDB/issues/3306/comments | 0 | 2020-11-30T12:32:12Z | 2024-06-27T12:00:12Z | https://github.com/MonetDB/MonetDB/issues/3306 | 753,440,440 | 3,306 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-11 02:46:59 +0200
From: Angelo <<oangelo>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @lsidir, @njnes
Last updated: 2013-07-31 13:48:41 +0200
## Comment 18814
Date: 2013-06-11 02:46:59 +0200
From: Angelo <<oangelo>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
Build Identifier:
Depending on the query, a field may be filled or may be null for the same line!
Reproducible: Always
### Steps to Reproduce:
1. Conect to the database using mclient
2. select id,instalacao, descricao_do_tipo_de_nota from notas_c where instalacao=412307404;
3. select id,instalacao, descricao_do_tipo_de_nota from notas_c where instalacao=412307404 limit 12;
### Actual Results:
Note the missing data on the first query. However, if a limit is added, there is no blank lines.
sql>select id,instalacao, descricao_do_tipo_de_nota from notas_c where instalacao=412307404;
+-------------+------------+---------------------------+
| id | instalacao | descricao_do_tipo_de_nota |
+=============+============+===========================+
| 35004675 | 412307404 | |
| 10009362195 | 412307404 | |
| 10009372721 | 412307404 | |
| 10009455607 | 412307404 | |
| 10010449356 | 412307404 | |
| 10010832683 | 412307404 | |
| 10011114747 | 412307404 | |
| 10011308855 | 412307404 | |
| 10011475191 | 412307404 | |
| 10012702114 | 412307404 | |
| 10014234776 | 412307404 | |
| 10014271409 | 412307404 | Religação BT |
+-------------+------------+---------------------------+
12 tuples (29.482ms)
sql>select id,instalacao, descricao_do_tipo_de_nota from notas_c where instalacao=412307404 limit 12;
+-------------+------------+---------------------------+
| id | instalacao | descricao_do_tipo_de_nota |
+=============+============+===========================+
| 35004675 | 412307404 | VerifTensão Fornec |
| 10009362195 | 412307404 | Vistoria BT |
| 10009372721 | 412307404 | Reclamação |
| 10009455607 | 412307404 | Modif/Manut Mediç BT |
| 10010449356 | 412307404 | Acompanhamento BT |
| 10010832683 | 412307404 | Modif/Manut Mediç BT |
| 10011114747 | 412307404 | Reclamação |
| 10011308855 | 412307404 | Modif/Manut Mediç BT |
| 10011475191 | 412307404 | Alterar Carga BT |
| 10012702114 | 412307404 | Corte BT |
| 10014234776 | 412307404 | Corte BT |
| 10014271409 | 412307404 | Religação BT |
+-------------+------------+---------------------------+
12 tuples (12.974ms)
### Expected Results:
I would expect the same results for both queries, since there is only 12 results, so, limit 12 should make no difference!
MonetDB Database Server Toolkit v1.1 (Feb2013-SP2)
sql>\d notas_c
CREATE TABLE "sys"."notas_c" (
"id" BIGINT,
"instalacao" BIGINT,
"data_de_criacao_da_nota" DATE,
"data_do_encerramento_da_nota" DATE,
"tipo_de_nota_de_servico" VARCHAR(32),
"descricao_do_tipo_de_nota" VARCHAR(256),
"codificacao_da_nota" VARCHAR(32),
"descricao_da_codificacao_da_nota" VARCHAR(256),
"data_fim_da_avaria" DATE,
"status_do_usuario" VARCHAR(32),
"descricao_do_status_do_usuario" VARCHAR(256)
);
## Comment 18815
Date: 2013-06-11 15:09:33 +0200
From: @lsidir
I tried to reproduce this bug but I could not. Could you also please send us a sample of the data? For example a csv file containing those 12 rows?
Thank you very much.
## Comment 18816
Date: 2013-06-11 15:21:42 +0200
From: Angelo <<oangelo>>
Created attachment 202
A sample of the data separated by ;
A sample data to possibly reproduce the bug.
> Attached file: [sample.csv](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3305_sample.csv_202) (text/plain, 1564 bytes)
> Description: A sample of the data separated by ;
## Comment 18818
Date: 2013-06-12 10:18:39 +0200
From: @njnes
There are no keys defined on the table?
## Comment 18832
Date: 2013-06-12 14:19:19 +0200
From: @lsidir
(In reply to comment 3)
> There are no keys defined on the table?
no there are no keys defined.
I was unable to reproduce this problem.
## Comment 18835
Date: 2013-06-12 15:55:27 +0200
From: Angelo <<oangelo>>
The table has few milions of rows, I can not send it all because of the size and NDA. Nevertheless, I have imported the table again, and makes no difference, the problem still there.
The odd thing is that the data is there, on the csv file, and when a limit is added to the query, the right result is returned. As a result, I think, the problem is the data retrieval!
In MySQL, adding a limit to the query only changes the amount of data to be printed on the screen. Here, it seems that a limit changes the way the query is done. This is also strange...
If I ask the data of a specific "id", the data does come right:
sql>select id,instalacao, descricao_do_tipo_de_nota from notas_c where id=35004675;
+----------+------------+---------------------------+
| id | instalacao | descricao_do_tipo_de_nota |
+==========+============+===========================+
| 35004675 | 412307404 | VerifTensão Fornec |
+----------+------------+---------------------------+
1 tuple (325.994ms)
## Comment 18853
Date: 2013-06-17 12:31:35 +0200
From: @sjoerdmullender
This problem looks a lot like bug #3261 which was supposedly fixed in Feb2013-SP2.
Can you recheck the version of mserver5 you're using? Please paste the output of "mserver5 --version" into the bug report.
## Comment 18855
Date: 2013-06-17 21:28:12 +0200
From: Angelo <<oangelo>>
The problem persist on SP2.
$ mserver5 --version
MonetDB 5 server v11.15.7 "Feb2013-SP2" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 62.9GiB available memory, 16 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.30)
openssl: OpenSSL 1.0.1c 10 May 2012 (compiled with OpenSSL 1.0.1c 10 May 2012)
libxml2: 2.8.0 (compiled with 2.8.0)
Compiled by: root@dev.monetdb.org (x86_64-pc-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18880
Date: 2013-06-22 17:58:00 +0200
From: @njnes
Angelo we can't repeat your problem with the limited data sample. Could you try to find a a smal sample which also on your system triggers the problem?
## Comment 18901
Date: 2013-07-03 13:11:52 +0200
From: @njnes
could you try with sp3?
## Comment 18904
Date: 2013-07-05 18:29:00 +0200
From: Angelo <<oangelo>>
Same behavior with SP3!
## Comment 18965
Date: 2013-07-31 13:48:41 +0200
From: @njnes
we will need more input (data) as with the small example the problem doesn't trigger
| Inconsistency in select, missing data depending on the where clause! | https://api.github.com/repos/MonetDB/MonetDB/issues/3305/comments | 0 | 2020-11-30T12:32:09Z | 2024-06-27T12:00:11Z | https://github.com/MonetDB/MonetDB/issues/3305 | 753,440,408 | 3,305 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-11 02:24:29 +0200
From: v_c
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes
Last updated: 2013-06-13 11:17:31 +0200
## Comment 18813
Date: 2013-06-11 02:24:29 +0200
From: v_c
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0
Build Identifier:
I want to batch load a table from a text file. The text file contains umlauts. It says it inserted but when I query the table, it returns the correct tuple count but also 'write error' instead of the values.
Reproducible: Always
### Steps to Reproduce:
1.Create a file test.txt containing "Köpis"
2.file -bi file.txt
3.iconv -f ISO-8859-1 -t UTF-8 test.txt > test_file.txt
4.create table test_table (afield varchar(255));
5.copy into test_table from '/tmp/test_file.txt';
6.select * from test_table
### Actual Results:
sql>select * from test_table;
+--------------------------+
| afield|
+==========================+
|4 tuples (0.972ms)
write error
I inserted 4 values.
### Expected Results:
sql>select * from test_table;
+--------------------------+
| afield|
|"Köpis|
+==========================+
## Comment 18817
Date: 2013-06-12 10:14:52 +0200
From: @njnes
I cannot repeat the problem on linux.
Which client are you using, did you compile with iconv support enabled?
## Comment 18837
Date: 2013-06-12 20:06:30 +0200
From: v_c
It is odd. I repeated all my steps again today and it succeeded also.
## Comment 18839
Date: 2013-06-13 11:17:31 +0200
From: @sjoerdmullender
The write error happens if mclient cannot convert the UTF-8 that it gets from the server to the terminal's encoding. It means you are trying to have mclient print a character your terminal doesn't support.
| "Write error" after querying table loaded using Copy Into | https://api.github.com/repos/MonetDB/MonetDB/issues/3304/comments | 0 | 2020-11-30T12:32:07Z | 2024-06-28T07:23:21Z | https://github.com/MonetDB/MonetDB/issues/3304 | 753,440,379 | 3,304 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-08 15:38:47 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:47:58 +0200
## Comment 18798
Date: 2013-06-08 15:38:47 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36
Build Identifier:
I got this assertion while trying to write and commit on the same table from 2 different mclient sessions. I would have expected a "COMMiT failed" error on the second commit.
2013-06-08 15:29:06 ERR equip_tnw_20130531_01[11909]: mserver5: /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/storage/bat/bat_storage.c:1451: tr_update_delta: Assertion `(((cur)->U->count) + ((ins)->U->count)) == (obat->cnt + (((((ins)->U->first <= (((BUN) 9223372036854775807LL) - 1)) ? (void) (0) : __assert_fail ("(ins)->U->first <= (((BUN) 9223372036854775807LL) - 1)", "/opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/storage/bat/bat_storage.c", 1451, __PRETTY_FUNCTION__)), (((ins)->U->count <= (((BUN) 9223372036854775807LL) - 1)) ? (void) (0) : __assert_fail ("(ins)->U->count <= (((BUN) 9223372036854775807LL) - 1)", "/opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/storage/bat/bat_storage.c", 1451, __PRETTY_FUNCTION__)), (((ins)->U->count <= (((BUN) 9223372036854775807LL) - 1) - (ins)->U->first) ? (void) (0) : __assert_fail ("(ins)->U->count <= (((BUN) 9223372036854775807LL) - 1) - (ins)->U->first", "/opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/storage/bat/bat_storage.c", 1451, __PRETTY_FUNCTION__)), (ins)->U->first + (ins)->U->count) - ins->U->inserted))' failed.
2
Reproducible: Always
### Steps to Reproduce:
1. open 2 mclient sessions
2. START TRANSACTION on both, add a tuple on the same table, from both
3. COMMIT on both
### Actual Results:
The second COMMIT triggers the assertion above
### Expected Results:
"COMMIT failed" error
$ mserver5 --version
MonetDB 5 server v11.15.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.31 2012-07-06 (compiled with 8.31)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e-fips 11 Feb 2013)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: roberto@photon.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64
Tip:
changeset: 47894:11a7d8d94a7b
branch: Feb2013
user: Niels Nes <niels@cwi.nl>
date: Fri Jun 07 15:49:07 2013 +0200
summary: fixed bug #3269, ie out of bounds write.
## Comment 18846
Date: 2013-06-16 16:12:36 +0200
From: @njnes
fixed, ie appends are (again) also reads on the table/column.
## Comment 18847
Date: 2013-06-16 16:14:33 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2a53b540e596](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2a53b540e596) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a53b540e596](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a53b540e596)
Changeset description:
fixed problem with concurrent appends (bug #3303)
fixed the test for join_over_multitable_using_index
| Assertion on concurrent write | https://api.github.com/repos/MonetDB/MonetDB/issues/3303/comments | 0 | 2020-11-30T12:32:04Z | 2024-06-27T12:00:09Z | https://github.com/MonetDB/MonetDB/issues/3303 | 753,440,345 | 3,303 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-07 21:57:55 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:47:59 +0200
## Comment 18797
Date: 2013-06-07 21:57:55 +0200
From: @drstmane
After recent changes, test sql/test/BugTracker-2011/Tests/exists-select.Bug-2933.sql fails with
"
ERROR = !Subquery result missing
"
cf.,
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47763:11a7d8d94a7b&target=GNU-Darwin-i386-propcheck&module=sql&test=sql%2Ftest%2FBugTracker-2011%2Fexists-select.Bug-2933&which=err
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47763:11a7d8d94a7b&target=GNU-Darwin-i386-propcheck&module=sql&test=sql%2Ftest%2FBugTracker-2011%2Fexists-select.Bug-2933&which=out
## Comment 18800
Date: 2013-06-09 14:18:37 +0200
From: @njnes
fixed, some more table name fixes.
| test exists-select.Bug-2933.sql fails after recent changes | https://api.github.com/repos/MonetDB/MonetDB/issues/3302/comments | 0 | 2020-11-30T12:32:02Z | 2024-06-27T12:00:08Z | https://github.com/MonetDB/MonetDB/issues/3302 | 753,440,310 | 3,302 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-06 21:35:55 +0200
From: Ben Reilly <<ben>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2016-04-11 11:45:38 +0200
## Comment 18787
Date: 2013-06-06 21:35:55 +0200
From: Ben Reilly <<ben>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36
Build Identifier:
When comparing with a CHAR type, the strings are not padded with trailing spaces, as they should be according to the SQL-92 standard (I couldn't find a more recent specification, but I assume this hasn't changed). For example, 'ABC' does not match 'ABC ' in MonetDB, whereas it should.
I experienced this error while running TPC-H: query 3 compares the c_mktsegment column with the string 'MACHINERY'. It appears that the loader I use actually pads the strings manually, so MonetDB does not match these values because they're stored as 'MACHINERY ' in the DB, and the comparison string is not padded to the same length.
Reproducible: Always
### Steps to Reproduce:
sql>CREATE TABLE strtest (str CHAR(10));
sql>INSERT INTO strtest VALUES ('NOPAD');
sql>INSERT INTO strtest VALUES ('PAD ');
sql>SELECT str FROM strtest WHERE str = 'NOPAD';
+------------+
| str |
+============+
| NOPAD |
+------------+
1 tuple (0.892ms)
sql>SELECT str FROM strtest WHERE str = 'NOPAD ';
+-----+
| str |
+=====+
+-----+
0 tuples (0.286ms)
sql>SELECT str FROM strtest WHERE str = 'PAD';
+-----+
| str |
+=====+
+-----+
0 tuples (0.279ms)
sql>SELECT str FROM strtest WHERE str = 'PAD ';
+------------+
| str |
+============+
| PAD |
+------------+
1 tuple (0.291ms)
### Expected Results:
From the SQL-92 specification, Section 8, General Rule 3
---
The comparison of two character strings is determined as follows:
a) If the length in characters of X is not equal to the length
in characters of Y, then the shorter string is effectively
replaced, for the purposes of comparison, with a copy of
itself that has been extended to the length of the longer
string by concatenation on the right of one or more pad char-
acters, where the pad character is chosen based on CS. If
CS has the NO PAD attribute, then the pad character is an
implementation-dependent character different from any char-
acter in the character set of X and Y that collates less
than any string under CS. Otherwise, the pad character is a
<space>.
## Comment 18819
Date: 2013-06-12 10:22:01 +0200
From: @njnes
although this is indeed part of the sql standard, we have no plans to change the current support for fixed sized strings. I changed this to a 'enhancement' request.
In the TPC-H standard the strings are all 'varchar' I believe.
| CHAR comparisons do not pad strings of different lengths | https://api.github.com/repos/MonetDB/MonetDB/issues/3301/comments | 0 | 2020-11-30T12:32:00Z | 2024-06-28T13:40:11Z | https://github.com/MonetDB/MonetDB/issues/3301 | 753,440,291 | 3,301 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-06 19:53:36 +0200
From: Tim Harrington <<tharrington>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:47:59 +0200
## Comment 18786
Date: 2013-06-06 19:53:36 +0200
From: Tim Harrington <<tharrington>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0
Build Identifier:
Using mclient log in as a non-admin user and connect to a database. Run the following command: explain select * from sys.storagemodel(); This causes a SEGFAULT in mserver5.
Reproducible: Always
### Steps to Reproduce:
1.Using mclient log in as a non-admin user and connect to a database.
2. Run the following command: explain select * from sys.storagemodel();
### Actual Results:
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.15.8 (unreleased), 'db0'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>explain select * from sys.storagemodel();
Connection terminated
### Expected Results:
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.15.8 (unreleased), 'db0'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>explain select * from sys.storagemodel();
(the mal plan)
(gdb) where
0 0x00007fffea20a9e6 in backend_call (be=0x7fffa80d2800, c=0x66c558, cq=0x7fffa80fc190) at sql_gencode.c:2425
1 0x00007fffea1e5104 in SQLparser (c=0x66c558) at sql_scenario.c:1771
2 0x00007ffff78b747b in runPhase (c=0x66c558, phase=1) at mal_scenario.c:522
3 0x00007ffff78b75aa in runScenarioBody (c=0x66c558) at mal_scenario.c:558
4 0x00007ffff78b7754 in runScenario (c=0x66c558) at mal_scenario.c:586
5 0x00007ffff78b8637 in MSserveClient (dummy=0x66c558) at mal_session.c:431
6 0x00007ffff4eda851 in start_thread () from /lib64/libpthread.so.0
7 0x00007ffff4c2890d in clone () from /lib64/libc.so.6
(gdb) l
2420 InstrPtr q;
2421 MalBlkPtr mb = c->curprg->def;
2422
2423 q = newStmt1(mb, userRef, cq->name);
2424 /* cached (factorized queries return bit??) */
2425 if (getInstrPtr(((Symbol)cq->code)->def, 0)->token == FACTORYsymbol ) {
2426 setVarType(mb, getArg(q, 0), TYPE_bit);
2427 setVarUDFtype(mb,getArg(q,0));
2428 } else {
2429 setVarType(mb, getArg(q, 0), TYPE_void);
(gdb) p getInstrPtr(((Symbol)cq->code)->def, 0)
No symbol "getInstrPtr" in current context.
(gdb) p (Symbol)cq->code
$1 = (struct SYMDEF *) 0x0
(gdb) p (Symbol)cq
$2 = (struct SYMDEF *) 0x7fffa80fc190
(gdb)
## Comment 18791
Date: 2013-06-07 14:57:46 +0200
From: @njnes
the crash is easily solved. But the real problem is a bit deeper, ie the handling of access rights with functions seems to cause this.
## Comment 18794
Date: 2013-06-07 15:49:15 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [5751d58f996d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5751d58f996d) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5751d58f996d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5751d58f996d)
Changeset description:
more defensive code. Partial fix for bug #3300
## Comment 18811
Date: 2013-06-10 18:44:05 +0200
From: @njnes
cleaned up the error handling of nested function calls. The nested function (storagemodel) gives an access error when called by an non admin user.
## Comment 18812
Date: 2013-06-10 18:52:11 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [cecb54de54c5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cecb54de54c5) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cecb54de54c5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cecb54de54c5)
Changeset description:
fixed bug #3300. The nested functions error handling was improved.
## Comment 18840
Date: 2013-06-13 11:28:39 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b441b033c4b7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b441b033c4b7) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b441b033c4b7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b441b033c4b7)
Changeset description:
Adapt filter for test sql/test/BugTracker-2013/psm_functions_and_accessrights.Bug-3300.
| explain select from storagemodel causes mserver5 to segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/3300/comments | 0 | 2020-11-30T12:31:57Z | 2024-06-27T12:00:06Z | https://github.com/MonetDB/MonetDB/issues/3300 | 753,440,255 | 3,300 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-06 11:38:14 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-06-20 11:22:42 +0200
## Comment 18782
Date: 2013-06-06 11:38:14 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
Build Identifier:
This is hard to make reproducible, but we have a rather long process that behaves like this:
repeat n times: {
new JDBC connection
repeat k times {
START TRANSACTION;
<CREATE, INSERT, ALTER, etc.. >
COMMIT;
}
close JDBC connection
}
Resident memory and swap space are completely filled after a few minutes (say after n=20) and mserver gets killed by the OS.
Notice that:
- This happens on Feb2013 and does not happen on Jul2012
- This does not happen if mserver is stopped and started at every iteration of the external cycle above.
Logs? Delta bats?
Reproducible: Always
(N.B. the released Feb2012_SP2 behaves the same way)
$ mserver5 --version
MonetDB 5 server v11.15.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.31 2012-07-06 (compiled with 8.31)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e-fips 11 Feb 2013)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: roberto@photon.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18824
Date: 2013-06-12 12:02:55 +0200
From: @njnes
Is this with one active client?
## Comment 18825
Date: 2013-06-12 12:06:00 +0200
From: @swingbit
a new client connection is opened and closed at every external loop
## Comment 18826
Date: 2013-06-12 12:08:56 +0200
From: @njnes
Could you verify this using gdb and check if
store_nr_active <= 1
## Comment 18827
Date: 2013-06-12 12:09:21 +0200
From: @njnes
the sequence only has create/alter and insert
ie no selects, update or deletes?
## Comment 18834
Date: 2013-06-12 14:51:49 +0200
From: @swingbit
I've actually changed the sequence as a workaround now...
About the store_nr_active, it should be the same as before, as the general loop and how the connections are made didn't change. I saw mostly store_nr_active=1 and once store_nr_active=2.
About the queries, what happens at every iteration varies much, but the pattern that caused the problem was (simplified):
jdbc connection {
START TRANSACTION;
DROP TABLE x;
CREATE TABLE x AS SELECT * from y ORDER BY a WITH DATA;
COMMIT;
}
jdbc connection {
START TRANSACTION;
INSERT INTO y SELECT ... FROM x ...
COMMIT;
}
jdbc connection {
START TRANSACTION;
UPDATE y ... FROM x ...
COMMIT;
}
jdbc connection {
START TRANSACTION;
DROP TABLE x;
CREATE TABLE x AS SELECT * from y ORDER BY a WITH DATA;
COMMIT;
}
etc... for several times (with more tables and operations).
That dropping and recreating X was the problem. This cyclic process got slower and slower every time "x" was re-materialized, and finally went out of memory. So it looks like delta bats grew bigger and bigger.
## Comment 18836
Date: 2013-06-12 16:15:51 +0200
From: @njnes
great found one bat leak (subsorting). Does your loop also leak when you do not sort/order by the created table.
## Comment 18841
Date: 2013-06-14 12:58:12 +0200
From: @njnes
did this fix your problem?
## Comment 18868
Date: 2013-06-20 11:22:42 +0200
From: @swingbit
It seems so. Marked fixed thanks.
| Out of memory after several transactions | https://api.github.com/repos/MonetDB/MonetDB/issues/3299/comments | 0 | 2020-11-30T12:31:55Z | 2024-06-27T12:00:05Z | https://github.com/MonetDB/MonetDB/issues/3299 | 753,440,232 | 3,299 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-05 15:44:46 +0200
From: Christian Braun <<hcb>>
To: SQL devs <<bugs-sql>>
Version: 11.15.19 (Feb2013-SP6)
CC: @mlkersten, @njnes
Last updated: 2014-02-20 15:03:08 +0100
## Comment 18779
Date: 2013-06-05 15:44:46 +0200
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0
Build Identifier:
Hello,
i am having these GDKmmap failure / recovery message in the logfile. Is this a bug?
The database takes 30 minutes to startup and become available. It contains 4TB of data. The server has 256GB RAM. Is the startup time related to the database size? Is it normal to take that long?
Thank you for any help,
Christian Braun.
Debian 6.0 with version:
ii monetdb5-server 11.15.7-20130426 MonetDB database server version 5
2013-06-05 14:37:03 MSG merovingian[63122]: Merovingian 1.7 (Feb2013-SP2) starting
2013-06-05 14:37:03 MSG merovingian[63122]: monitoring dbfarm /var/monetdb/dbfarm
2013-06-05 14:37:03 MSG merovingian[63122]: accepting connections on TCP socket 0.0.0.0:50000
2013-06-05 14:37:03 MSG merovingian[63122]: accepting connections on UNIX domain socket /tmp/.s.monetdb.50000
2013-06-05 14:37:03 MSG discovery[63122]: listening for UDP messages on 0.0.0.0:50000
2013-06-05 14:37:03 MSG control[63122]: accepting connections on UNIX domain socket /tmp/.s.merovingian.50000
2013-06-05 14:37:06 MSG control[63122]: (local): served status list
2013-06-05 14:37:06 MSG merovingian[63122]: starting database 'db', up min/avg/max: 4s/1d/6w, crash average: 0.00 0.10 0.07 (321-315=6)
2013-06-05 14:37:07 MSG db[63137]: arguments: /usr/bin/mserver5 --dbpath=/var/monetdb/dbfarm/db --set merovingian_uri=mapi:monetdb://lhotse:50000/db --set mapi_open=false --set mapi_port=0 --set mapi_us
ock=/var/monetdb/dbfarm/db/.mapi.sock --set monet_vault_key=/var/monetdb/dbfarm/db/.vaultkey --set gdk_nr_threads=32 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-06-05 14:59:15 MSG db[63137]: MonetDB 5 server v11.15.7 "Feb2013-SP2"
2013-06-05 14:59:15 MSG db[63137]: Serving database 'db', using 32 threads
2013-06-05 14:59:15 MSG db[63137]: Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
2013-06-05 14:59:15 MSG db[63137]: Found 252.390 GiB available main-memory.
2013-06-05 14:59:15 MSG db[63137]: Copyright (c) 1993-July 2008 CWI.
2013-06-05 14:59:15 MSG db[63137]: Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
2013-06-05 14:59:15 MSG db[63137]: Visit http://www.monetdb.org/ for further information
2013-06-05 14:59:15 MSG db[63137]: Listening for UNIX domain connection requests on mapi:monetdb:///var/monetdb/dbfarm/db/.mapi.sock
2013-06-05 14:59:15 MSG db[63137]: GDKmmap(45613056) fails, try to free up space [memory in use=195224400,virtual memory in use=4937100485456]
2013-06-05 14:59:15 MSG db[63137]: GDKmmap(45613056) result [mem=185323792,vm=194498832]
2013-06-05 14:59:15 MSG db[63137]: GDKmmap: recovery ok. Continuing..
2013-06-05 14:59:15 MSG db[63137]: MonetDB/SQL module loaded
2013-06-05 14:59:15 MSG control[63122]: (local): started 'db'
Reproducible: Always
## Comment 18793
Date: 2013-06-07 15:22:51 +0200
From: @njnes
During startup the old logs need to be checked. This process may touch a lot of tables/columns which in your case could mean lots of data/IO. The MMAP failures indicate MonetDB is running out of memory. Are there really big tables which could explain this?
## Comment 18796
Date: 2013-06-07 16:34:08 +0200
From: Christian Braun <<hcb>>
There are 4 huge tables. The largest has 6.4 billion rows. The other tables are of modest size. What does this mean for the largest table? Queries seems to work fine on it.
Thank you,
Christian.
## Comment 18820
Date: 2013-06-12 10:25:25 +0200
From: @njnes
startup shouldn't be al that expensive. The mmap usage indicates some log rollforward is needed. Are you doing lots of updates?
## Comment 18828
Date: 2013-06-12 12:16:48 +0200
From: Christian Braun <<hcb>>
Yes, many updates. I load new data via copy into and then do a lot of updates to set extra columns. About 150 copy into and 15000 update statements on a daily basis.
## Comment 18829
Date: 2013-06-12 12:35:19 +0200
From: @njnes
Could right before the restart check how large the log files (monetdb5/dbfarm/dbname/sql_logs/sql/log*) are.
## Comment 18830
Date: 2013-06-12 12:38:10 +0200
From: Christian Braun <<hcb>>
ls /var/monetdb/dbfarm/db/sql_logs/sql/ -l
total 1036
-rw------- 1 monetdb monetdb 14 Jun 12 04:31 log
-rw------- 1 monetdb monetdb 2 May 22 2012 log.10585
-rw------- 1 monetdb monetdb 2 Jun 5 21:22 log.27162
-rw------- 1 monetdb monetdb 524308 Jun 12 05:04 log.27479
## Comment 18831
Date: 2013-06-12 12:43:57 +0200
From: @njnes
did a restart with these small logs take long?
## Comment 18833
Date: 2013-06-12 14:20:54 +0200
From: Christian Braun <<hcb>>
Yes, startup took 20 minutes.
## Comment 19065
Date: 2013-08-25 09:45:52 +0200
From: @njnes
I just tested (again) on a 256G machine with tpch sf 1000. And restarting takes
at most 3 sec. Do you have many tables?
## Comment 19066
Date: 2013-08-25 09:48:53 +0200
From: Christian Braun <<hcb>>
~4000 tables
## Comment 19068
Date: 2013-08-25 10:04:19 +0200
From: @mlkersten
A test for large cataloges can be found int
the test suite
BugTracker-2012/Tests/huge_table_update.Bug-2803.sql
Perhaps callgrind can give a hint on the performance loss culprit
## Comment 19069
Date: 2013-08-25 10:28:44 +0200
From: @mlkersten
running this script with 5000 updates over empty table with 5000 colums takes 10 min.
It could be expanded to work on non-empty tables to approach the case discussed in this bug report.
## Comment 19076
Date: 2013-08-25 22:38:43 +0200
From: @mlkersten
Created attachment 224
kcachegrind grab of top use
kcachegrind grab
> Attached file: [hugetable.tiff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3298_hugetable.tiff_224) (image/tiff, 99458 bytes)
> Description: kcachegrind grab of top use
## Comment 19077
Date: 2013-08-25 22:42:27 +0200
From: @mlkersten
Created attachment 225
List_find_column
80% of all cycles are spent in this code fragment
> Attached file: [list_find_column.tiff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3298_list_find_column.tiff_225) (image/tiff, 120556 bytes)
> Description: List_find_column
## Comment 19078
Date: 2013-08-26 08:46:25 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [eac781c321ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=eac781c321ce) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=eac781c321ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=eac781c321ce)
Changeset description:
Added insert into huge table test
This test could potentially be used to debug slow recovery
as reported in bug #3298
## Comment 19080
Date: 2013-08-26 20:19:31 +0200
From: @njnes
on restart the logs are indeed replayed. This used to be quick but a small change could lead to changes on files which now need to be flushed (which is
enforced using fsync/fdatasync). This may be very slow.
## Comment 19415
Date: 2013-12-11 16:42:42 +0100
From: @njnes
the test now takes 16sec (was 10Min). Seems time to close this bug.
## Comment 19624
Date: 2014-02-20 15:03:08 +0100
From: @sjoerdmullender
Jan2014 has been released.
| GDKmmap messages and monetdb start db takes very long | https://api.github.com/repos/MonetDB/MonetDB/issues/3298/comments | 0 | 2020-11-30T12:31:51Z | 2024-06-27T12:00:04Z | https://github.com/MonetDB/MonetDB/issues/3298 | 753,440,192 | 3,298 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-05 02:53:19 +0200
From: Ben Reilly <<ben>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: ben, @njnes
Last updated: 2013-07-03 08:48:00 +0200
## Comment 18778
Date: 2013-06-05 02:53:19 +0200
From: Ben Reilly <<ben>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36
Build Identifier:
When using a prepared statement that includes arithmetic on an 'int' parameter (e.g. "? - 20"), with operands that are in the range [-127,+127], the prepared statement converts the expression to the type 'tinyint', and limits the parameter accordingly to the 'tinyint' type.
So, for instance, "? - 20" will only accept 8-bit integers, but "? - 200" will accept any (16? 32? 64bit?) value.
Reproducible: Always
### Steps to Reproduce:
sql> CREATE TABLE ints ( val int );
sql> PREPARE INSERT INTO ints VALUES ( ? - 20 );
sql> EXEC 2(1000);
### Actual Results:
Error message:
EXEC: wrong type for argument 1 of prepared statement: smallint, expected tinyint
## Comment 18804
Date: 2013-06-09 20:14:42 +0200
From: @njnes
improved type handling in case of numerics.
## Comment 18805
Date: 2013-06-09 20:20:41 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [834adef227d0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=834adef227d0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=834adef227d0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=834adef227d0)
Changeset description:
fixed bug #3297. More general types are used in case of numerics.
| Data type changes when arithmetic in prepared statements. | https://api.github.com/repos/MonetDB/MonetDB/issues/3297/comments | 0 | 2020-11-30T12:31:49Z | 2024-06-27T12:00:03Z | https://github.com/MonetDB/MonetDB/issues/3297 | 753,440,154 | 3,297 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-02 17:37:49 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:48:01 +0200
## Comment 18770
Date: 2013-06-02 17:37:49 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:21.0) Gecko/20100101 Firefox/21.0
Build Identifier:
The test table_functions.sql has been added. When ran, it produces two type errors and misses the insertion of a tuple in the temporary table.
Reproducible: Always
### Actual Results:
sql>CREATE FUNCTION f1(i int) RETURNS TABLE (j int) BEGIN RETURN TABLE(SELECT i); END;
operation successful (20.375ms)
sql>CREATE FUNCTION f2(i int) RETURNS TABLE (j int) BEGIN RETURN TABLE(SELECT i UNION SELECT 2 * i); END;
operation successful (13.811ms)
sql>CREATE FUNCTION f3(i bigint) RETURNS TABLE (j int) BEGIN RETURN TABLE(SELECT i UNION SELECT 2 * i); END;
operation successful (13.805ms)
sql>CREATE FUNCTION f4(i int) RETURNS TABLE (j int) BEGIN RETURN TABLE(SELECT i UNION SELECT i); END;
operation successful (14.160ms)
sql>
sql>SELECT * FROM f1(1);
+------+
| j |
+======+
| 1 |
+------+
1 tuple (1.077ms)
sql>SELECT * FROM f2(3);
TypeException:user.f2[27]:RETURN type mismatch at type 'bat[:oid,:lng]'
TypeException:user.s2_1[3]:'user.f2' undefined in: _5:bat[:oid,:int] := user.f2(_4:int)
program contains errors
sql>SELECT * FROM f3(5);
TypeException:user.f3[27]:RETURN type mismatch at type 'bat[:oid,:lng]'
TypeException:user.s3_1[3]:'user.f3' undefined in: _5:bat[:oid,:int] := user.f3(_4:lng)
program contains errors
sql>SELECT * FROM f4(7);
+------+
| j |
+======+
| 7 |
+------+
1 tuple (1.543ms)
## Comment 18771
Date: 2013-06-02 19:30:54 +0200
From: @njnes
Indeed a type check is missing. The f4 should however return a single value, unless you change UNION into union ALL.
## Comment 18783
Date: 2013-06-06 19:26:19 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=52ed955b70c9) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9)
Changeset description:
fixed bug #3279 and 3278. We properly look up the order by columns.
And keep table names with all sub-relations.
Fixed bug #3296, ie fixed type checking on table returning functions.
| Type checking in table functions | https://api.github.com/repos/MonetDB/MonetDB/issues/3296/comments | 0 | 2020-11-30T12:31:47Z | 2024-06-27T12:00:02Z | https://github.com/MonetDB/MonetDB/issues/3296 | 753,440,129 | 3,296 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-06-01 08:32:17 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @mlkersten
Last updated: 2013-07-03 08:47:59 +0200
## Comment 18761
Date: 2013-06-01 08:32:17 +0200
From: @drstmane
With the latest default code base (changeset 4530d12232c2), mserver5 fails to start properly:
.../MonetDB $ mserver5
MonetDB 5 server v11.16.0
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^<address> not found
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^<address> not found
## Comment 18764
Date: 2013-06-01 08:56:23 +0200
From: @mlkersten
fixed by checking in the (incomplete) implementation
| mserver5 fails to start properly: "address JSONrenderobject not found" | https://api.github.com/repos/MonetDB/MonetDB/issues/3295/comments | 0 | 2020-11-30T12:31:44Z | 2024-06-27T12:00:01Z | https://github.com/MonetDB/MonetDB/issues/3295 | 753,440,101 | 3,295 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-31 17:40:40 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @mlkersten, @njnes, @drstmane
Last updated: 2013-08-25 09:49:55 +0200
## Comment 18757
Date: 2013-05-31 17:40:40 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
Build Identifier:
[ N.B. I had no way to select the correct MonetDB version for this report, the listed versions look like "Bugzilla::Version=HASH(0x4a4cf08)". I selected the first on the list ]
Same data, same query, same database properties (8 threads, default pipe), same machine, on 2 MonetDB versions: Jul2012 and Feb2013 (updated today).
The MAL plan size for the two versions:
$ wc -l explain_*
11359 explain_Feb2013.txt
195 explain_Jul2012.txt
In Feb2013, just the EXPLAIN takes 9 seconds. The query then takes way too much memory and mserver gets killed by the os (on a 48GB RAM machine).
(I can provide the explain dumps for both versions if needed)
The query:
SELECT a3.id AS _old,
a1.id AS _new
FROM
(SELECT * FROM "_attributesString" as a, dict_mat as b WHERE a.subject=b.id AND b.type='person' AND a.attribute='initials') AS a1,
(SELECT * FROM "_attributesString" as a, dict_mat as b WHERE a.subject=b.id AND b.type='person' AND a.attribute='lastName') AS a2,
(SELECT * FROM "_attributesString" as a, dict_mat as b WHERE a.subject=b.id AND b.type='didl-person' AND a.attribute='name') AS a3
WHERE a1.id = a2.id
AND (a2.value||', '||a1.value = a3.value)
AND a1.id <> a3.id
GROUP BY a1.id, a3.id;
The tables:
CREATE TABLE "spinque"."dict_mat" (
"idstr" CHARACTER LARGE OBJECT,
"id" INTEGER,
"type" CHARACTER LARGE OBJECT,
"prob" DOUBLE
);
CREATE TABLE "spinque"."_attributesString" (
"subject" INTEGER,
"attribute" CHARACTER LARGE OBJECT,
"value" CHARACTER LARGE OBJECT,
"prob" DOUBLE DEFAULT 1.0
);
sql>select count(*) from "_attributesString";
+---------+
| L1 |
+=========+
| 1611801 |
+---------+
1 tuple (2.579ms)
sql>select count(*) from spinque.dict_mat ;
+--------+
| L1 |
+========+
| 335287 |
+--------+
1 tuple (1.996ms)
Default pipe in Feb2013:
optimizer.inline();optimizer.remap();optimizer.costModel();optimizer.coercions();optimizer.evaluate();optimizer.emptySet();optimizer.aliases();optimizer.pushselect();optimizer.mitosis();optimizer.mergetable();optimizer.deadcode();optimizer.commonTerms();optimizer.joinPath();optimizer.reorder();optimizer.deadcode();optimizer.reduce();optimizer.matpack();optimizer.dataflow();optimizer.history();optimizer.multiplex();optimizer.garbageCollector();
Default pipe in Jul2012:
optimizer.inline();optimizer.remap();optimizer.evaluate();optimizer.costModel();optimizer.coercions();optimizer.emptySet();optimizer.aliases();optimizer.mitosis();optimizer.mergetable();optimizer.deadcode();optimizer.commonTerms();optimizer.groups();optimizer.joinPath();optimizer.reorder();optimizer.deadcode();optimizer.reduce();optimizer.dataflow();optimizer.history();optimizer.multiplex();optimizer.accumulators();optimizer.garbageCollector();
Reproducible: Always
### Actual Results:
non-executable MAL plan
### Expected Results:
executable MAL plan
Jul2012:
MonetDB 5 server v11.11.12 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 35.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0d 8 Feb 2011 (compiled with OpenSSL 1.0.0d-fips 8 Feb 2011)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: roberto@spinque01.ins.cwi.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wmissing-include-dirs
Linking : /usr/bin/ld -m elf_x86_64
Feb2013:
MonetDB 5 server v11.15.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 35.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0d 8 Feb 2011 (compiled with OpenSSL 1.0.0d-fips 8 Feb 2011)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: roberto@spinque01.ins.cwi.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wmissing-include-dirs
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18758
Date: 2013-05-31 17:45:05 +0200
From: @swingbit
Created attachment 198
the two explain dumps mentrioned in the report
> Attached file: [bug3294_explain.tar.gz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3294_bug3294_explain.tar.gz_198) (application/gzip, 97229 bytes)
> Description: the two explain dumps mentrioned in the report
## Comment 18762
Date: 2013-06-01 08:39:15 +0200
From: @drstmane
Roberto,
Since you do not appear to use a released version of MonetDB, could you (1) please share the exact changeset IDs of both the Jun2012 & Feb2013 code base you use, and/or (2) possibly use released version(s) (binary for your platform, source tarball, or release tag from Mecurial --- e.g., Feb2013_SP2_release) and report whether this/these behave the same way?
Thanks!
Stefan
## Comment 18763
Date: 2013-06-01 08:50:13 +0200
From: @mlkersten
The increase in MAL plan size is most likely a result of the growth of 8 -> 32 cores. It would be good to run it with GDKnr_threads = 8, 16 and identify what MAL instruction calls for allocation of a (too) large memory fragment.
## Comment 18765
Date: 2013-06-01 12:24:54 +0200
From: @swingbit
Stefan: I've just tried the Feb2013_SP2 release, it behaves exactly the same.
Martin: Unless I'm mistaken, the following set to "nthreads" means that GDKnr_threads is already set to 8, how can it grow to 32?
$ monetdb -p50500 get all equip_tnw_20130530_01
name prop source value
equip_tnw_20130530_01 name - equip_tnw_20130530_01
equip_tnw_20130530_01 type default database
equip_tnw_20130530_01 shared default yes
equip_tnw_20130530_01 nthreads default 8
equip_tnw_20130530_01 optpipe default default_pipe
equip_tnw_20130530_01 readonly default no
equip_tnw_20130530_01 nclients default 64
Does the amount of physical memory influence the number of concurrent MAL blocks created as well as the GDKnr_threads setting?
The same scenario (same db, same query, same monetdb, same nthreads) on a machine with 16GB gives a plan of 3K lines (against the 11K lines on a 48GB machine). If this is true, I don't think it's realistic to assume monetdb has the full physical memory. For example, on the 48GB machine we have normally 15-20 mserver instances running.
I would like to point out that I see two possible issues here:
One is executing this huge query, which becomes impossible.
The other issue is that no matter how fast the final MAL plan is supposed to execute, it cannot be as large as to take 9 seconds to be produced. Even if I were so fool as to set nthreads to 64, there should be an intrinsic limit to how much the MAL plan can grow (assuming the current MAL processing speed won't improve dramatically).
## Comment 18766
Date: 2013-06-01 13:30:27 +0200
From: @drstmane
Roberto,
it would be useful for us to also see the two different MAL plan with identical MonetDB version, identical data, identical number of threads on a 16GB vs. a 48GB machine --- IMHO, memory size should not have any impact on plan size.
Also the output of `mserver5 --version` and `monetdb get all <db>` for both machines would be very useful.
Thanks!
Stefan
## Comment 18767
Date: 2013-06-01 13:37:37 +0200
From: @drstmane
correcting myself: memory size can influence plan size:
if the (the larges table) exceed memory size, mitosis can decide to create more chunks than number of threads (but only run number of threads chunks concurrently) to keep the (concurrent) memory requirements controlled;
thus, with identical data and identical number of threads, the plan can get larger (!) with less/smaller(!) memory --- which is to opposite of what you report...
## Comment 18768
Date: 2013-06-02 13:26:07 +0200
From: @njnes
I think there is a relatively simple reason for this problem. The mitosis/mergetable combo will partition the largest table. As this is a 3 way self join, with one big table, this will explode 3 times. So at least 8*8*8 probably more given the reasons outlined by stefan.
The second (complex) join condition probably does influence the performance too.
## Comment 18772
Date: 2013-06-02 19:54:37 +0200
From: @mlkersten
Roberto
You might also look at
DEBUG sqlquery
followed by single step into the query body and then asking for an overview of the optimizer pipe line costs (O). Perhaps it will indicate the culprit.
I agree with Niel's remarks on plan explosion. Finding the optimal of threads for each and every query is a research challenge by itself.
## Comment 18773
Date: 2013-06-03 09:54:39 +0200
From: @swingbit
Created attachment 199
The shorter explain for a 16GB machine
> Attached file: [explain_Feb2013_16GB.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3294_explain_Feb2013_16GB.txt_199) (text/plain, 371280 bytes)
> Description: The shorter explain for a 16GB machine
## Comment 18774
Date: 2013-06-03 10:28:21 +0200
From: @swingbit
Stefan, I attached the plan for the 16GB machine.
With no_mitosis_pipe, the plan doesn't explode indeed.
However, it still uses all available 10-12GB ram + 8GB swap and then gets killed (this is on the 16 GB machine).
The Jul2012 doesn't seem to be split in chunks (though mitosis was enabled) for some reason, but it also runs with no problem. So perhaps there are really 2 problems: plan explosion due to mitosis, and out-of-memory due to a different plan (without mitosis)
## Comment 18775
Date: 2013-06-03 10:34:01 +0200
From: @swingbit
Created attachment 200
the short plan with no mitosis, but still failing with out of memory
> Attached file: [explain_Feb2013_16GB_nomitosis.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3294_explain_Feb2013_16GB_nomitosis.txt_200) (text/plain, 13824 bytes)
> Description: the short plan with no mitosis, but still failing with out of memory
## Comment 18776
Date: 2013-06-03 10:35:36 +0200
From: @swingbit
I added another plan: on the 16GB machine, with no_mitosis_pipe. The plan generation problem is gone. But the query still runs out of memory. Sounds like a select is not pushed down and we get cartesian products?
## Comment 18781
Date: 2013-06-06 11:19:17 +0200
From: @swingbit
UPDATE:
Please ignore the *execution* issues on this query. I will file this as a separate bug report (there is nothing wrong with the query itself, it appears to a massive leak).
The problem of mitosis exploding the MAL plan remains. A few more comments on that:
Martin, I agree that finding the right fragmentation scheme for all queries is a difficult problem. However, I think it is vital that the system doesn't try to kill itself. There should probably be some more prudent guards about the plan explosion. Can I replicate a block of 100 lines 8x8x8 times? Definitely not, no matter what the intended optimisation was.
I'm also wondering about what Stefan mentioned on mitosis fragmenting the plan - not for multithreading but rather in single-thread mode for limiting memory consumption. That sounds very reasonable, but then shouldn't have anything to do with GDKnr_threads, should it?
So, do you think there is a fix against this plan explosion?
## Comment 18822
Date: 2013-06-12 10:34:41 +0200
From: @njnes
roberto did you already file the separate bug?
## Comment 18823
Date: 2013-06-12 11:58:05 +0200
From: @swingbit
Yes, that is 3299
## Comment 18838
Date: 2013-06-13 10:45:16 +0200
From: @sjoerdmullender
(In reply to comment 0)
> [ N.B. I had no way to select the correct MonetDB version for this report,
> the listed versions look like "Bugzilla::Version=HASH(0x4a4cf08)". I
> selected the first on the list ]
This bit is fixed now.
## Comment 19017
Date: 2013-08-16 22:12:04 +0200
From: @mlkersten
Roberto, any news on this bug with the latest FEB13-SP3 release?
## Comment 19067
Date: 2013-08-25 09:49:55 +0200
From: @njnes
plan explosion is still a problem for performance, but mal should handle it (ie possibly with a slowdown). Marking this as a feature request now, not sure if we should fix the explosion or the slowdown on large plans (mal optimizers problem I guess).
| MAL plan for SQL query is way too big - not executable | https://api.github.com/repos/MonetDB/MonetDB/issues/3294/comments | 0 | 2020-11-30T12:31:41Z | 2024-06-27T11:59:59Z | https://github.com/MonetDB/MonetDB/issues/3294 | 753,440,074 | 3,294 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-30 07:53:09 +0200
From: wongsee
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-06-07 13:40:34 +0200
## Comment 18756
Date: 2013-05-30 07:53:09 +0200
From: wongsee
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31
Build Identifier:
mserver crashes when running a set of statements inside a transaction. But running the same set of statements one by one ie with autocommit on works fine.
Reproducible: Always
### Steps to Reproduce:
1. start transaction
2. run a series of statements which insert into some tables
3. commit transaction
### Actual Results:
segfaults
### Expected Results:
transaction commits successfully
(gdb) where
0 0x00007f640c4c5bb0 in strHash () from /usr/lib/libbat.so.9
1 0x00007f640cc1e841 in MKEYbathash () from /usr/lib/libmonetdb5.so.14
2 0x00007f640caf54eb in runMALsequence () from /usr/lib/libmonetdb5.so.14
3 0x00007f640caf6f7b in ?? () from /usr/lib/libmonetdb5.so.14
4 0x00007f640bfe5f8e in start_thread (arg=0x7f6403bb6700) at pthread_create.c:311
5 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb) thr app all bt
Thread 10 (Thread 0x7f6405b41700 (LWP 17416)):
0 0x00007f640bd08233 in select () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640c52d5c9 in MT_sleep_ms () from /usr/lib/libbat.so.9
2 0x00007f640c4c3e92 in ?? () from /usr/lib/libbat.so.9
3 0x00007f640bfe5f8e in start_thread (arg=0x7f6405b41700) at pthread_create.c:311
4 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 9 (Thread 0x7f6405940700 (LWP 17417)):
0 0x00007f640bd08233 in select () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640c52d5c9 in MT_sleep_ms () from /usr/lib/libbat.so.9
2 0x00007f640cb09a6a in ?? () from /usr/lib/libmonetdb5.so.14
3 0x00007f640bfe5f8e in start_thread (arg=0x7f6405940700) at pthread_create.c:311
4 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 8 (Thread 0x7f6404c99700 (LWP 17418)):
0 0x00007f640bd08233 in select () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640cc0e66c in ?? () from /usr/lib/libmonetdb5.so.14
2 0x00007f640bfe5f8e in start_thread (arg=0x7f6404c99700) at pthread_create.c:311
3 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 7 (Thread 0x7f6403fb8700 (LWP 17419)):
0 0x00007f640bd08233 in select () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640c52d5c9 in MT_sleep_ms () from /usr/lib/libbat.so.9
2 0x00007f640539c6bf in store_manager () from /usr/lib/monetdb5/lib_sql.so
3 0x00007f640534d5f5 in mvc_logmanager () from /usr/lib/monetdb5/lib_sql.so
4 0x00007f640bfe5f8e in start_thread (arg=0x7f6403fb8700) at pthread_create.c:311
5 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 6 (Thread 0x7f6403bb6700 (LWP 17422)):
0 0x00007f640c4c5bb0 in strHash () from /usr/lib/libbat.so.9
1 0x00007f640cc1e841 in MKEYbathash () from /usr/lib/libmonetdb5.so.14
2 0x00007f640caf54eb in runMALsequence () from /usr/lib/libmonetdb5.so.14
3 0x00007f640caf6f7b in ?? () from /usr/lib/libmonetdb5.so.14
4 0x00007f640bfe5f8e in start_thread (arg=0x7f6403bb6700) at pthread_create.c:311
5 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 5 (Thread 0x7f64039b5700 (LWP 17423)):
0 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1555
1 0x00007f640c4c1e2c in HEAPcopy () from /usr/lib/libbat.so.9
2 0x00007f640c6f2709 in ?? () from /usr/lib/libbat.so.9
3 0x00007f64052f9f84 in DELTAproject () from /usr/lib/monetdb5/lib_sql.so
4 0x00007f640caf54eb in runMALsequence () from /usr/lib/libmonetdb5.so.14
5 0x00007f640caf6f7b in ?? () from /usr/lib/libmonetdb5.so.14
6 0x00007f640bfe5f8e in start_thread (arg=0x7f64039b5700) at pthread_create.c:311
7 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 4 (Thread 0x7f64037b4700 (LWP 17424)):
0 0x00007f640c4c5bc3 in strHash () from /usr/lib/libbat.so.9
1 0x00007f640cc1e841 in MKEYbathash () from /usr/lib/libmonetdb5.so.14
2 0x00007f640caf54eb in runMALsequence () from /usr/lib/libmonetdb5.so.14
3 0x00007f640caf6f7b in ?? () from /usr/lib/libmonetdb5.so.14
4 0x00007f640bfe5f8e in start_thread (arg=0x7f64037b4700) at pthread_create.c:311
---Type <return> to continue, or q <return> to quit---
5 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 3 (Thread 0x7f64035b3700 (LWP 17425)):
0 0x00007f640bd03317 in unlink () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640c515c91 in GDKunlink () from /usr/lib/libbat.so.9
2 0x00007f640c4c205a in HEAPdelete () from /usr/lib/libbat.so.9
3 0x00007f640c517a19 in BATdelete () from /usr/lib/libbat.so.9
4 0x00007f640c4bcf87 in ?? () from /usr/lib/libbat.so.9
5 0x00007f64052f9f91 in DELTAproject () from /usr/lib/monetdb5/lib_sql.so
6 0x00007f640caf54eb in runMALsequence () from /usr/lib/libmonetdb5.so.14
7 0x00007f640caf6f7b in ?? () from /usr/lib/libmonetdb5.so.14
8 0x00007f640bfe5f8e in start_thread (arg=0x7f64035b3700) at pthread_create.c:311
9 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 2 (Thread 0x7f6403db7700 (LWP 17697)):
0 sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
1 0x00007f640caf6928 in ?? () from /usr/lib/libmonetdb5.so.14
2 0x00007f640caf7779 in runMALdataflow () from /usr/lib/libmonetdb5.so.14
3 0x00007f640cc0a15d in MALstartDataflow () from /usr/lib/libmonetdb5.so.14
4 0x00007f640caf50d8 in runMALsequence () from /usr/lib/libmonetdb5.so.14
5 0x00007f640caf54c5 in runMALsequence () from /usr/lib/libmonetdb5.so.14
6 0x00007f640caf6380 in callMAL () from /usr/lib/libmonetdb5.so.14
7 0x00007f64052cf98c in ?? () from /usr/lib/monetdb5/lib_sql.so
8 0x00007f640cb152c9 in ?? () from /usr/lib/libmonetdb5.so.14
9 0x00007f640cb16325 in runScenario () from /usr/lib/libmonetdb5.so.14
10 0x00007f640cb163e8 in MSserveClient () from /usr/lib/libmonetdb5.so.14
11 0x00007f640bfe5f8e in start_thread (arg=0x7f6403db7700) at pthread_create.c:311
12 0x00007f640bd0fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Thread 1 (Thread 0x7f640d1aa780 (LWP 17415)):
0 0x00007f640bd08233 in select () at ../sysdeps/unix/syscall-template.S:81
1 0x00007f640c52d5c9 in MT_sleep_ms () from /usr/lib/libbat.so.9
2 0x000000000040269a in main ()
## Comment 18769
Date: 2013-06-02 13:41:42 +0200
From: @njnes
We need a lot more input on this bug report to fix it. Could you create an example query (set) which has this problem (could be derived from your application). Also we need to know some sizes, it table size, width, machine ram/disk etc.
| segfault at /usr/lib/libbat.so.9 if a set of statements is run inside a transaction | https://api.github.com/repos/MonetDB/MonetDB/issues/3293/comments | 0 | 2020-11-30T12:31:39Z | 2024-06-27T11:59:59Z | https://github.com/MonetDB/MonetDB/issues/3293 | 753,440,046 | 3,293 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-29 09:36:02 +0200
From: @bartscheers
To: Merovingian devs <<bugs-merovingian>>
Version: 11.15.11 (Feb2013-SP3)
Last updated: 2013-09-27 13:47:17 +0200
## Comment 18752
Date: 2013-05-29 09:36:02 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
depending on the windown size the monetdb status replaces too long string by dots in which case you can't read the info.
Also not practical when reading the lines with dots from scripts
Reproducible: Always
### Steps to Reproduce:
1.set window width small
2.monetdb status
3.
### Actual Results:
name state health remarks
...0 R 9h 100% 0s mapi:monetdb://rocks096.scilens:50096/cycle0_100x10000
### Expected Results:
name state health remarks
cycle0_100x10000 R 9h 100% 0s mapi:monetdb://rocks096.scilens:50096/cycle0_100x10000
or something similar...
## Comment 18947
Date: 2013-07-30 20:40:53 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8ca402652831](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8ca402652831) made by Fabian Groffen <fabian@monetdb.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8ca402652831](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8ca402652831)
Changeset description:
monetdb: don't compress output when not connected to a terminal
- check stdout for its size (since we're writing there, we don't care
about reading end -- may as well be completely different in case of a
pipe)
- don't compress output when we didn't find a terminal width (0),
addresses bug #3292, now scripts should get full output
## Comment 18948
Date: 2013-07-30 20:42:12 +0200
From: @grobian
% monetdb status
name state health remarks
...t R 15m 62% 5d mapi:monetdb://nut....er.nl:52100/jaqltest
...l S 7w 100% 2w mapi:monetdb://nut....der.nl:52100/decimal
c S 37m 100% 19s mapi:monetdb://nut....bitzolder.nl:52100/c
b S 37m 100% 20s mapi:monetdb://nut....bitzolder.nl:52100/b
a S 37m 100% 20s mapi:monetdb://nut....bitzolder.nl:52100/a
% monetdb status | cat
name state health remarks
jaqltest R 46m 62% 5d mapi:monetdb://nut.cheops.bitzolder.nl:52100/jaqltest
decimal S 7w 100% 2w mapi:monetdb://nut.cheops.bitzolder.nl:52100/decimal
c S 1h 100% 19s mapi:monetdb://nut.cheops.bitzolder.nl:52100/c
b S 1h 100% 20s mapi:monetdb://nut.cheops.bitzolder.nl:52100/b
a S 1h 100% 20s mapi:monetdb://nut.cheops.bitzolder.nl:52100/a
| monetdb status should print full line | https://api.github.com/repos/MonetDB/MonetDB/issues/3292/comments | 0 | 2020-11-30T12:31:36Z | 2024-06-27T11:59:58Z | https://github.com/MonetDB/MonetDB/issues/3292 | 753,440,016 | 3,292 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-29 01:22:10 +0200
From: Ben Reilly <<ben>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: ben, @njnes
Last updated: 2013-08-25 09:51:30 +0200
## Comment 18750
Date: 2013-05-29 01:22:10 +0200
From: Ben Reilly <<ben>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36
Build Identifier:
We're currently working on integrating MonetDB into the OLTPBenchmark testing suite (mostly to use their stat-tracking platform), because it should be as simple as plugging in MonetDB via JDBC---but we're having some troubles with prepared statements. In particular, we encounter an internal error when MonetDB tries to prepare some INSERT statements. For example:
INSERT INTO "oorder" VALUES (?, ?, ?, ?, ?, ?, ?, ?)
produces the error
java.sql.SQLException: TypeException:user.main[90]:'algebra.subselect' undefined in: _138:any := algebra.subselect(_109:bat[:oid,:int], _135:bat[:oid,:oid], _66:any, _66:any, _136:bit, _136:bit, _137:bit)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2535)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.<init>(MonetPreparedStatement.java:118)
at nl.cwi.monetdb.jdbc.MonetConnection.prepareStatement(MonetConnection.java:901)
at nl.cwi.monetdb.jdbc.MonetConnection.prepareStatement(MonetConnection.java:825)
In this application, there are about 6 queries that are run many times each. The first 2-3 sets of queries will run without problem, but the last 3-4 will crash with an error similar to the one above. If we reorder the queries, it fails in the same manner. That is, if we put the above query before all the rest, then it will run successfully: no matter what the last 3-4 queries are, they will fail; no matter what the first 2-3 queries are, they will succeed. So it does not appear to be related to the queries themselves, but to something internal to the driver that crashes after some tens of thousands of prepared statements are executed.
Attached is the output of running EXPLAIN on the query.
Reproducible: Always
### Steps to Reproduce:
Simple reproduction unknown; sorry...
## Comment 18751
Date: 2013-05-29 01:22:56 +0200
From: Ben Reilly <<ben>>
Created attachment 196
Output of EXPLAIN on query.
> Attached file: [query-explain.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3291_query-explain.txt_196) (text/plain, 15106 bytes)
> Description: Output of EXPLAIN on query.
## Comment 18777
Date: 2013-06-04 00:50:03 +0200
From: Ben Reilly <<ben>>
In order to get around this issue, I've been able to do the following: for each table that I load, I close the previous Connection and open a new one. The code looks something like this:
this.conn = DriverManager.getConnection( ... );
loadTableX();
this.conn.close();
With this workaround, I no longer encounter this issue, which leads me to believe that there are some resources internal to the driver that run out if I try to load all tables on the same connection. Note that for each table loading function, I create a finite number of PreparedStatements (1-3 per function), so perhaps the driver can only create a fixed number of PreparedStatement handles, then crashes when it runs out of slots.
Either way, something related to memory corruption or limited resources would explain the issue, I think.
## Comment 18801
Date: 2013-06-09 18:00:08 +0200
From: @grobian
mal error, not a driver bug
## Comment 18821
Date: 2013-06-12 10:30:06 +0200
From: @njnes
Fabian, could you help Ben to send me an trace of the data send to the server.
That way I could create a debug script (without) java/jdbc to fix this issue.
## Comment 18973
Date: 2013-08-06 09:07:16 +0200
From: @njnes
how many times are the prepared statements executed?
## Comment 18979
Date: 2013-08-07 19:02:32 +0200
From: Ben Reilly <<ben>>
Hundreds to thousands of times, I believe. The application I have submits batches of about 10k inserts, totaling maybe a few million inserts overall (so up to a few thousand executions of the PreparedStatement).
## Comment 18980
Date: 2013-08-07 22:58:38 +0200
From: @njnes
the query cache (which also holds the prepared statements) tries to limit (with a
hard (crude) measure) the total number of cached/prepared statements to a max
(default of 100).
Per client this can be set to a higer number (set cache = 1000;). Could you
try this to see if it solves the problem. If so we should find a cleaner way to
limit the amount of prepared/cached queries.
| PreparedStatement experiences internal error after many statements executed. | https://api.github.com/repos/MonetDB/MonetDB/issues/3291/comments | 0 | 2020-11-30T12:31:34Z | 2024-06-27T11:59:57Z | https://github.com/MonetDB/MonetDB/issues/3291 | 753,439,990 | 3,291 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-29 01:14:38 +0200
From: Ben Reilly <<ben>>
To: clients devs <<bugs-clients>>
Version: 11.15.7 (Feb2013-SP2)
CC: ben
Last updated: 2013-07-03 08:48:00 +0200
## Comment 18749
Date: 2013-05-29 01:14:38 +0200
From: Ben Reilly <<ben>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36
Build Identifier:
When we generate some prepared statements with columns of certain decimal types, we encounter errors that appear to be related to casting from Java's float/double types to these decimal(N,P) types in MonetDB.
For instance, with a column of type "decimal(4,4)", we get the following error when we provide the PreparedStatement object with either a float or double in our Java code using PreparedStatement.setDouble(...):
java.sql.SQLException: EXEC: wrong type for argument 3 of prepared statement: decimal, expected decimal
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2535)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(MonetPreparedStatement.java:247)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.executeUpdate(MonetPreparedStatement.java:287)
This error can only be avoided by switching the column type from "decimal(4,4)" to "double".
A less troublesome, but similar, bug occurs when the column is of type "decimal(5,2)" and we provide a Java float type in our method call. That is, we do not encounter the bug when we provide a Java double type.
Both of these bugs are avoidable by switching the "decimal(N,P)" types to "double" types in our schema, so these aren't show-stopping. However, there does appear to be some sort of bug with the casting, since Java's float and double types should easily contain enough precision to convert to a 4- or 5-digit decimal value.
Reproducible: Always
### Steps to Reproduce:
1. Create table with a field of type "decimal(5,2)".
2. Compile and run a JDBC application that uses a PreparedStatement to insert into this table, passing a `float' into setDouble(...). Consider the simple example below.
------------------
sql> CREATE TABLE demo ( val decimal(5,2) );
------------------
import java.sql.*;
public class JDBCTest {
public static void main(String[] args) throws Exception {
// make sure the driver is loaded
Class.forName("nl.cwi.monetdb.jdbc.MonetDriver");
Connection con = DriverManager.getConnection("jdbc:monetdb://localhost/typetest", "monetdb", "monetdb");
try {
PreparedStatement distStmt = con.prepareStatement("INSERT INTO \"demo\" VALUES (?)");
distStmt.setDouble(1, 5.1f); // Pass in a float.
distStmt.executeUpdate();
} catch(SQLException se) {
se.printStackTrace();
}
}
}
------------------
### Actual Results:
Experience the following exception:
java.sql.SQLException: EXEC: wrong type for argument 1 of prepared statement: decimal, expected decimal
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2535)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(MonetPreparedStatement.java:247)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.executeUpdate(MonetPreparedStatement.java:287)
at JDBCTest.main(JDBCTest.java:14)
### Expected Results:
No error.
## Comment 18753
Date: 2013-05-29 21:22:58 +0200
From: @grobian
I think [78e62eb2c684](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=78e62eb2c684) fixes this problem
## Comment 18754
Date: 2013-05-30 02:27:10 +0200
From: Ben Reilly <<ben>>
Created attachment 197
Proposed patch for decimal type issues
I cloned and compiled that code, but it did not work for me. At the least, there was an error with the indexing: the value 'i' to look up parameter properties in the 'digits' and 'scale' arrays should be calculated from `getParamIdx(parameterIndex)', as it is in, say, setValue(...). Without this, you may experience an IndexOutOfBoundsException (I believe your test case didn't experience this because there was more than one parameter in the PreparedStatement---so it just selected the wrong one).
In any case, I've found a solution that works for me, which manipulates the scale in the BigDecimal. Further, I've rerouted setDouble(...) and setFloat(...) to use setBigDecimal(...) too, rather than setValue(...).
Attached is my diff.
> Attached file: [jdbc-decimal-fix.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3290_jdbc-decimal-fix.diff_197) (text/plain, 2482 bytes)
> Description: Proposed patch for decimal type issues
## Comment 18755
Date: 2013-05-30 02:31:47 +0200
From: Ben Reilly <<ben>>
I should note as well that with the previous fix, I was getting rounding errors: the DB would reject my sending it, say 5.1, because it would actually be represented as 5.09999..., which certainly has too high of a precision. My proposed patch uses BigDecimal.round(...) for this reason (I presume that it is acceptable to round a user's input to the format specified in the schema).
## Comment 18780
Date: 2013-06-05 20:35:36 +0200
From: Ben Reilly <<ben>>
Created attachment 201
Updated patch to fix decimal type casting
I noticed that my previous patch also had a bug in it: it seems that MonetDB counts leading 0's in a decimal's precision. So, for instance, the number "0.1234" is counted as having precision 5. Now, the leading zero is dropped from these values, yielding ".1234" in our example, which has the expected precision of 4.
> Attached file: [typefix.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3290_typefix.patch_201) (text/plain, 2768 bytes)
> Description: Updated patch to fix decimal type casting
## Comment 18802
Date: 2013-06-09 18:33:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3bde6392aa91](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3bde6392aa91) made by Fabian Groffen <fabian@monetdb.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3bde6392aa91](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3bde6392aa91)
Changeset description:
setBigDecimal: improve way we "round" BigDecimals
Use BigDecimal rounding to "shave off" digits from the input BigDecimal
to try and make it fit for the DECIMAL(x,y) type the server expects.
Slightly modified patch by Ben Reilly from bug #3290.
## Comment 18803
Date: 2013-06-09 18:36:05 +0200
From: @grobian
Thanks! I've committed your patch with some slight modifications. I did NOT take your modifications of setFloat and setDouble, since they would only work if the underlying type would be a DECIMAL. Regardless to that, those changes were incorrect anyway, since the contract of those methods say that the driver should send the value it gets as float or double to the database.
For just sending float/double types to the database in a DECIMAL column, use setObject(), which will do all the required magic/mapping etc. that is possible to convert the value received to the target type in the database.
## Comment 18810
Date: 2013-06-10 18:24:20 +0200
From: Ben Reilly <<ben>>
Ah, yes, I didn't notice that in the PreparedStatement spec, the setXYZ() functions explicitly state what type they should be sending to the database.
Thanks for adding in the fix.
| Faulty type handling/casting in JDBC driver | https://api.github.com/repos/MonetDB/MonetDB/issues/3290/comments | 0 | 2020-11-30T12:31:31Z | 2024-06-27T11:59:56Z | https://github.com/MonetDB/MonetDB/issues/3290 | 753,439,958 | 3,290 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-24 19:43:01 +0200
From: Peter <<Peter.DeRijk>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:48:02 +0200
## Comment 18748
Date: 2013-05-24 19:43:01 +0200
From: Peter <<Peter.DeRijk>>
The example code below gives the following error in the final select:
SELECT: no such binary operator 'sql_add(boolean,boolean)'
The query is supported by other databases and is (afaik) valid sql.
mclient -d monetdbtest -s 'drop table t' || true
mclient -d monetdbtest -s 'create table t ("v1" int,"v2" int, "v3" int)'
mclient -d monetdbtest -s 'insert into t ("v1","v2","v3") values (1,1,1)'
mclient -d monetdbtest -s 'insert into t ("v1","v2","v3") values (1,2,1)'
mclient -d monetdbtest -s 'insert into t ("v1","v2","v3") values (1,2,3)'
mclient -d monetdbtest -s 'insert into t ("v1","v2","v3") values (4,4,4)'
mclient -d monetdbtest -s 'select * from t where (("v1" > 1)+("v2" > 1)+("v3" > 1)) > 1'
## Comment 18759
Date: 2013-05-31 19:32:20 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c7531a9567d0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c7531a9567d0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c7531a9567d0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c7531a9567d0)
Changeset description:
fixed bug #3289 and added test
## Comment 18760
Date: 2013-05-31 19:33:35 +0200
From: @njnes
fixed bug by handling boolean add/sub
| SELECT: no such binary operator 'sql_add(boolean,boolean)' | https://api.github.com/repos/MonetDB/MonetDB/issues/3289/comments | 0 | 2020-11-30T12:31:29Z | 2024-06-27T11:59:55Z | https://github.com/MonetDB/MonetDB/issues/3289 | 753,439,932 | 3,289 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-23 19:49:04 +0200
From: Ben Reilly <<ben>>
To: clients devs <<bugs-clients>>
Version: 11.15.7 (Feb2013-SP2)
CC: ben
Last updated: 2013-07-03 08:48:03 +0200
## Comment 18745
Date: 2013-05-23 19:49:04 +0200
From: Ben Reilly <<ben>>
Some of the setXYZ(...) methods in MonetPreparedStatement.java do not allow for the parameter to be null, resulting in an exception. For instance, setTimestamp(...) and setDate(...) do not check if the parameter 'x' is null before trying to call `x.toString()'.
Not all methods are affected, however: setBytes(...), for example, checks if 'x' is null and calls setNull(...) as necessary, which is the expected behaviour (the JDBC drivers for MySQL and PostgreSQL both do this in all cases).
## Comment 18746
Date: 2013-05-23 20:10:02 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0d3537514b4e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0d3537514b4e) made by Fabian Groffen <fabian@monetdb.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0d3537514b4e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0d3537514b4e)
Changeset description:
PreparedStatement: properly handle null for setXXX() methods, bug #3288
## Comment 18747
Date: 2013-05-23 20:10:46 +0200
From: @grobian
Thanks, fixed for the next release
| PreparedStatements may throw NullPointerException when setting parameter | https://api.github.com/repos/MonetDB/MonetDB/issues/3288/comments | 0 | 2020-11-30T12:31:27Z | 2024-06-27T11:59:54Z | https://github.com/MonetDB/MonetDB/issues/3288 | 753,439,902 | 3,288 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-18 02:08:59 +0200
From: Tim H. <<monetdb.bug.reporter>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:48:00 +0200
## Comment 18738
Date: 2013-05-18 02:08:59 +0200
From: Tim H. <<monetdb.bug.reporter>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
[root ~] mclient -d testdb -u monetdb
Database: MonetDB v11.15.8 (unreleased)
sql>select name from "sys".users where lower(name) = 'monetdb';
GDK reported error.
BATsubselect: invalid argument: b must have a dense head.
sql>
Reproducible: Always
### Steps to Reproduce:
1. start with an empty database named testdb
2. mclient -d testdb -u monetdb
3. create user my_user with password 'p1' name 'User with role' schema "sys";
4. select name from "sys".users where lower(name) = 'monetdb';
### Actual Results:
GDK reported error.
BATsubselect: invalid argument: b must have a dense head.
### Expected Results:
+---------+
| name |
+=========+
| monetdb |
| my_user |
+---------+
I can delete the user my_user then re-run the problem query and it does not report an error.
## Comment 18740
Date: 2013-05-18 16:47:50 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2fb3afea17e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2fb3afea17e5) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2fb3afea17e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2fb3afea17e5)
Changeset description:
fixed bug #3287, ie non void users bat.
## Comment 18741
Date: 2013-05-18 16:49:10 +0200
From: @njnes
fixed in sql using extra mark
| lower(name) clause in query causing "BATsubselect: invalid argument.." error | https://api.github.com/repos/MonetDB/MonetDB/issues/3287/comments | 0 | 2020-11-30T12:31:24Z | 2024-06-27T11:59:53Z | https://github.com/MonetDB/MonetDB/issues/3287 | 753,439,871 | 3,287 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-18 01:54:16 +0200
From: Tim H. <<monetdb.bug.reporter>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:48:00 +0200
## Comment 18737
Date: 2013-05-18 01:54:16 +0200
From: Tim H. <<monetdb.bug.reporter>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
Consider the following SQL statements.
call sys.storagemodelinit();
create table estimated_storage
as (
select "table" as tblname,
max("count") as count
from sys.storagemodel()
where "schema" = 'sys'
group by "table")
with data;
The second statement fails with the following error:
SyntaxException:user.storagemodel[86]:invalid return target!
TypeException:user.main[7]:'user.storagemodel' undefined in:
(_11:bat[:oid,:str], _12:bat[:oid,:str], _13:bat[:oid,:str],
_14:bat[:oid,:str], _15:bat[:oid,:lng], _16:bat[:oid,:lng],
_17:bat[:oid,:lng], _18:bat[:oid,:lng], _19:bat[:oid,:bit])
:= user.storagemodel()
The workaround is to run the query in the create table statement by itself and then run the create table statement.
call sys.storagemodelinit();
select "table" as tblname,
max("count") as count
from sys.storagemodel()
where "schema" = 'sys'
group by "table";
create table estimated_storage
as (
select "table" as tblname,
max("count") as count
from sys.storagemodel()
where "schema" = 'sys'
group by "table")
with data;
The above SQL statements succeed, but only after completely exiting and restarting mclient (i.e. once the error happens, selecting from sys.storagemodel() always fails with the same error in the same mclient session).
Reproducible: Always
### Steps to Reproduce:
1. mclient -d dbname -u monetdb
2. call sys.storagemodelinit();
3. create table estimated_storage
as (
select "table" as tblname,
max("count") as count
from sys.storagemodel()
where "schema" = 'sys'
group by "table")
with data;
### Actual Results:
SyntaxException:user.storagemodel[86]:invalid return target!
TypeException:user.s3_1[6]:'user.storagemodel' undefined in: (_12:bat[:oid,:str], _13:bat[:oid,:str], _14:bat[:oid,:str], _15:bat[:oid,:str], _16:bat[:oid,:lng], _17:bat[:oid,:lng], _18:bat[:oid,:lng], _19:bat[:oid,:lng], _20:bat[:oid,:bit]) := user.storagemodel()
program contains errors
### Expected Results:
operation successful (7.215ms)
Once this error occurs I must exit mclient completely before trying the workaround.
## Comment 18742
Date: 2013-05-19 20:20:58 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [32f653ab6e7a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=32f653ab6e7a) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=32f653ab6e7a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=32f653ab6e7a)
Changeset description:
fixed bug #3286. Only on top level query (mal) creation add calls
for sql exception.
## Comment 18743
Date: 2013-05-19 20:44:41 +0200
From: @njnes
fixed by only returning the sql.exception on toplevel queries.
| TypeException when creating table with data by selecting from sys.storagemodel() | https://api.github.com/repos/MonetDB/MonetDB/issues/3286/comments | 0 | 2020-11-30T12:31:22Z | 2024-06-27T11:59:52Z | https://github.com/MonetDB/MonetDB/issues/3286 | 753,439,846 | 3,286 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-18 01:40:14 +0200
From: Tim H. <<monetdb.bug.reporter>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @mlkersten
Last updated: 2014-02-20 15:02:56 +0100
## Comment 18736
Date: 2013-05-18 01:40:14 +0200
From: Tim H. <<monetdb.bug.reporter>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
When I try to query from sys.queryLog when my current schema is not sys then the query fails with error: no such table 'queryHistory'
Transcript:
[root ~] mclient -d testdb -u monetdb
Database: MonetDB v11.15.8 (unreleased)
auto commit mode: on
sql>create schema my_schema;
operation successful (4.528ms)
sql>set schema my_schema;
auto commit mode: on
sql>select * from sys.queryLog;
SELECT: no such table 'queryhistory'
Reproducible: Always
### Steps to Reproduce:
1. mclient -d dbname -u monetdb
2. create schema my_schema;
3. set schema my_schema;
4. select * from sys.queryLog;
### Actual Results:
SELECT: no such table 'queryhistory'
### Expected Results:
+----+---------+------+-------+-------+----------+-------+-----------+---------+--------+------+--------+--------+---------+---------+
| id | defined | name | query | parse | optimize | ctime | arguments | execute | result | foot | memory | tuples | inblock | oublock |
+====+=========+======+=======+=======+==========+=======+===========+=========+========+======+========+========+=========+=========+
+----+---------+------+-------+-------+----------+-------+-----------+---------+--------+------+--------+--------+---------+---------+
0 tuples (5.558ms)
## Comment 18739
Date: 2013-05-18 02:54:45 +0200
From: @mlkersten
This correct.
In the Feb 2013 release, the queryLog is defined as:
create view queryLog as
select qd.*, ql.ctime, ql.arguments, ql.exec, ql.result, ql.foot, ql.memory, ql.tuples, ql.inblock, ql.oublock from queryHistory qd, callHistory ql
where qd.id = ql.id;
In this view qd and ql are not qualified by schema name, which means they are resolved the current schema. A patch would be:
create view queryLog as
select qd.*, ql.ctime, ql.arguments, ql.exec, ql.result, ql.foot, ql.memory, ql.tuples, ql.inblock, ql.oublock from sys.queryHistory qd, sys.callHistory ql
where qd.id = ql.id;
The querylog functionality is changed in the development branch:
http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/QueryHistoryNew
## Comment 19613
Date: 2014-02-20 15:02:56 +0100
From: @sjoerdmullender
Jan2014 has been released.
| no such table 'queryHistory' | https://api.github.com/repos/MonetDB/MonetDB/issues/3285/comments | 0 | 2020-11-30T12:31:19Z | 2024-06-27T11:59:51Z | https://github.com/MonetDB/MonetDB/issues/3285 | 753,439,821 | 3,285 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-17 20:40:17 +0200
From: Joseph <<jpfourny>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @mlkersten, @njnes
Last updated: 2013-08-25 09:52:17 +0200
## Comment 18735
Date: 2013-05-17 20:40:17 +0200
From: Joseph <<jpfourny>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
Basically, any attempt to execute COPY INTO (from file or STDIN) will result in an Access Violation if I have at least one DOUBLE column (all other data types seem fine). Even with even the simplest table (say 1 column and 1 row), this is 100% reproducible. I don't have debug symbols for libbat.dll, so this is the stack trace I have from Visual Studio 2010:
mswsock.dll!DllMain() + 0x50ad bytes
mswsock.dll!_CRT_INIT() - 0x62 bytes
ntdll.dll!LdrShutdownThread() - 0x28 bytes
ntdll.dll!RtlExitUserThread() + 0x38 bytes
libbat.dll!000007feeff9afd7()
[Frames below may be incorrect and/or missing, no symbols loaded for libbat.dll]
kernel32.dll!BaseThreadInitThunk() + 0xd bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes
Recently, I have rebuilt my development box running Windows 7 Pro SP1 and since then I have not been able to get MonetDB to work right. This is a very clean system (one week old). I have several installs (32 bit and 64 bit) with no luck. Most of my troubleshooting was done with the Feb2013-SP2 build.
The same test case works fine on another machine I have, so it is definitely something environmental. What boggles my mind is how Winsock is related. In older builds (say April 2012), I get an Access Violation in a completely different area (cabinet.dll). Perhaps some sort of stack corruption?
If someone can send me a debug build (including PDBs with source info) then I can extract more information for you. I have a minidump available, if you are interest.
Reproducible: Always
### Steps to Reproduce:
1) Start mserver5.exe
2) Open MonetDB client.
3) Run these commands:
CREATE TABLE "test" (col double);
COPY 1 RECORDS INTO "test" FROM STDIN USING DELIMITERS ',', '\n', '"' NULL AS '';
1;
### Actual Results:
Access Violation.
### Expected Results:
No crash.
Happens with Feb2013-SP2 build. Same problem with older builds (back to Apr 2012), but stacks may differ.
## Comment 18864
Date: 2013-06-19 15:55:19 +0200
From: @sjoerdmullender
You can find an installer in http://homepages.cwi.nl/~sjoerd/downloads/installer/
It is the tip of the Feb2013 branch (hg id ee65f3d73109), i.e. the branch that the Feb2013 releases are made from, but a later version than the latest release, and it is for 64 bit Windows.
This installer was created from a debug build and includes the .pdb files as well. Since creating an installer from a debug build is a manual process, I won't do this too often, but if you really need it, I can try to make one from the actual Feb2013-SP2 release.
## Comment 18865
Date: 2013-06-19 19:08:15 +0200
From: Joseph <<jpfourny>>
Thanks :) That installer should be fine. I will try it as soon as possible.
## Comment 19016
Date: 2013-08-16 22:03:52 +0200
From: @mlkersten
Is there any progress on this issue?
| Access Violation during bulk-import (ie: COPY INTO) with DOUBLE column | https://api.github.com/repos/MonetDB/MonetDB/issues/3284/comments | 0 | 2020-11-30T12:31:16Z | 2024-06-27T11:59:50Z | https://github.com/MonetDB/MonetDB/issues/3284 | 753,439,790 | 3,284 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-15 15:07:33 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.17.9 (Jan2014)
CC: ajdamico, @hannesmuehleisen, monetdbuser
Last updated: 2014-03-04 09:54:25 +0100
## Comment 18733
Date: 2013-05-15 15:07:33 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
As originally requested by Martin[1] (and agreed to by Niels on the mailing list), I'd like to request that the median() function be expanded to a quantile() function that allows the calculation of all percentiles, instead of just the 50th.
I believe this would be a useful addition for the new statistical user-base that the MonetDB.R project is starting to attract. :)
If this function works like the quantile() function in the R language, it would require two inputs: quantile( COLUMN_NAME , percentile_value )
The following pairs of commands should be equivalent in all cases:
quantile( COLUMN_NAME , 0.5 ) == median( COLUMN_NAME )
quantile( COLUMN_NAME , 0 ) == min( COLUMN_NAME )
quantile( COLUMN_NAME , 1 ) == max( COLUMN_NAME )
Hopefully, the bulk of the work to create the median() function can be quickly expanded for this purpose.
Thanks for considering this!
[1] http://osdir.com/ml/db.monetdb.bugs/2008-06/msg00206.html
Reproducible: Always
### Steps to Reproduce:
Not relevant - feature request
## Comment 19662
Date: 2014-03-04 09:54:25 +0100
From: @hannesmuehleisen
Jan2014 includes quantile() support
| FEATURE REQUEST: please expand median() function to quantile() - enabling all percentiles | https://api.github.com/repos/MonetDB/MonetDB/issues/3283/comments | 0 | 2020-11-30T12:31:13Z | 2024-06-27T11:59:49Z | https://github.com/MonetDB/MonetDB/issues/3283 | 753,439,745 | 3,283 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-14 10:02:34 +0200
From: Inho Kim <<georgios.kim>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @drstmane
Last updated: 2013-07-03 08:48:01 +0200
## Comment 18720
Date: 2013-05-14 10:02:34 +0200
From: Inho Kim <<georgios.kim>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
Alter load 65k rows with bulk load (copy), query will succeed and data was correct. When restart mserver5, same query returns below warning messages.
"1 field truncated!\n note: to disable dropping columns and/or truncating fields use \w-1\n write error"
Reproducible: Always
### Steps to Reproduce:
[inho@ChakraMonet tmp]$ mclient -u monetdb -d test
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Feb2013-SP2)
Database: MonetDB v11.15.7 (Feb2013-SP2), 'mapi:monetdb://ChakraMonet:50002/test'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>\</tmp/test.sql
operation successful
655360 affected rows
sql>select * from test limit 20 offset 655350;
+------+--------+-------+
| id | name | seq |
+======+========+=======+
| id0 | Test 0 | 1 |
| id2 | Test 2 | 2 |
| id3 | Test 3 | 3 |
| id4 | Test 4 | 4 |
| id5 | Test 5 | 5 |
| id6 | Test 6 | 6 |
| id7 | Test 7 | 7 |
| id9 | Test 9 | 9 |
| id8 | Test 8 | 99999 |
| id9 | Test 9 | 9 |
+------+--------+-------+
10 tuples (50.898ms)
sql>\q
[inho@ChakraMonet tmp]$ monetdb stop test
stopping database 'test'... done
[inho@ChakraMonet tmp]$ monetdb start test
starting database 'test'... done
[inho@ChakraMonet tmp]$ !mclient
mclient -u monetdb -d test
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Feb2013-SP2)
Database: MonetDB v11.15.7 (Feb2013-SP2), 'mapi:monetdb://ChakraMonet:50002/test'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select * from test limit 20 offset 655350;
+------+--------+-----------+
| id | name | seq |
+======+========+===========+
| id0 | Test 0 | 1 |
| id2 | Test 2 | 2 |
| id3 | Test 3 | 3 |
| id4 | Test 4 | 4 |
| id5 | Test 5 | 5 |
| id6 | Test 6 | 6 |
| id7 | Test 7 | 7 |
| id9 | Test 9 | 9 |
| id8 | Test 8 | 99999 |
| 녋랁u |10 tuples (42.354ms) !1 field truncated!
note: to disable dropping columns and/or truncating fields use \w-1
write error
sql>
## Comment 18721
Date: 2013-05-14 10:04:22 +0200
From: Inho Kim <<georgios.kim>>
Created attachment 194
bulk load data
> Attached file: [test.sql.gz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3282_test.sql.gz_194) (application/x-gzip, 74157 bytes)
> Description: bulk load data
## Comment 18722
Date: 2013-05-14 10:15:31 +0200
From: @drstmane
Is your original output indeed correct, in particular the double "| id9 | Test 9 | 9 |" record (the second occurrence of which seem to be corrupted after the restart)?
Can you share the content of your monetdbd / merovingian log file that is related to stopping and restarting the server after the bulk load?
## Comment 18723
Date: 2013-05-14 10:27:25 +0200
From: Inho Kim <<georgios.kim>>
>Is your original output indeed correct, in particular the double "| id9 | Test 9 >| 9 |" record (the second occurrence of which seem to be corrupted after the >restart)?
yes..
>Can you share the content of your monetdbd / merovingian log file that is related >to stopping and restarting the server after the bulk load?
I already uploaded test.sql.gz file ( for bulk load )
## Comment 18724
Date: 2013-05-14 10:28:21 +0200
From: Inho Kim <<georgios.kim>>
Created attachment 195
merovingian.log
> Attached file: [merovingian.log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3282_merovingian.log_195) (text/plain, 5290 bytes)
> Description: merovingian.log
## Comment 18725
Date: 2013-05-14 12:50:01 +0200
From: @sjoerdmullender
After loading the data and restarting the server, I get an assertion error:
mserver5: monetdb5/modules/atoms/str.c:1357: strLength: Assertion `l <2147483647' failed.
I'll investigate a bit more.
## Comment 18726
Date: 2013-05-14 15:11:48 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [83ada82a21d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=83ada82a21d8) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=83ada82a21d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=83ada82a21d8)
Changeset description:
Off-by-one error: don't extend if file already correct size.
This fixes bug #3282.
Extending a file is done by seeking to the desired size and writing a
byte. In the case encountered here, the file was already the correct
size, but a byte was written anyway, overwriting the last byte in the
file and thereby corrupting the data.
## Comment 18727
Date: 2013-05-14 15:49:09 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [934a44f61041](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=934a44f61041) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=934a44f61041](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=934a44f61041)
Changeset description:
Test for bug #3282.
## Comment 18728
Date: 2013-05-14 15:57:35 +0200
From: @sjoerdmullender
Bug is fixed, test is added.
| bulk loaded data corrupted when restart monetdb | https://api.github.com/repos/MonetDB/MonetDB/issues/3282/comments | 0 | 2020-11-30T12:31:11Z | 2024-06-27T11:59:48Z | https://github.com/MonetDB/MonetDB/issues/3282 | 753,439,722 | 3,282 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-13 17:29:58 +0200
From: Nik Schuiling <<n.h.schuiling>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.7 (Feb2013-SP2)
CC: @mlkersten
Last updated: 2013-07-03 08:47:58 +0200
## Comment 18718
Date: 2013-05-13 17:29:58 +0200
From: Nik Schuiling <<n.h.schuiling>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
pqueue.enqueue_max throws a type mismatch in my example MAL-program. This is incorrect behaviour in my opinion (correct me if i'm wrong).
Reproducible: Always
### Steps to Reproduce:
Execute the following MAL code:
init pqueue
X_buffer_type:bat[:oid,:int] := bat.new(:oid,:int,1);
X_buffer := pqueue.init(X_buffer_type,5:wrd);
enqueue something
pqueue.enqueue_max(X_buffer,5:oid,5:int); throws a type mismatch error
### Actual Results:
type mismatch error
### Expected Results:
no error message
In pqueue.c the following check of method PQenqueue_anymax seems to be wrong:
if (p->argc != 4 || getArgType(mb, p, 1) != TYPE_bat || getArgType(mb, p, 2) != TYPE_oid)
In my example MAL-program the condition getArgType(mb, p, 1) != TYPE_bat is true, which doesn't make sense. The value of getArgType(mb, p, 1) in this context is 670777.
## Comment 18719
Date: 2013-05-13 21:09:52 +0200
From: @mlkersten
The value 670777 indicates a BAT.
The type TYPE_bat refers to a BAT identifier, which is largely obsolete since we abandoned recursive BATs
The code has been fixed in default and a test has been added
src/modules/mal/Tests/pqueue.mal
## Comment 18729
Date: 2013-05-14 15:58:22 +0200
From: @sjoerdmullender
Bug was backported.
| pqueue.enqueue_max type mismatch error | https://api.github.com/repos/MonetDB/MonetDB/issues/3281/comments | 0 | 2020-11-30T12:31:09Z | 2024-06-27T11:59:47Z | https://github.com/MonetDB/MonetDB/issues/3281 | 753,439,689 | 3,281 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-02 21:20:08 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: ajdamico
Last updated: 2013-07-03 08:48:02 +0200
## Comment 18705
Date: 2013-05-02 21:20:08 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
avg(), sum(), min(), max() all work when a column contains some NULL values. median does not (at least not in the very simple example below)
Reproducible: Always
### Steps to Reproduce:
### Steps to Reproduce:
1) download a simple, reproducible data file
http://forge.scilab.org/index.php/p/rdataset/source/file/master/csv/datasets/mtcars.csv
2) run these commands
CREATE TABLE mtcars ( rownames VARCHAR(255) , mpg DOUBLE PRECISION , cyl DOUBLE PRECISION , disp DOUBLE PRECISION , hp DOUBLE PRECISION , drat DOUBLE PRECISION , wt DOUBLE PRECISION , qsec DOUBLE PRECISION , vs DOUBLE PRECISION , am DOUBLE PRECISION , gear DOUBLE PRECISION , carb DOUBLE PRECISION ) ;
COPY 33 offset 2 records into mtcars from 'c:\\users\\anthonyd.kff\\desktop\\mtcars.csv' USING DELIMITERS ',','\n','\"' NULL as '' ;
UPDATE mtcars SET mpg = NULL WHERE cyl = 6 ;
select avg( mpg ) from mtcars ;
select sum( mpg ) , min( mpg ) , max( mpg ) from mtcars ;
select median( mpg ) from mtcars ;
b must be dense-headed
### Actual Results:
explain select median( mpg ) from mtcars ;
+-------------------------------------------------------------------+
| mal |
+===================================================================+
| function user.s6_2{autoCommit=true}():void; |
| X_17 := nil:dbl; |
| barrier X_34 := language.dataflow(); |
| X_2 := sql.mvc(); |
| X_3:bat[:oid,:oid] := sql.tid(X_2,"sys","mtcars"); |
| X_6 := sql.bind(X_2,"sys","mtcars","mpg",0); |
| (X_9,r1_9) := sql.bind(X_2,"sys","mtcars","mpg",2); |
| X_12 := sql.bind(X_2,"sys","mtcars","mpg",1); |
| X_14 := sql.delta(X_6,X_9,r1_9,X_12); |
| X_15 := algebra.leftfetchjoin(X_3,X_14); |
| X_16 := algebra.selectNotNil(X_15); |
| X_17 := aggr.median(X_16); |
| exit X_34; |
| sql.exportValue(1,"sys.mtcars","L1","double",53,0,9,X_17,""); |
| end s6_2; |
+-------------------------------------------------------------------+
plan select median( mpg ) from mtcars ;
+-----------------------------------------------------------------------------+
| rel |
+=============================================================================+
| project ( |
| | group by ( |
| | | table(sys.mtcars) [ mtcars.rownames, mtcars.mpg, mtcars.%TID% NOT NULL |
: ] COUNT :
| | ) [ ] [ sys.median no nil (mtcars.mpg) as L1 ] |
| ) [ L1 ] |
+-----------------------------------------------------------------------------+
5 tuples (0.660ms)
sql>
### Expected Results:
returned the median() value for mpg column of the mtcars data table
## Comment 18706
Date: 2013-05-02 21:31:14 +0200
From: Anthony Damico <<ajdamico>>
sorry, should've included:
MonetDB 5 server v11.15.7 "Feb2013-SP2"
Serving database 'test', using 8 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 7.860 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/JAQL module loaded
MonetDB/SQL module loaded
>
## Comment 18708
Date: 2013-05-03 10:07:08 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0768b9f3fc76](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0768b9f3fc76) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0768b9f3fc76](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0768b9f3fc76)
Changeset description:
Fix bug #3280: sometimes allow non-dense heads in subaggr.
## Comment 18709
Date: 2013-05-03 10:07:56 +0200
From: @sjoerdmullender
Thanks for the report and the test.
The bug is fixed for the next release.
| median function breaks when the column contains NULL values | https://api.github.com/repos/MonetDB/MonetDB/issues/3280/comments | 0 | 2020-11-30T12:31:06Z | 2024-06-27T11:59:46Z | https://github.com/MonetDB/MonetDB/issues/3280 | 753,439,672 | 3,280 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-05-02 14:17:13 +0200
From: milan <<milan.martak>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-07-03 08:47:58 +0200
## Comment 18704
Date: 2013-05-02 14:17:13 +0200
From: milan <<milan.martak>>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
(cannot read version in the list - shows HAS code) so -> i am on MonetDB v11.15.7 (Feb2013-SP2)
when using combination of column aliases with ORDER BY clause, the result set is not correct - it returns repeating value of first column for all columns in the SELECT
see the test cases to reproduce
confirmed as bug by Hannes Muehleisen
Reproducible: Always
### Steps to Reproduce:
*test case 1, no ORDER BY - correct**
**----------------------------------*
WITH SAWITH0 AS ( select 'a' as c1,
'b' as c2,
'c' as c3,
1 as c4 )
select 0 as c1,
D1.c1 as c2,
D1.c2 as c3,
D1.c3 as c4,
D1.c4 as c5
from SAWITH0 D1
*test case 2, add ORDER BY - wrong result (repeats the 1st value for all
columns)*
*--------------------------------------------------------------------------------*
WITH SAWITH0 AS ( select 'a' as c1,
'b' as c2,
'c' as c3,
1 as c4 )
select 0 as c1,
D1.c1 as c2,
D1.c2 as c3,
D1.c3 as c4,
D1.c4 as c5
from SAWITH0 D1
order by 5, 4, 3, 2
--order by c5,c4,c3,c2
**test case 3, use completely different alias with order by - correct **
**-------------------------------------------------------------------*
WITH SAWITH0 AS ( select 'a' as c1,
'b' as c2,
'c' as c3,
1 as c4 )
select 0 as c1,
D1.c1 as a2,
D1.c2 as a3,
D1.c3 as a4,
D1.c4 as a5
from SAWITH0 D1
order by 5, 4, 3, 2
### Actual Results:
1.
+------+------+------+------+------+
| c1 | c2 | c3 | c4 | c5 |
+======+======+======+======+======+
| 0 | a | b | c | 1 |
+------+------+------+------+------+
2.
+------+------+------+------+------+
| c1 | c2 | c3 | c4 | c5 |
+======+======+======+======+======+
| 0 | a | a | a | a |
+------+------+------+------+------+
Note that the result is the same even if you use the column alias
instead of the ord.num.
3.
+------+------+------+------+------+
| c1 | a2 | a3 | a4 | a5 |
+======+======+======+======+======+
| 0 | a | b | c | 1 |
+------+------+------+------+------+
### Expected Results:
1.
+------+------+------+------+------+
| c1 | c2 | c3 | c4 | c5 |
+======+======+======+======+======+
| 0 | a | b | c | 1 |
+------+------+------+------+------+
2.
+------+------+------+------+------+
| c1 | c2 | c3 | c4 | c5 |
+======+======+======+======+======+
| 0 | a | b | c | 1 |
+------+------+------+------+------+
3.
+------+------+------+------+------+
| c1 | a2 | a3 | a4 | a5 |
+======+======+======+======+======+
| 0 | a | b | c | 1 |
+------+------+------+------+------+
## Comment 18707
Date: 2013-05-03 09:30:59 +0200
From: milan <<milan.martak>>
Additional testcases, not sure if related to this bug, the worst one (7) can kill the server:
-----------------------------
Test Case 4 - will emit error
-----------------------------
WITH SAWITH0 AS ( select 2 as c2 ),
SAWITH1 AS ( select 5 as c2, null as c4
UNION ALL
select 5 as c2, 'x' as c4 )
( select
cast(NULL as VARCHAR ( 1 ) ) as c2,
D1.c2 as c7
from SAWITH0 D1
union all
select
D1.c4 as c2,
D1.c2 as c7
from SAWITH1 D1 )
Note: plain UNION will fail too emitting even more errors
-------------------------------------------------------------------
Test Case 5 - correct (note different alias c200000 instead of c2)
-------------------------------------------------------------------
WITH SAWITH0 AS ( select 2 as c2 ),
SAWITH1 AS (select 5 as c2, null as c4
UNION ALL
select 5 as c2, 'x' as c4 )
(select
cast(NULL as VARCHAR ( 1 ) ) as c200000,
D1.c2 as c7
from SAWITH0 D1
union all
select
D1.c4 as c200000,
D1.c2 as c7
from SAWITH1 D1 )
------------------------------------------------------------------------
Test Case 6, modification of 4, just one query from the UNION- correct
------------------------------------------------------------------------
WITH SAWITH0 AS ( select 2 as c2 ),
SAWITH1 AS (select 5 as c2, null as c4
UNION ALL
select 5 as c2, 'x' as c4 )
select
cast(NULL as VARCHAR ( 1 ) ) as c2,
D1.c2 as c7
from SAWITH0 D1
------------------------------------------------------------------------
Test Case 7, add ORDER BY to 6 - error (SIGSEGV)
------------------------------------------------------------------------
WITH SAWITH0 AS ( select 2 as c2 ),
SAWITH1 AS (select 5 as c2, null as c4
UNION ALL
select 5 as c2, 'x' as c4 )
select
cast(NULL as VARCHAR ( 1 ) ) as c2,
D1.c2 as c7
from SAWITH0 D1
ORDER BY 1
## Comment 18712
Date: 2013-05-03 13:07:53 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bf23e8009dd2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bf23e8009dd2) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bf23e8009dd2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bf23e8009dd2)
Changeset description:
Added test for bug #3279.
Hand-approved outputs for failing tests--should be checked.
## Comment 18785
Date: 2013-06-06 19:26:21 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=52ed955b70c9) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9)
Changeset description:
fixed bug #3279 and 3278. We properly look up the order by columns.
And keep table names with all sub-relations.
Fixed bug #3296, ie fixed type checking on table returning functions.
## Comment 18788
Date: 2013-06-07 13:32:18 +0200
From: @njnes
fixed
| column alias combined with ORDER BY returns wrong data | https://api.github.com/repos/MonetDB/MonetDB/issues/3279/comments | 0 | 2020-11-30T12:31:04Z | 2024-06-27T11:59:45Z | https://github.com/MonetDB/MonetDB/issues/3279 | 753,439,634 | 3,279 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-26 18:30:17 +0200
From: Pete Hollobon <<pete>>
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes, pete
Last updated: 2013-07-03 08:47:58 +0200
## Comment 18701
Date: 2013-04-26 18:30:17 +0200
From: Pete Hollobon <<pete>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
When using a column number to specify a column to order by (e.g. "order by 2"), subsequent queries which are identical - apart from the column number ordered by - ignore the the ordering and return identical results to the first query.
Ordering by column name works correctly.
Reproducible: Always
### Steps to Reproduce:
sql>create table testorder (a string, b string);
operation successful (48.648ms)
sql>insert into testorder values ('a', 'z'), ('b', 'y'), ('c', 'x');
3 affected rows (10.922ms)
sql>select * from testorder order by 1;
+------+------+
| a | b |
+======+======+
| a | z |
| b | y |
| c | x |
+------+------+
3 tuples (1.616ms)
sql>select * from testorder order by 2;
### Actual Results:
+------+------+
| a | b |
+======+======+
| a | z |
| b | y |
| c | x |
+------+------+
3 tuples (0.817ms)
### Expected Results:
+------+------+
| a | b |
+======+======+
| c | x |
| b | y |
| a | z |
+------+------+
The MAL is identical for the "order by 1" and "order by 2" variants, looks like a caching bug.
I also tested with integer columns: this also exhibited the bug.
## Comment 18713
Date: 2013-05-03 13:07:56 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1bfb10f341a8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1bfb10f341a8) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1bfb10f341a8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1bfb10f341a8)
Changeset description:
Added test for bug #3278.
## Comment 18784
Date: 2013-06-06 19:26:20 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=52ed955b70c9) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52ed955b70c9)
Changeset description:
fixed bug #3279 and 3278. We properly look up the order by columns.
And keep table names with all sub-relations.
Fixed bug #3296, ie fixed type checking on table returning functions.
| SQL order by <column number> only sorts on first call | https://api.github.com/repos/MonetDB/MonetDB/issues/3278/comments | 0 | 2020-11-30T12:31:01Z | 2024-06-27T11:59:44Z | https://github.com/MonetDB/MonetDB/issues/3278 | 753,439,601 | 3,278 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-25 21:36:16 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: ajdamico
Last updated: 2013-07-03 08:48:02 +0200
## Comment 18696
Date: 2013-04-25 21:36:16 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
Variables created with the query..
create table mtcars2 as select carb , count( distinct case when gear in ( 3 , 4 ) then mpg end ) as prob1 from mtcars group by carb with data ;
..seem to disrupt some of the functions in MonetDB.
on the reproducible example below, these break--
select sign( prob1 ) from mtcars2;
select stddev( prob1 ) from mtcars2;
select stddev_pop( prob1 ) from mtcars2;
--and these work, but they do NOT work on similarly-created data I cannot share.
select median( prob1 ) from mtcars2;
select prod( prob1 ) from mtcars2;
Reproducible: Always
### Steps to Reproduce:
1) download a simple, reproducible data file
http://forge.scilab.org/index.php/p/rdataset/source/file/master/csv/datasets/mtcars.csv
2) run these commands
CREATE TABLE mtcars ( rownames VARCHAR(255) , mpg DOUBLE PRECISION , cyl DOUBLE PRECISION , disp DOUBLE PRECISION , hp DOUBLE PRECISION , drat DOUBLE PRECISION , wt DOUBLE PRECISION , qsec DOUBLE PRECISION , vs DOUBLE PRECISION , am DOUBLE PRECISION , gear DOUBLE PRECISION , carb DOUBLE PRECISION ) ;
COPY 33 offset 2 records into mtcars from 'c:\\users\\anthonyd.kff\\desktop\\mtcars.csv' USING DELIMITERS ',','\n','\"' NULL as '' ;
create table mtcars2 as select carb , count( distinct case when gear in ( 3 , 4 ) then mpg end ) as prob1 from mtcars group by carb with data ;
*THESE BREAK;
select sign( prob1 ) from mtcars2;
select stddev( prob1 ) from mtcars2;
select stddev_pop( prob1 ) from mtcars2;
*THESE WORK;
select median( prob1 ) from mtcars2;
select prod( prob1 ) from mtcars2;
### Actual Results:
sql>select sign( prob1 ) from mtcars2;
TypeException:user.s6_1[16]:'bat.insert' undefined in: _53:any := bat.insert(_43
:bat[:oid,:int], _51:oid, _50:bte)
program contains errors
sql>select stddev( prob1 ) from mtcars2;
SELECT: no such unary operator 'stddev(wrd)'
sql>select stddev_pop( prob1 ) from mtcars2;
SELECT: no such unary operator 'stddev_pop(wrd)'
### Expected Results:
not those.
Additional discussion on monetdb users list under the subject
"All tested on the same column, some functions work, some don't?"
Thanks!!! :)
## Comment 18697
Date: 2013-04-26 11:50:24 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [181e76a702af](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=181e76a702af) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=181e76a702af](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=181e76a702af)
Changeset description:
added test for bug #3277:
The problem is threefold:
1)
As of the Feb2013 release of MonetDB,
stddev() has been replaced by stddev_pop() & stddev_samp(),
i.e., there is no stddev() any more.
We might have failed to communicate this change clearly.
Sorry!
2)
stddev_pop() & stddev_samp() fail on the results of count(),
as the latter returns MonetDB internal type wrd, which is
not a standard/valid SQL type, and (thus?) there is not
implementation of stddev_pop() & stddev_samp() for type wrd.
Explicitly casting the result of count() to a valid standard
SQL integer type (tinying, smallint, integer, bigint) makes
these functions work fine.
Open question is, whether we should simple "treat the symptom"
by adding implementations for stddev_pop() & stddev_samp() on
type wrd, or rather cure the cause by making count() return a
valid standard SQL type, e.g., integer on 32-bit systems and
bigint on 64-bit systems.
3)
sign() seems to fail as the created physical plan tries to
insert a value of type bte into a BAT with tail type int,
and while this should be no problem, there seems to be
no signature that allows this.
We'll need to investigate whether simply adding that
signature is a valid solution, or whether there is a need
to fix the translation of sign().
## Comment 18698
Date: 2013-04-26 13:15:43 +0200
From: Anthony Damico <<ajdamico>>
Sorry I missed the stddev -> stddev_samp, I should've known that. :)
If you're trying to decide on treating the sympton vs. a long-term cure, I hope I can convince you that the cure is much more desirable -- now with the R package MonetDB.R, a lot more statisticians are going to start using MonetDB alongside the R language.. and that means these statistical functions (median and prod too) are going to see a lot more everyday use than they probably currently do.
Thanks for looking at this!! :)
## Comment 18710
Date: 2013-05-03 10:59:58 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7f56b438b044](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7f56b438b044) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7f56b438b044](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7f56b438b044)
Changeset description:
Fix bug #3277: add aggregates on wrd, fix output type of sign.
aggr.sign returns a bat of type bte, so tell SQL about that.
The count aggregate returns a bat of type wrd, so in order to use
aggregates on that result, we need to have those.
Also incorporate test data into test and approve the results.
## Comment 18711
Date: 2013-05-03 11:03:06 +0200
From: @sjoerdmullender
There were two unrelated bugs. The output type of the sign function was marked incorrectly as integer instead of tinyint (i.e. int instead of bte). And the aggregate functions working on the (internal) wrd type were missing. The wrd types leaks out in the result of the count aggregate.
| count( case when COL1 in ( NUM1 , NUM2 ) then COL2 end ) cause problems in functions | https://api.github.com/repos/MonetDB/MonetDB/issues/3277/comments | 0 | 2020-11-30T12:30:59Z | 2024-06-27T11:59:43Z | https://github.com/MonetDB/MonetDB/issues/3277 | 753,439,560 | 3,277 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-22 11:08:04 +0200
From: konstantin.parshikov
To: Merovingian devs <<bugs-merovingian>>
Version: 11.15.3 (Feb2013-SP1)
CC: konstantin.parshikov
Last updated: 2013-04-29 14:51:28 +0200
## Comment 18686
Date: 2013-04-22 11:08:04 +0200
From: konstantin.parshikov
User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:
Linux dw1-1 3.2.0-0.bpo.4-amd64 1 SMP Debian 3.2.32-1~bpo60+1 x86_64
When I'm trying ot start up database I've got following:
$ monetdb start dw
starting database 'dw'... FAILED
start: starting 'dw' failed: database 'dw' started up, but failed to open up a communication channel
merovingian.log
2013-04-17 13:34:58 MSG merovingian[8295]: starting database 'dw', up min/avg/max: 0s/0s/1s, crash average: 0.00 0.00 0.00 (5-5=0)
2013-04-17 13:34:59 MSG merovingian[8295]: sending process 10095 (database 'dw') the TERM signal
2013-04-17 13:34:59 MSG dw[10095]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/dw --set merovingian_uri=mapi:monetdb://dw1-1:50000/dw --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/dw/.mapi.sock --set monet_vault_key=/var/lib/monetdb/dw/.vaultkey --set gdk_nr_threads=16 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-17 13:34:59 MSG dw[10095]: MonetDB 5 server v11.15.3 "Feb2013-SP1"
2013-04-17 13:34:59 MSG dw[10095]: Serving database 'dw', using 16 threads
2013-04-17 13:34:59 MSG dw[10095]: Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
2013-04-17 13:34:59 MSG dw[10095]: Found 11.755 GiB available main-memory.
2013-04-17 13:34:59 MSG dw[10095]: Copyright (c) 1993-July 2008 CWI.
2013-04-17 13:34:59 MSG dw[10095]: Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
2013-04-17 13:34:59 MSG dw[10095]: Visit http://www.monetdb.org/ for further information
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
2013-04-17 13:34:59 MSG dw[10095]: WARNING: LoaderException:loadLibrary:Loading error could not locate library lsst (from within file 'lsst')
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:user.main[1228]:object code for command sql.prelude missing
2013-04-17 13:34:59 MSG dw[10095]: !TypeException:user.main[1228]:'sql.prelude' undefined in: _1228:void := sql.prelude()
2013-04-17 13:34:59 MSG merovingian[8295]: database 'dw' (10095) has exited with exit status 0
2013-04-17 13:34:59 MSG merovingian[8295]: database 'dw' has shut down
2013-04-17 13:34:59 ERR merovingian[8295]: client error: database 'dw' started up, but failed to open up a communication channel
Reproducible: Always
### Steps to Reproduce:
1.Install monetdb
2.create db dw
3. monetdb start dw
## Comment 18687
Date: 2013-04-22 14:23:04 +0200
From: @sjoerdmullender
I can reproduce it. There is a problem with packaging for Debian squeeze. The Ubuntu packages don't have this problem, even though they are created in exactly the same way.
The workaround is: as root run:
cd /usr/lib/monetdb5
for i in *.cpython-31mu.so; do mv $i ${i%.cpython-31mu.so}.so; done
In other words, in the /usr/lib/monetdb5 directory, rename all files that end in .cpython-31mu.so to the equivalent file without the ".cpython-31mu" bit.
## Comment 18688
Date: 2013-04-22 15:19:07 +0200
From: konstantin.parshikov
Thanks.
After renaming i have new problem
monetdb start dw
starting database 'dw'... FAILED
start: starting 'dw' failed: database 'dw' appears to shut itself down after starting, check monetdbd's logfile for possible hints
merovingian.log
2013-04-22 13:04:49 MSG merovingian[11774]: starting database 'dw', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (2-2=0)
2013-04-22 13:04:49 MSG dw[12441]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/dw --set merovingian_uri=mapi:monetdb://dw1-1:50000/dw --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/dw/.mapi.sock --set monet_vault_key=/var/lib/monetdb/dw/.vaultkey --set gdk_nr_threads=16 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-22 13:04:49 MSG dw[12441]: MonetDB 5 server v11.15.3 "Feb2013-SP1"
2013-04-22 13:04:49 MSG dw[12441]: Serving database 'dw', using 16 threads
2013-04-22 13:04:49 MSG dw[12441]: Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
2013-04-22 13:04:49 MSG dw[12441]: Found 11.755 GiB available main-memory.
2013-04-22 13:04:49 MSG dw[12441]: Copyright (c) 1993-July 2008 CWI.
2013-04-22 13:04:49 MSG dw[12441]: Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
2013-04-22 13:04:49 MSG dw[12441]: Visit http://www.monetdb.org/ for further information
2013-04-22 13:04:49 MSG dw[12441]: !MALException:malInclude:could not open file: mal_init
2013-04-22 13:04:49 MSG merovingian[11774]: database 'dw' (12441) has exited with exit status 0
2013-04-22 13:04:49 ERR control[11774]: (local): failed to fork mserver: database 'dw' appears to shut itself down after starting, check monetdbd's logfile for possible hints
## Comment 18689
Date: 2013-04-22 16:13:59 +0200
From: @sjoerdmullender
(In reply to comment 2)
> 2013-04-22 13:04:49 MSG dw[12441]: !MALException:malInclude:could not open
> file: mal_init
There should be a file call mal_init.mal in the same directory /usr/lib/monetdb5. Can you check whether that's there?
After having done the renames I was able to start the server, so I can't reproduce this latest problem.
## Comment 18690
Date: 2013-04-22 16:34:01 +0200
From: @grobian
(In reply to comment 1)
> The workaround is: as root run:
> cd /usr/lib/monetdb5
> for i in *.cpython-31mu.so; do mv $i ${i%.cpython-31mu.so}.so; done
this sounds as the python multiarch thing, perhaps this is an upgraded install?
## Comment 18691
Date: 2013-04-22 16:36:12 +0200
From: @sjoerdmullender
(In reply to comment 4)
> (In reply to comment 1)
> > The workaround is: as root run:
> > cd /usr/lib/monetdb5
> > for i in *.cpython-31mu.so; do mv $i ${i%.cpython-31mu.so}.so; done
>
> this sounds as the python multiarch thing, perhaps this is an upgraded
> install?
It also happens on a new install (I tried).
The problem is in the Debian build system, and specifically in the script dh_python3 which does a rename of all .so files it encounters.
## Comment 18692
Date: 2013-04-22 17:14:29 +0200
From: konstantin.parshikov
/usr/lib/monetdb5 ls -l
total 1468
drwxr-xr-x 2 root root 4096 Apr 22 12:59 autoload
-rw-r--r-- 1 root root 808 Feb 27 15:23 cache.sql
drwxr-xr-x 2 root root 4096 Apr 22 12:59 createdb
-rw-r--r-- 1 root root 1356576 Feb 27 15:23 lib_sql.so
-rw-r--r-- 1 root root 1502 Feb 27 15:23 lsst.sql
-rw-r--r-- 1 root root 1879 Feb 27 15:23 octopus.sql
-rw-r--r-- 1 root root 777 Feb 27 15:23 parts.sql
-rw-r--r-- 1 root root 102374 Feb 27 15:23 sql.mal
-rw-r--r-- 1 root root 850 Feb 27 15:23 temporal.sql
-rw-r--r-- 1 root root 1727 Feb 27 15:23 vault.sql
## Comment 18693
Date: 2013-04-22 17:28:34 +0200
From: @sjoerdmullender
It looks like you have only installed the monetdb5-sql package and not the packages it depends on.
When I try to install monetdb5-sql with apt-get, I see:
The following extra packages will be installed:
libmonetdb-client6 libmonetdb-stream3 libmonetdb9 monetdb5-server
The following NEW packages will be installed:
libmonetdb-client6 libmonetdb-stream3 libmonetdb9 monetdb5-server
monetdb5-sql
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
The package monetdb5-server provides the mal_init.mal file you were missing (and a lot else besides).
## Comment 18694
Date: 2013-04-23 14:12:11 +0200
From: @sjoerdmullender
The original bug seems to be fixed by changeset [054957d3e8ca](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=054957d3e8ca)
If the problem of comment 2 is not fixed, it should be entered as a new bug.
## Comment 18695
Date: 2013-04-23 16:00:55 +0200
From: konstantin.parshikov
Thanks.
Db start up after apt-get remove libmonetdb-client6 libmonetdb-stream3 libmonetdb9 monetdb5-server monetdb5-sql monetdb-client and new installation.
| Problem with starting monetdb on debian sqeeze | https://api.github.com/repos/MonetDB/MonetDB/issues/3276/comments | 0 | 2020-11-30T12:30:56Z | 2024-06-27T11:59:42Z | https://github.com/MonetDB/MonetDB/issues/3276 | 753,439,519 | 3,276 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-20 09:48:48 +0200
From: Elvin <<jr_fan>>
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @mlkersten, @njnes, @drstmane
Last updated: 2013-08-23 14:09:22 +0200
## Comment 18684
Date: 2013-04-20 09:48:48 +0200
From: Elvin <<jr_fan>>
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.3)
Build Identifier:
when I use the mclient command to connect the database, the command line shows the information: internal error while starting mserver.
Then I check the logs file, it shows:
2013-04-20 15:43:50 MSG merovingian[2787]: starting database 'my-first-db', up min/avg/max: 0s/0s/1s, crash average: 0.00 0.00 0.00 (12-12=0)
2013-04-20 15:43:50 MSG my-first-db[2870]: arguments: /usr/bin/mserver5 --dbpath=/home/ahui/monetDB/my-dbfarm/my-first-db --set merovingian_uri=mapi:monetdb://SVN:54321/my-first-db --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/ahui/monetDB/my-dbfarm/my-first-db/.mapi.sock --set monet_vault_key=/home/ahui/monetDB/my-dbfarm/my-first-db/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-20 15:43:50 MSG merovingian[2787]: sending process 2870 (database 'my-first-db') the TERM signal
2013-04-20 15:43:50 MSG my-first-db[2870]: MonetDB 5 server v11.15.3 "Feb2013-SP1"
2013-04-20 15:43:50 MSG my-first-db[2870]: Serving database 'my-first-db', using 4 threads
2013-04-20 15:43:50 MSG my-first-db[2870]: Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
2013-04-20 15:43:50 MSG my-first-db[2870]: Found 7.820 GiB available main-memory.
2013-04-20 15:43:50 MSG my-first-db[2870]: Copyright (c) 1993-July 2008 CWI.
2013-04-20 15:43:50 MSG my-first-db[2870]: Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
2013-04-20 15:43:50 MSG my-first-db[2870]: Visit http://www.monetdb.org/ for further information
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
2013-04-20 15:43:50 MSG my-first-db[2870]: WARNING: LoaderException:loadLibrary:Loading error could not locate library lsst (from within file 'lsst')
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:user.main[1228]:object code for command sql.prelude missing
2013-04-20 15:43:50 MSG my-first-db[2870]: !TypeException:user.main[1228]:'sql.prelude' undefined in: _1228:void := sql.prelude()
2013-04-20 15:43:50 MSG merovingian[2787]: database 'my-first-db' (2870) has exited with exit status 0
2013-04-20 15:43:50 MSG merovingian[2787]: database 'my-first-db' has shut down
2013-04-20 15:43:50 ERR merovingian[2787]: client error: database 'my-first-db' started up, but failed to open up a communication channel
My operation system is Debian 2.6.32-48squeezel. The monetdb version is Feb2013-SP1.
Reproducible: Always
### Steps to Reproduce:
1.monetdbd start /home/monetDB/my-dbfarm
2.mclient -u monetdb -d my-first-db
3.
### Actual Results:
monetdb:internal error while starting mserver, please refer to the logs.
## Comment 18920
Date: 2013-07-18 02:43:01 +0200
From: @mlkersten
Is this bug fixed in the newer releases?
## Comment 18923
Date: 2013-07-18 08:57:14 +0200
From: @drstmane
Did you install the pre-built binary Debian packages, or did you compile MonetDB yourself from sources?
| internal error while starting mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/3275/comments | 0 | 2020-11-30T12:30:53Z | 2024-06-28T07:23:21Z | https://github.com/MonetDB/MonetDB/issues/3275 | 753,439,487 | 3,275 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-11 14:15:17 +0200
From: Pete Hollobon <<pete>>
To: clients devs <<bugs-clients>>
Version: 11.15.3 (Feb2013-SP1)
CC: pete
Last updated: 2013-04-29 14:51:28 +0200
## Comment 18682
Date: 2013-04-11 14:15:17 +0200
From: Pete Hollobon <<pete>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31
Build Identifier:
There is only a Bourne shell script for running the tests for the Python clients at present. I've attached a patch that adds cmd (batch) files for running the tests on Windows.
Reproducible: Always
## Comment 18683
Date: 2013-04-11 14:15:35 +0200
From: Pete Hollobon <<pete>>
Created attachment 193
Patch
> Attached file: [python-run-tests-windows.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3274_python-run-tests-windows.patch_193) (text/plain, 883 bytes)
> Description: Patch
## Comment 18699
Date: 2013-04-26 15:16:04 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [265b7615030a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=265b7615030a) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=265b7615030a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=265b7615030a)
Changeset description:
Added run scripts for testing the Python interface on Windows.
The scripts were provided by Pete Hollobon in bug #3274.
I did remove the double quotes since they tend to end up in the value
of the environment variables on Windows.
## Comment 18700
Date: 2013-04-26 15:16:56 +0200
From: @sjoerdmullender
The scripts have been added.
| Add scripts to run Python client tests on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/3274/comments | 0 | 2020-11-30T12:30:51Z | 2024-06-27T11:59:40Z | https://github.com/MonetDB/MonetDB/issues/3274 | 753,439,461 | 3,274 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-11 14:06:18 +0200
From: Pete Hollobon <<pete>>
To: clients devs <<bugs-clients>>
Version: 11.15.7 (Feb2013-SP2)
CC: @gijzelaerr, pete
Last updated: 2014-02-20 15:03:00 +0100
## Comment 18681
Date: 2013-04-11 14:06:18 +0200
From: Pete Hollobon <<pete>>
Created attachment 192
Patch
The Python DBAPI client currently lacks support for timetz, url and inet types.
The attached patch implements support for these types.
> Attached file: [monetdb-python-types.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3273_monetdb-python-types.patch_192) (application/octet-stream, 10657 bytes)
> Description: Patch
## Comment 18702
Date: 2013-05-02 14:08:23 +0200
From: @gijzelaerr
Maybe I'm wrong, but the inet datatype test Pete Hollobon supplied fails. When I change the conversion function from strip to str it works. MAPI doesn't add parentheses around the inet datatype.
I've committed the fixed patch. Thanks Pete!
## Comment 18703
Date: 2013-05-02 14:12:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [9677b89dd8fb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9677b89dd8fb) made by Gijs Molenaar <g.j.molenaar@uva.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9677b89dd8fb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9677b89dd8fb)
Changeset description:
fixed and accepted patch submitted by Pete Hollobon (bug #3273)
## Comment 19617
Date: 2014-02-20 15:03:00 +0100
From: @sjoerdmullender
Jan2014 has been released.
| Add support to Python DBAPI package for timetz, inet and url types | https://api.github.com/repos/MonetDB/MonetDB/issues/3273/comments | 0 | 2020-11-30T12:30:49Z | 2024-06-27T11:59:39Z | https://github.com/MonetDB/MonetDB/issues/3273 | 753,439,437 | 3,273 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-10 15:38:23 +0200
From: mdobryakov
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-08-23 14:08:29 +0200
## Comment 18680
Date: 2013-04-10 15:38:23 +0200
From: mdobryakov
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Firefox/20.0
Build Identifier:
Hello,
My DB was corrupter after several crashes of mserver5. Now I can't repair database. Could you please try to diagnose problem?
Backtrace:
0 0x00007ffff7a40148 in strPut () from /usr/lib64/libbat.so.9
1 0x00007ffff79e9b01 in BATappend () from /usr/lib64/libbat.so.9
2 0x00007ffff7aa84fd in logger_readlog () from /usr/lib64/libbat.so.9
3 0x00007ffff7aa946c in logger_new () from /usr/lib64/libbat.so.9
4 0x00007ffff7aaa966 in logger_create () from /usr/lib64/libbat.so.9
5 0x00007ffff1216dd9 in bl_create () from /usr/lib64/monetdb5/lib_sql.so
6 0x00007ffff120f3aa in store_init () from /usr/lib64/monetdb5/lib_sql.so
7 0x00007ffff11bd050 in mvc_init () from /usr/lib64/monetdb5/lib_sql.so
8 0x00007ffff11402ad in SQLprelude () from /usr/lib64/monetdb5/lib_sql.so
9 0x0000003584a4d0fb in runMALsequence () from /usr/lib64/libmonetdb5.so.14
10 0x0000003584a4e827 in runMAL () from /usr/lib64/libmonetdb5.so.14
11 0x0000003584a6da21 in MALengine () from /usr/lib64/libmonetdb5.so.14
12 0x0000003584a6e572 in malBootstrap () from /usr/lib64/libmonetdb5.so.14
13 0x0000003584a3619a in mal_init () from /usr/lib64/libmonetdb5.so.14
14 0x0000000000402885 in main ()
Log:
2013-04-10 13:18:12 MSG merovingian[48918]: proxying client 172.31.92.210:58204 for database 'stat' to mapi:monetdb:///data/monetdb/stat/.mapi.sock?database=stat
2013-04-10 13:18:12 MSG merovingian[48918]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2013-04-10 13:18:18 MSG merovingian[48918]: database 'stat' (25356) was killed by signal SIGSEGV
2013-04-10 13:18:18 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:17:43, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2849-0=2849)
2013-04-10 13:18:18 MSG merovingian[48918]: proxying client localhost.localdomain:42815 for database 'stat' to mapi:monetdb:///data/monetdb/stat/.mapi.sock?database=stat
2013-04-10 13:18:18 MSG stat[25420]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:18 MSG stat[25420]: MonetDB 5 server v11.15.4
2013-04-10 13:18:18 MSG stat[25420]: This is an unreleased version
2013-04-10 13:18:18 MSG stat[25420]: Serving database 'stat', using 24 threads
2013-04-10 13:18:18 MSG stat[25420]: Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked
2013-04-10 13:18:18 MSG stat[25420]: Found 62.878 GiB available main-memory.
2013-04-10 13:18:18 MSG stat[25420]: Copyright (c) 1993-July 2008 CWI.
2013-04-10 13:18:18 MSG stat[25420]: Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
2013-04-10 13:18:18 MSG stat[25420]: Visit http://www.monetdb.org/ for further information
2013-04-10 13:18:18 MSG stat[25420]: Listening for UNIX domain connection requests on mapi:monetdb:///data/monetdb/stat/.mapi.sock
2013-04-10 13:18:18 MSG stat[25420]: MonetDB/SQL module loaded
2013-04-10 13:18:18 MSG merovingian[48918]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2013-04-10 13:18:18 MSG merovingian[48918]: proxying client localhost.localdomain:42816 for database 'stat' to mapi:monetdb:///data/monetdb/stat/.mapi.sock?database=stat
2013-04-10 13:18:18 MSG merovingian[48918]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2013-04-10 13:18:18 MSG merovingian[48918]: proxying client localhost.localdomain:42817 for database 'stat' to mapi:monetdb:///data/monetdb/stat/.mapi.sock?database=stat
2013-04-10 13:18:18 MSG merovingian[48918]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2013-04-10 13:18:36 MSG merovingian[48918]: proxying client 172.31.92.210:58205 for database 'stat' to mapi:monetdb:///data/monetdb/stat/.mapi.sock?database=stat
2013-04-10 13:18:36 MSG merovingian[48918]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2013-04-10 13:18:41 MSG merovingian[48918]: database 'stat' (25420) was killed by signal SIGSEGV
2013-04-10 13:18:41 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:18:18, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2850-0=2850)
2013-04-10 13:18:41 MSG stat[25472]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:41 MSG merovingian[48918]: database 'stat' (25472) has crashed (dumped core)
2013-04-10 13:18:41 ERR merovingian[48918]: client error: database 'stat' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
2013-04-10 13:18:41 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:18:41, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2851-0=2851)
2013-04-10 13:18:42 MSG stat[25477]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:42 MSG merovingian[48918]: database 'stat' (25477) has crashed (dumped core)
2013-04-10 13:18:42 ERR merovingian[48918]: client error: database 'stat' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
2013-04-10 13:18:42 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:18:41, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2852-0=2852)
2013-04-10 13:18:42 MSG stat[25482]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:42 MSG merovingian[48918]: database 'stat' (25482) has crashed (dumped core)
2013-04-10 13:18:42 ERR merovingian[48918]: client error: database 'stat' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
2013-04-10 13:18:42 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:18:42, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2853-0=2853)
2013-04-10 13:18:43 MSG stat[25487]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:43 MSG merovingian[48918]: database 'stat' (25487) has crashed (dumped core)
2013-04-10 13:18:43 ERR merovingian[48918]: client error: database 'stat' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
2013-04-10 13:18:43 MSG merovingian[48918]: database 'stat' has crashed after start on 2013-04-10 13:18:42, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 1.00 1.00 (2854-0=2854)
2013-04-10 13:18:43 MSG stat[25492]: arguments: /usr/bin/mserver5 --dbpath=/data/monetdb/stat --set merovingian_uri=mapi:monetdb://app-0-22.spb.nexg.tv:50000/stat --set mapi_open=false --set mapi_port=0 --set mapi_usock=/data/monetdb/stat/.mapi.sock --set monet_vault_key=/data/monetdb/stat/.vaultkey --set gdk_nr_threads=24 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2013-04-10 13:18:43 MSG merovingian[48918]: database 'stat' (25492) has crashed (dumped core)
Database file from /data/monetdb/stat: https://www.dropbox.com/s/pztnxvi3kmurtby/stat.tar.gz
Reproducible: Always
### Steps to Reproduce:
Happens every time when I exec: monetdb start stat
I think DB file help you to reproduce problem: https://www.dropbox.com/s/pztnxvi3kmurtby/stat.tar.gz
This problem appear after several unsuccessful connection through JDBC driver (I think).
This version was compiled from sources (branch Feb2013) for CentOS.
$ mserver5 --version
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 62.9GiB available memory, 24 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0 29 Mar 2010 (compiled with OpenSSL 1.0.0-fips 29 Mar 2010)
libxml2: 2.7.6 (compiled with 2.7.6)
Compiled by: root@build-1-2.mwm.local (x86_64-redhat-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 19026
Date: 2013-08-18 17:11:49 +0200
From: @njnes
the database looks corrupt indeed. Do you know why the stat database crashed that many times?
## Comment 19030
Date: 2013-08-19 10:30:43 +0200
From: mdobryakov
I think these crashes related to unsuccess connections through JDBC driver. I suppose you can reproduce it use SQuirreL SQL client (http://squirrel-sql.sourceforge.net/) and official MonetDB JDBC driver.
## Comment 19062
Date: 2013-08-23 14:08:29 +0200
From: @njnes
I cannot reproduce this. Do you have a sequence of statements (server restarts) which produces this problem.
| Segmentation fault in strPut () from /usr/lib64/libbat.so.9 | https://api.github.com/repos/MonetDB/MonetDB/issues/3272/comments | 0 | 2020-11-30T12:30:46Z | 2024-06-27T11:59:38Z | https://github.com/MonetDB/MonetDB/issues/3272 | 753,439,407 | 3,272 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-06 01:02:00 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: 11.17.9 (Jan2014)
CC: @mlkersten
Last updated: 2015-11-11 10:46:52 +0100
## Comment 18679
Date: 2013-04-06 01:02:00 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
I have issued:
- Query that took much longer than I had anticipated; group by on distinct selection
- monetdb stop kv6
- monetdb start kv6
- Simple query
I see that all the string columns have corrupted. The "not null" once appear as '', for the nullable ones have records have data, the other are null. This is the same codebase after Sjoerd's string fix.
The total number of records is: 66063560 (and as always is available).
Reproducible: Didn't try
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18730
Date: 2013-05-14 16:05:53 +0200
From: @sjoerdmullender
(In reply to comment 0)
> I see that all the string columns have corrupted. The "not null" once appear
> as '', for the nullable ones have records have data, the other are null.
Sorry, I can't parse this paragraph.
## Comment 18949
Date: 2013-07-30 20:44:23 +0200
From: @grobian
store corruption
## Comment 21512
Date: 2015-11-11 10:46:52 +0100
From: @mlkersten
No additional information to proceed and code base has changed significantly since reporting.
| After issue monetdb stop, restarting destroyed an entire varchar column | https://api.github.com/repos/MonetDB/MonetDB/issues/3271/comments | 0 | 2020-11-30T12:30:44Z | 2024-06-28T07:23:20Z | https://github.com/MonetDB/MonetDB/issues/3271 | 753,439,380 | 3,271 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-03 09:56:41 +0200
From: @drstmane
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2013-05-03 15:46:51 +0200
## Comment 18671
Date: 2013-04-03 09:56:41 +0200
From: @drstmane
The manpages on the MonetDB website [1] are not up-to-date with the actual man pages (`man <xyz>`) of the latest Feb2013-SP1 release.
[1] http://www.monetdb.org/Documentation/monetdbd
## Comment 18714
Date: 2013-05-03 15:46:51 +0200
From: @sjoerdmullender
I have just updated the man pages on the drupal site.
| manpages on MonetDB web site are outdated | https://api.github.com/repos/MonetDB/MonetDB/issues/3270/comments | 0 | 2020-11-30T12:30:41Z | 2024-06-27T11:59:36Z | https://github.com/MonetDB/MonetDB/issues/3270 | 753,439,356 | 3,270 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-03 02:10:56 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: jpfourny, @njnes
Last updated: 2013-07-03 08:47:59 +0200
## Comment 18666
Date: 2013-04-03 02:10:56 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
I did the following query;
sql>copy 8583682 records into adres from '/mnt/database/openkvk/adres.tsv' delimiters '\n','\t' null as '';
With the result:
mserver5: gdk_utils.c:728: GDKfree_: Assertion `(size & 2) == 0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffeb774700 (LWP 15358)]
0x00007ffff49625b5 in raise () from /lib64/libc.so.6
(gdb) bt
0 0x00007ffff49625b5 in raise () from /lib64/libc.so.6
1 0x00007ffff4963a38 in abort () from /lib64/libc.so.6
2 0x00007ffff495b632 in ?? () from /lib64/libc.so.6
3 0x00007ffff495b6e2 in __assert_fail () from /lib64/libc.so.6
4 0x00007ffff6fa70b1 in GDKfree_ (blk=0x7fffbba7f020) at gdk_utils.c:728
5 0x00007ffff6fa71ae in GDKfree (blk=0x7fffbba7f020) at gdk_utils.c:757
6 0x00007ffff7a5a485 in SQLload_file (cntxt=0x649168, as=0x7fffeb773190, b=0x7fffdc0ae020, out=0x0, csep=0x7fffdc0ae110 "\n", rsep=0x7fffdc0ae000 "\t", quote=0 '\000', skip=-3623171,
maxrow=8583682) at tablet.c:1701
7 0x00007fffec1e2698 in mvc_import_table (cntxt=0x649168, m=0x7fffdc005470, bs=0x7fffdc0ae020, sname=0x7fffdc0a96a0 "sys", tname=0x7fffdc0ace90 "adres", sep=0x7fffdc0ae110 "\n",
rsep=0x7fffdc0ae000 "\t", ssep=0x0, ns=0x7fffdc0ad7c0 "", sz=8583682, offset=0, locked=0) at sql_result.c:675
8 0x00007fffec1f2668 in mvc_import_table_wrap (cntxt=0x649168, mb=0x7fffdc082380, stk=0x7fffdc0bb890, pci=0x7fffdc0b6350) at sql.mx:4185
9 0x00007ffff7827828 in runMALsequence (cntxt=0x649168, mb=0x7fffdc082380, startpc=1, stoppc=0, stk=0x7fffdc0bb890, env=0x0, pcicaller=0x0) at mal_interpreter.c:642
10 0x00007ffff7826ced in callMAL (cntxt=0x649168, mb=0x7fffdc082380, env=0x7fffeb773cb8, argv=0x7fffeb773d10, debug=0 '\000') at mal_interpreter.c:469
11 0x00007fffec1b4a2e in SQLexecutePrepared (c=0x649168, be=0x7fffdc05cf80, q=0x7fffdc088a00) at sql_scenario.c:1844
12 0x00007fffec1b4e12 in SQLengineIntern (c=0x649168, be=0x7fffdc05cf80) at sql_scenario.c:1911
13 0x00007fffec1b5383 in SQLengine (c=0x649168) at sql_scenario.c:2012
14 0x00007ffff7854c36 in runPhase (c=0x649168, phase=4) at mal_scenario.c:522
15 0x00007ffff7854e1f in runScenarioBody (c=0x649168) at mal_scenario.c:566
16 0x00007ffff7854f42 in runScenario (c=0x649168) at mal_scenario.c:586
17 0x00007ffff7855fb4 in MSserveClient (dummy=0x649168) at mal_session.c:431
18 0x00007ffff4cddf3b in start_thread () from /lib64/libpthread.so.0
19 0x00007ffff4a1865d in clone () from /lib64/libc.so.6
Reproducible: Always
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18667
Date: 2013-04-03 02:16:18 +0200
From: @skinkie
I am aware that I reversed the \n and \t.
## Comment 18734
Date: 2013-05-15 23:08:20 +0200
From: Joseph <<jpfourny>>
I am seeing this, too. Every CSV I tried to bulk-load MonetDB with causes a crash. I am using the 64-bit Windows build (same release date).
## Comment 18789
Date: 2013-06-07 13:35:41 +0200
From: @njnes
we need an example to be able to fix this problem. Ie ddl and update statements, including data to be loaded.
## Comment 18790
Date: 2013-06-07 14:05:44 +0200
From: @skinkie
CREATE TABLE "sys"."adres" (
"openbareruimtenaam" VARCHAR(80),
"huisnummer" DECIMAL(5),
"huisletter" CHAR(1),
"huisnummertoevoeging" VARCHAR(4),
"postcode" VARCHAR(6),
"woonplaatsnaam" VARCHAR(80),
"gemeentenaam" VARCHAR(80),
"provincienaam" VARCHAR(16),
"typeadresseerbaarobject" VARCHAR(3),
"adresseerbaarobject" DECIMAL(16),
"nummeraanduiding" DECIMAL(16),
"x" INTEGER,
"y" INTEGER
);
Link to the data data will fly to you in a private mail.
## Comment 18792
Date: 2013-06-07 15:19:48 +0200
From: @njnes
out of bounds problem. We now properly check for this.
## Comment 18795
Date: 2013-06-07 15:49:17 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [11a7d8d94a7b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=11a7d8d94a7b) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=11a7d8d94a7b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=11a7d8d94a7b)
Changeset description:
fixed bug #3269, ie out of bounds write.
| copy into results into gdk_utils.c:728: GDKfree_: Assertion `(size & 2) == 0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/3269/comments | 0 | 2020-11-30T12:30:39Z | 2024-06-27T11:59:35Z | https://github.com/MonetDB/MonetDB/issues/3269 | 753,439,318 | 3,269 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-03 01:48:48 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @drstmane
Duplicates: #3261
Last updated: 2013-04-03 12:44:51 +0200
## Comment 18665
Date: 2013-04-03 01:48:48 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
sql>select kvks, bedrijfsnaam, length(bedrijfsnaam) from kvk where bedrijfsnaam ilike 'Caf%' limit 25;
+---------+--------------------------+---------------------+
| kvks | bedrijfsnaam | length_bedrijfsnaam |
+=========+==========================+=====================+
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1002828 | | 0 |
| 1004254 | | 0 |
| 1004443 | | 0 |
| 1005754 | | 0 |
| 1005904 | | 0 |
| 1006104 | | 0 |
| 1006248 | Café-Slijterij "De Ster" | 24 |
+---------+--------------------------+---------------------+
25 tuples (143.974ms)
sql>select bedrijfsnaam from kvk where length(bedrijfsnaam) = 0;
+--------------+
| bedrijfsnaam |
+==============+
+--------------+
0 tuples (1.0s)
sql>select kvks, bedrijfsnaam, postcode, plaats from kvk where kvks in (1002828, 1004254, 1004443, 1005754, 1005904, 1006104);
+---------+--------------------------------------------+----------+--------------+
| kvks | bedrijfsnaam | postcode | plaats |
+=========+============================================+==========+==============+
| 1002828 | CAF | 8912AA | LEEUWARDEN |
| 1002828 | CAF | 8421PJ | OLDEBERKOOP |
| 1002828 | CAF | 8411KG | JUBBEGA |
| 1002828 | CAF | 8447RH | HEERENVEEN |
| 1002828 | CAF | 9206AD | DRACHTEN |
| 1002828 | CAF | 9101BA | DOKKUM |
| 1002828 | CAF | 8801JK | FRANEKER |
| 1002828 | CAF | 9206AJ | DRACHTEN |
| 1002828 | CAF | 8912AH | LEEUWARDEN |
| 1002828 | CAF | 9206AP | DRACHTEN |
| 1002828 | CAF | 8471AR | WOLVEGA |
| 1002828 | CAF | 8531HJ | LEMMER |
| 1002828 | CAF | 8701PP | BOLSWARD |
| 1002828 | CAF | 9073GA | MARRUM |
| 1002828 | CAF | 8723AX | KOUDUM |
| 1002828 | CAF | 9008SJ | ROORDAHUIZUM |
| 1002828 | CAF | 8606VP | SNEEK |
| 1002828 | CAF | 9291MA | KOLLUM |
| 1002828 | C.A.F.-WINKEL WYNJEWOUDE | 9241HS | WIJNJEWOUDE |
| 1002828 | CAF | 8912AB | LEEUWARDEN |
| 1004254 | Café Zaal 't Hert | 8501AR | Joure |
| 1004443 | CAFE HET WAPEN VAN FRIESLAND | 8723AT | KOUDUM |
| 1005754 | Café "De Rustende Jager" | 8474CL | Oldeholtpade |
| 1005904 | Café Restaurant "Old Inn" | 9101AB | Dokkum |
| 1006104 | Hotel-Café-Restaurant De Groene Weide B.V. | 8701XD | Bolsward |
| 1006104 | CAFE-RESTAURANT "'T WAPEN VAN WONSERADEEL" | 8701WS | BOLSWARD |
| 1006104 | LUNCHROOM 'T POORTJE | 8701HL | BOLSWARD |
+---------+--------------------------------------------+----------+--------------+
27 tuples (7.775ms)
Full database is available.
Reproducible: Always
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18672
Date: 2013-04-03 09:59:28 +0200
From: @drstmane
Appears to be related to bug #3261.
I also vaguely recall having seen similar problems either in some other bug report or on a mailing list --- unfortunately, I don't recall the details ...
## Comment 18675
Date: 2013-04-03 11:48:12 +0200
From: @sjoerdmullender
Can you test with the latest change on the Feb2013 branch (at least changeset 745ff1012a26)? I think this may well have fixed this bug.
## Comment 18676
Date: 2013-04-03 12:05:06 +0200
From: @skinkie
Thanks Sjoerd, that fixes it for me!
## Comment 18677
Date: 2013-04-03 12:44:51 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #3261 ***
| ilike, length, plain data giving different results (probably encoding related) | https://api.github.com/repos/MonetDB/MonetDB/issues/3268/comments | 0 | 2020-11-30T12:30:36Z | 2024-06-28T07:23:20Z | https://github.com/MonetDB/MonetDB/issues/3268 | 753,439,285 | 3,268 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-04-02 22:36:08 +0200
From: @skinkie
To: Merovingian devs <<bugs-merovingian>>
Version: 11.15.3 (Feb2013-SP1)
CC: @drstmane
Last updated: 2013-04-03 09:51:41 +0200
## Comment 18663
Date: 2013-04-02 22:36:08 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
sql>drop user dbslayer;
operation successful (299.495ms)
sql>CREATE USER "dbslayer" WITH PASSWORD 'xxxxx' NAME 'DBSlayer' SCHEMA "sys";
/opt/monetdb/bin/mclient -d openkvk
user(skinkie):dbslayer
password:
server is running in maintenance mode, please try again later
I tried if monetdb stop and monetdb start worked, which it didn't. I created a different user, which also results into the same error message.
Reproducible: Always
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18664
Date: 2013-04-02 23:27:07 +0200
From: @skinkie
While my 'monetdb' user was able to log in, the other user was not. I could solve it with monetdb openkvk release. I don't know if there are 'two' states of "maintenance mode".
It wasn't very obvious from:
/opt/monetdb/bin/monetdb status
name state health remarks
openkvk LR 1m 100% 14h
It might be good for documentation and user guidance to mention something at the error.
## Comment 18668
Date: 2013-04-03 07:20:18 +0200
From: @grobian
You just need to "release" the database, as your status shows, it's locked.
The examples do that. It's the first thing after create in
http://www.monetdb.org/Documentation/Tutorial
## Comment 18669
Date: 2013-04-03 08:50:59 +0200
From: @skinkie
Why is the monetdb user able to log in when the database is 'locked'?
## Comment 18670
Date: 2013-04-03 09:51:41 +0200
From: @drstmane
See `man monetdb` for documentation.
The administrator needs to be able to log in to perform the maintenance in maintenance mode. User "monetdb" is the administrator of MonetDB.
| "Correct" user results into "server is running in maintenance mode, please try again later" | https://api.github.com/repos/MonetDB/MonetDB/issues/3267/comments | 0 | 2020-11-30T12:30:33Z | 2024-06-28T07:23:20Z | https://github.com/MonetDB/MonetDB/issues/3267 | 753,439,255 | 3,267 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-30 22:38:31 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-08-18 17:08:21 +0200
## Comment 18660
Date: 2013-03-30 22:38:31 +0100
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
After a succesfully was succesfully created, and a rollback was issued due to a copy into failure, the next attemped showed that the user already existed. I tried to remove this user and saw;
sql>drop user dbslayer;
DROP ROLE: no such role 'dbslayer'
sql>drop user dbslayer;
DROP USER: no such user: 'dbslayer'
sql>drop user dbslayer;
DROP ROLE: no such role 'dbslayer'
Reproducible: Always
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 19025
Date: 2013-08-18 17:08:21 +0200
From: @njnes
this is fixed in the current stable and default
| DROP USER "fails" with DROP ROLE: no such role | https://api.github.com/repos/MonetDB/MonetDB/issues/3266/comments | 0 | 2020-11-30T12:30:31Z | 2024-06-27T11:59:32Z | https://github.com/MonetDB/MonetDB/issues/3266 | 753,439,224 | 3,266 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-30 22:30:12 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
Last updated: 2013-07-03 08:48:01 +0200
## Comment 18659
Date: 2013-03-30 22:30:12 +0100
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Build Identifier:
create table test (x decimal(9,9));
insert into test values (0.123456789); [works]
COPY 1 RECORDS INTO "sys"."test" FROM stdin USING DELIMITERS '\t','\n','"';
0.123456789
value '0.123456789' from line 1 field 1 not inserted, expecting type decimal(9,9)
failed to import table
Reproducible: Always
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30 (compiled with 8.32)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: root@openkvk.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 18717
Date: 2013-05-06 17:14:00 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [21a4449a8c0e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=21a4449a8c0e) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21a4449a8c0e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21a4449a8c0e)
Changeset description:
Don't count leading zeros when importing decimals.
This fixes bug #3265.
Also added test.
| import decimal with copy into fails | https://api.github.com/repos/MonetDB/MonetDB/issues/3265/comments | 0 | 2020-11-30T12:30:28Z | 2024-06-27T11:59:31Z | https://github.com/MonetDB/MonetDB/issues/3265 | 753,439,202 | 3,265 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-29 12:42:46 +0100
From: milan <<milan.martak>>
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes
Last updated: 2013-04-29 14:51:28 +0200
## Comment 18655
Date: 2013-03-29 12:42:46 +0100
From: milan <<milan.martak>>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
The mclient will close connection when executing
SELECT <func> as <alias> ... FROM <aview> GROUP BY <alias>
where <func> is
extract(month from <column>) AS <alias>
merovingian.log shows there was database crash
2013-03-29 10:22:40 MSG merovingian[2446]: database 'zkdev1' (17036) was killed by signal SIGSEGV
2013-03-29 10:37:29 MSG merovingian[2446]: database 'zkdev1' has crashed after start on 2013-03-29 10:21:30, attempting restart, up min/avg/max: 2m/1d/1w, crash average: 1.00 1.00 0.60 (31-13=18)
this can be reproduced at any time - see the test case in "Steps to Reproduce"
Reproducible: Always
### Steps to Reproduce:
1.
CREATE VIEW mmtest_v AS SELECT date'2012-01-01' as period, 1 as quantity;
2.
SELECT extract(month from period) as m, count(1) as cnt FROM mmtest_v GROUP BY m;
### Actual Results:
Connection terminated + database killed by signal SIGSEGV
### Expected Results:
query result, i.e.
m cnt
--- ---
1 1
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffee3d5700 (LWP 25583)]
0x00007fffef493ffb in exp_alias_or_copy (sql=0x7fffe0005470, tname=0x0, cname=0x0, orel=0x0, old=0x7fffe00cd720, settname=0) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:185
185 ne = exp_column(sql->sa, nme, nme, exp_subtype(old), orel->card, has_nil(old), is_intern(old));
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-3.fc15.x86_64 cfitsio-3.280-2.fc16.x86_64 cyrus-sasl-lib-2.1.23-27.fc16.x86_64 geos-3.3.1-1.fc16.x86_64 glibc-2.14.90-24.fc16.9.x86_64 keyutils-libs-1.5.2-1.fc16.x86_64 krb5-libs-1.9.4-3.fc16.x86_64 libcom_err-1.41.14-2.fc15.x86_64 libcurl-7.21.7-8.fc16.x86_64 libgcc-4.6.3-2.fc16.x86_64 libidn-1.22-3.fc16.x86_64 libselinux-2.1.6-6.fc16.x86_64 libssh2-1.2.7-4.fc16.x86_64 libstdc++-4.6.3-2.fc16.x86_64 libuuid-2.20.1-2.3.fc16.x86_64 libxml2-2.7.8-8.fc16.x86_64 ncurses-libs-5.9-2.20110716.fc16.x86_64 nspr-4.9.4-1.fc16.x86_64 nss-3.14.1-3.fc16.x86_64 nss-softokn-freebl-3.14.1-3.fc16.x86_64 nss-util-3.14.1-1.fc16.x86_64 openldap-2.4.26-8.fc16.x86_64 openssl-1.0.0j-1.fc16.x86_64 pcre-8.12-9.fc16.x86_64 readline-6.2-2.fc16.x86_64 zlib-1.2.5-7.fc16.x86_64
(gdb) bt
0 0x00007fffef493ffb in exp_alias_or_copy (sql=0x7fffe0005470, tname=0x0, cname=0x0, orel=0x0, old=0x7fffe00cd720, settname=0) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:185
1 0x00007fffef4a2896 in _rel_aggr (sql=0x7fffe0005470, rel=0x7fffee3d4900, distinct=0, aggrstr=0x7fffe00cc1e0 "count", args=0x7fffe00cc350, f=3) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:3771
2 0x00007fffef4a2d37 in rel_aggr (sql=0x7fffe0005470, rel=0x7fffee3d4900, se=0x7fffe00cc380, f=3) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:3832
3 0x00007fffef4a5992 in rel_value_exp2 (sql=0x7fffe0005470, rel=0x7fffee3d4900, se=0x7fffe00cc380, f=3, ek=..., is_last=0x7fffee3d4814) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:4543
4 0x00007fffef4a6267 in rel_value_exp (sql=0x7fffe0005470, rel=0x7fffee3d4900, se=0x7fffe00cc380, f=3, ek=...) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:4691
5 0x00007fffef4a634c in column_exp (sql=0x7fffe0005470, rel=0x7fffee3d4900, column_e=0x7fffe00cc430, f=3) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:4704
6 0x00007fffef4a65af in rel_column_exp (sql=0x7fffe0005470, rel=0x7fffee3d4900, column_e=0x7fffe00cc430, f=3) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:4748
7 0x00007fffef4a794b in rel_select_exp (sql=0x7fffe0005470, rel=0x7fffe00cd610, outer=0x0, sn=0x7fffe00cc7c0, ek=...) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:5059
8 0x00007fffef4a8ba7 in rel_query (sql=0x7fffe0005470, rel=0x0, sq=0x7fffe00cc7c0, toplevel=1, ek=...) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:5304
9 0x00007fffef4aa2fc in rel_subquery (sql=0x7fffe0005470, rel=0x0, sq=0x7fffe00cc7c0, ek=...) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:5660
10 0x00007fffef4aa393 in rel_selects (sql=0x7fffe0005470, s=0x7fffe00cc7c0) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_select.c:5671
11 0x00007fffef49363c in rel_semantic (sql=0x7fffe0005470, s=0x7fffe00cc7c0) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/server/rel_semantic.c:263
12 0x00007fffef41ccc6 in sql_symbol2relation (c=0x7fffe0005470, sym=0x7fffe00cc7c0) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/backends/monet5/sql.mx:1723
13 0x00007fffef3e93ab in SQLparser (c=0x648b28) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/sql/backends/monet5/sql_scenario.c:1666
14 0x00007ffff7a73367 in runPhase (c=0x648b28, phase=1) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:522
15 0x00007ffff7a7365f in runScenarioBody (c=0x648b28) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:587
16 0x00007ffff7a73826 in runScenario (c=0x648b28) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:616
17 0x00007ffff7a748a0 in MSserveClient (dummy=0x648b28) at /ufs/manegold/_/Monet/HG/Feb2013/source/MonetDB/monetdb5/mal/mal_session.c:431
18 0x0000003cf3c07d90 in start_thread () from /lib64/libpthread.so.0
19 0x0000003cf30f119d in clone () from /lib64/libc.so.6
(gdb) li
180 } else if (!cname) {
181 char name[16], *nme;
182 nme = number2name(name, 16, ++sql->label);
183
184 exp_setname(sql->sa, old, nme, nme);
185 ne = exp_column(sql->sa, nme, nme, exp_subtype(old), orel->card, has_nil(old), is_intern(old));
186 ne->p = prop_copy(sql->sa, old->p);
187 return ne;
188 } else if (cname && !old->name) {
189 exp_setname(sql->sa, old, tname, cname);
(gdb) p sql
$1 = (mvc *) 0x7fffe0005470
(gdb) p sql->sa
$2 = (sql_allocator *) 0x7fffe007aeb0
(gdb) p *sql
$3 = {errstr = "\000ELECT: identifier 'm' unknown\000wn", '\000' <repeats 8158 times>, sa = 0x7fffe007aeb0, qc = 0x7fffe00075d0, clientid = 1, scanner = {rs = 0x7fffe8006c30, ws = 0x7fffe8004b20, log = 0x0, yynext = 0, yylast = 259, yysval = 80, yyval = 377, yycur = 81, yybak = 10 '\n',
as = 0, key = 203, started = 1, mode = LINE_N, schema = 0x0}, params = 0x0, vars = 0x7fffe0007610, topvars = 9, sizevars = 32, frame = 1, use_views = 0, args = 0x7fffe0007e30, argc = 1, argmax = 32, sym = 0x7fffe00cc7c0, point_query = 0, user_id = 3, role_id = 3, last_id = -1,
timezone = 3600000, cache = 100, caching = 100, history = 0, reply_size = -1, sizeheader = 0, debug = 0, emode = 0 '\000', emod = 0 '\000', session = 0x7fffe0007f50, type = 0, label = 1, cascade_action = 0x0, opt_stats = {0, 0, 0, 0, 0, 0, 0, 0}, result_id = 1, results = 0x0, times = {
tms_utime = 0, tms_stime = 0, tms_cutime = 0, tms_cstime = 0}, Tparse = 0}
(gdb) p *sql->sa
$4 = {size = 64, nr = 1, blks = 0x7fffe0082800, used = 6256, usedmem = 111904}
(gdb) p nme
$5 = 0x7fffee3d452d "L1"
(gdb) p old
$6 = (sql_exp *) 0x7fffe00cd720
(gdb) p *old
$7 = {type = e_atom, name = 0x7fffe00cd7b0 "L1", rname = 0x7fffe00cd7c0 "L1", l = 0x0, r = 0x0, f = 0x0, flag = 0, card = 1 '\001', tpe = {type = 0x19eb3b0, digits = 8, scale = 0, comp_type = 0x0}, used = 0, p = 0x0}
(gdb) p orel
$8 = (sql_rel *) 0x0
## Comment 18656
Date: 2013-03-29 12:46:13 +0100
From: milan <<milan.martak>>
Created attachment 191
gdb trace created by Stefan M.
> Attached file: [gdb_trace_segfault_view_select.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3264_gdb_trace_segfault_view_select.txt_191) (text/plain, 6406 bytes)
> Description: gdb trace created by Stefan M.
## Comment 18657
Date: 2013-03-29 12:49:31 +0100
From: @njnes
fixed crash in exp_alias_or_copy, there is no enclosing orel in this case.
## Comment 18658
Date: 2013-03-29 12:50:20 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [329bbb4c5564](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=329bbb4c5564) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=329bbb4c5564](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=329bbb4c5564)
Changeset description:
fixed bug #3264
| select + group by expression alias from a view kills database by signal SIGSEGV | https://api.github.com/repos/MonetDB/MonetDB/issues/3264/comments | 0 | 2020-11-30T12:30:25Z | 2024-06-27T11:59:30Z | https://github.com/MonetDB/MonetDB/issues/3264 | 753,439,169 | 3,264 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-25 17:24:02 +0100
From: leo
To: clients devs <<bugs-clients>>
Version: 11.21.19 (Jul2015-SP4)
CC: martin.van.dinther
Last updated: 2016-08-04 17:42:46 +0200
## Comment 18650
Date: 2013-03-25 17:24:02 +0100
From: leo
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
When using microsoft ETL tool (SSIS) to load data from SQL Into MonetDB, I choosed ODBC for destination and enabled the Bulk Insert selection.
I am wondering if it used the bulk insert. It inserted data with auto committe mode.
Reproducible: Always
## Comment 22281
Date: 2016-08-04 17:42:46 +0200
From: Martin van Dinther <<martin.van.dinther>>
For questions please use the users mailing list, see https://www.monetdb.org/Developers/Mailinglists
Please use Bugzilla only for bugs or enhancement requests.
To see which ODBC calls are sent from SSIS to the MonetDB ODBC driver you can enable the ODBC logging via the ODBC panel and analyse the log file contents.
For bulk inserts ODBC function SQLBulkOperations(hStmt, SQL_ADD) is typically called.
See also: https://msdn.microsoft.com/en-us/library/windows/desktop/ms712471(v=vs.85).aspx
Currently MonetDB ODBC driver has not implemented SQLBulkOperations() functionality.
For information and tips on loading data in bulk see:
https://www.monetdb.org/Documentation/Cookbooks/SQLrecipes/LoadingBulkData
| Using MS SSIS for BULK Insert | https://api.github.com/repos/MonetDB/MonetDB/issues/3263/comments | 0 | 2020-11-30T12:30:22Z | 2024-06-28T07:23:19Z | https://github.com/MonetDB/MonetDB/issues/3263 | 753,439,134 | 3,263 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-25 12:41:37 +0100
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2013-03-25 14:55:39 +0100
## Comment 18648
Date: 2013-03-25 12:41:37 +0100
From: @drstmane
changeset [2c634aabaff8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2c634aabaff8) "fixed memory leak"
makes tests
sql/test/concurrent/Tests/crash_on_concurrent_use.SF-1411926
sql/test/BugTracker-2013/Tests/perl-undef-0.Bug-3235
sql/test/BugTracker-2011/Tests/perl-short-read-bug.Bug-2897
fail with
"
mserver5(63246,0xb0509000) malloc:
*** error for object 0x1969801: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
"
or abort with
"
*** glibc detected *** mserver5: free(): invalid pointer: 0xf5846cc9 ***
"
or segfault.
See
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47281:e501b202c0ed&target=GNU-Fedora-i386-propcheck-dbfarm&module=sql&test=sql%2Ftest%2Fconcurrent%2Fcrash_on_concurrent_use.SF-1411926&which=err
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47281:e501b202c0ed&target=GNU-Darwin-i386-propcheck&module=sql&test=sql%2Ftest%2FBugTracker-2013%2Fperl-undef-0.Bug-3235&which=err
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47281:e501b202c0ed&target=GNU-Darwin-i386-propcheck&module=sql&test=sql%2Ftest%2FBugTracker-2011%2Fperl-short-read-bug.Bug-2897&which=err
## Comment 18649
Date: 2013-03-25 14:55:10 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [b01b7d0d7ac7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b01b7d0d7ac7) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b01b7d0d7ac7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b01b7d0d7ac7)
Changeset description:
sql_gencode: fixed bug #3262 & changeset [2c634aabaff8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2c634aabaff8)
make sure, we free the genuine base pointer.
| changeset 2c634aabaff8 makes tests fail, abort, segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/3262/comments | 0 | 2020-11-30T12:30:20Z | 2024-06-27T11:59:28Z | https://github.com/MonetDB/MonetDB/issues/3262 | 753,439,103 | 3,262 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-22 18:46:48 +0100
From: Milena Ivanova <<M.Ivanova>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @drstmane, @skinkie
Last updated: 2013-05-06 16:10:40 +0200
## Comment 18645
Date: 2013-03-22 18:46:48 +0100
From: Milena Ivanova <<M.Ivanova>>
Incorrect query results over a string column with no empty string values. Some queries show empty string as a result, others display correct values.
The problem is reproducible, it appears when the table has more than 5M rows, and the missing values are consistent (ranges rmm1-rmm10, 183-192, etc.)
table definition
create table rock_qtl3(
probename varchar(64),
markername varchar(64),
qtl real );
correct values
select * from rock_qtl3 where probename='AGIUSA1234' and markername like 'rmm_' limit 15;
+------------+------------+-----------------+
| probename | markername | qtl |
+============+============+=================+
| AGIUSA1234 | rmm1 | 0.107853971 |
| AGIUSA1234 | rmm2 | 0.107853971 |
| AGIUSA1234 | rmm3 | 0.107853971 |
| AGIUSA1234 | rmm4 | 0.158719465 |
| AGIUSA1234 | rmm5 | 0.107853971 |
| AGIUSA1234 | rmm6 | 0.107853971 |
| AGIUSA1234 | rmm7 | 0.107853971 |
| AGIUSA1234 | rmm8 | 0.130806118 |
| AGIUSA1234 | rmm9 | 0.0857530013 |
+------------+------------+-----------------+
incorrect values
select * from rock_qtl3 where probename='AGIUSA1234' limit 15;
+------------+------------+-----------------+
| probename | markername | qtl |
+============+============+=================+
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.158719465 |
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.107853971 |
| AGIUSA1234 | | 0.130806118 |
| AGIUSA1234 | | 0.0857530013 |
| AGIUSA1234 | | 0.0850726515 |
| AGIUSA1234 | rmm11 | 0.178307399 |
| AGIUSA1234 | rmm12 | 0.275123864 |
| AGIUSA1234 | rmm13 | 0.145893753 |
| AGIUSA1234 | rmm14 | 0.145893753 |
| AGIUSA1234 | rmm15 | 0.0447690487 |
+------------+------------+-----------------+
Test data and scripts available in ~milena/monetdb_test
## Comment 18673
Date: 2013-04-03 09:59:54 +0200
From: @drstmane
Bug #3268 appear to be related to this one.
I also vaguely recall having seen similar problems either in some other bug report or on a mailing list --- unfortunately, I don't recall the details ...
## Comment 18674
Date: 2013-04-03 11:45:51 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [745ff1012a26](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=745ff1012a26) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=745ff1012a26](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=745ff1012a26)
Changeset description:
Make sure the whole heap gets copied if that's what we want.
When going from malloced to mmapped heap memory, HEAPextend only
copies what it says in the free field. When GDKupgradevarheap needs
to copy everything (copyall is set), we need to temporarily set free
to the size of the whole heap.
This fixes bug #3261, and presumably also bu 3268.
## Comment 18678
Date: 2013-04-03 12:44:51 +0200
From: @sjoerdmullender
*** Bug #3268 has been marked as a duplicate of this bug. ***
## Comment 18715
Date: 2013-05-06 16:09:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bad6f014778c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bad6f014778c) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bad6f014778c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bad6f014778c)
Changeset description:
Added test for bug #3261.
## Comment 18716
Date: 2013-05-06 16:10:40 +0200
From: @sjoerdmullender
Closing since the fix is already in the SP2 release and we now also have a test.
| Incorrect empty string values in query results | https://api.github.com/repos/MonetDB/MonetDB/issues/3261/comments | 0 | 2020-11-30T12:30:17Z | 2024-06-27T11:59:27Z | https://github.com/MonetDB/MonetDB/issues/3261 | 753,439,069 | 3,261 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-22 02:08:00 +0100
From: Masood Mortazavi <<masoodmortazavi>>
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: @mlkersten
Last updated: 2013-05-14 17:00:04 +0200
## Comment 18641
Date: 2013-03-22 02:08:00 +0100
From: Masood Mortazavi <<masoodmortazavi>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
The active links shown for the MonetDB MAL modules on the following page are broken:
http://www.monetdb.org/Documentation/Manuals/MonetDB/Modules
They all lead to the top age instead of the module-specific pages, assuming they exist.
Reproducible: Always
### Steps to Reproduce:
1. Go to http://www.monetdb.org/Documentation/Manuals/MonetDB/Modules
2. Click on any of the active links for any of the MAL modules listed
3. Get redirected to Home page (through a redirect to http://www.monetdb.org/Home<MobuleName>) instead of the actual document on the MAL module.
### Actual Results:
No documentation on MAL modules can be seen although there seems to be some links to them.
### Expected Results:
To see the documents if there are active links to them.
## Comment 18642
Date: 2013-03-22 02:08:44 +0100
From: Masood Mortazavi <<masoodmortazavi>>
There are two lists on the URL noted.
It is only the top list that's broken.
## Comment 18643
Date: 2013-03-22 04:38:23 +0100
From: @mlkersten
Thanks for pointing this out. The top list references have been fixed, but a lot of work remains to be done. Most of the text originates from the deprecated version 4 code base.
## Comment 18732
Date: 2013-05-14 17:00:04 +0200
From: @sjoerdmullender
All links on the page seem to work properly now.
| Broken MAL Modules Links | https://api.github.com/repos/MonetDB/MonetDB/issues/3260/comments | 0 | 2020-11-30T12:30:15Z | 2024-06-27T11:59:26Z | https://github.com/MonetDB/MonetDB/issues/3260 | 753,439,042 | 3,260 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-21 16:53:56 +0100
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes
Last updated: 2015-03-22 00:16:35 +0100
## Comment 18631
Date: 2013-03-21 16:53:56 +0100
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22
Build Identifier:
The following bit of SQL:
ROLLBACK;
START TRANSACTION;
CREATE TABLE treeitems (
"tree" CHARACTER LARGE OBJECT,
"subject" INTEGER,
"pre" BIGINT,
"post" BIGINT,
"size" BIGINT,
"level" TINYINT,
"prob" DOUBLE DEFAULT 1.0,
CONSTRAINT "treeitems_tree_pre_unique" UNIQUE ("tree", "pre"),
CONSTRAINT "treeitems_tree_post_unique" UNIQUE ("tree", "post")
);
explain
SELECT t1.subject as id1, t2.subject as id2
FROM treeitems t1, treeitems t2
WHERE t2.pre between t1.pre and t1.pre + t1.size;
On Jun2012 (notice X_15, which calls a BATrangejoin):
| function user.s1_1():void; |
| X_25 := nil:bat[:oid,:int]; |
| X_29 := nil:bat[:oid,:int]; |
| barrier X_50 := language.dataflow(); |
| X_1 := sql.mvc(); |
| X_2:bat[:oid,:lng] := sql.bind(X_1,"spinque","treeitems","pre",0); |
| X_7:bat[:oid,:oid] := sql.bind_dbat(X_1,"spinque","treeitems",1); |
| X_9 := bat.reverse(X_7); |
| X_10 := algebra.kdifference(X_2,X_9); |
| X_11:bat[:oid,:lng] := sql.bind(X_1,"spinque","treeitems","size",0); |
| X_13 := algebra.kdifference(X_11,X_9); |
| X_14:bat[:oid,:lng] := batcalc.+(X_10,X_13); |
| X_15 := algebra.join(X_10,X_10,X_14,true,true); |
| X_17 := bat.reverse(X_15); |
| X_18 := algebra.markT(X_17,0@0:oid); |
| X_19 := bat.reverse(X_18); |
| X_20:bat[:oid,:int] := sql.bind(X_1,"spinque","treeitems","subject",0); |
| X_25 := algebra.leftjoin(X_19,X_20); |
| X_27 := algebra.markT(X_15,0@0:oid); |
| X_28 := bat.reverse(X_27); |
| X_29 := algebra.leftjoin(X_28,X_20); |
| exit X_50; |
| X_31 := sql.resultSet(2,1,X_25); |
| sql.rsColumn(X_31,"spinque.t1","id1","int",32,0,X_25); |
| sql.rsColumn(X_31,"spinque.t2","id2","int",32,0,X_29); |
| X_40 := io.stdout(); |
| sql.exportResult(X_40,X_31); |
| end s1_1; |
On Feb2013 (notice X9, X_26, X22):
| function user.s7_1():void; |
| X_32:bat[:oid,:int] := nil:bat[:oid,:int]; |
| X_34:bat[:oid,:int] := nil:bat[:oid,:int]; |
| barrier X_54 := language.dataflow(); |
| X_1 := sql.mvc(); |
| X_2:bat[:oid,:oid] := sql.tid(X_1,"spinque","treeitems"); |
| X_5 := sql.bind(X_1,"spinque","treeitems","tree",0); |
| X_8 := algebra.leftfetchjoin(X_2,X_5); |
| (X_9,r1_18) := algebra.crossproduct(X_8,X_8); |
| X_11 := sql.bind(X_1,"spinque","treeitems","pre",0); |
| X_13 := algebra.leftfetchjoin(X_2,X_11); |
| X_14 := algebra.leftfetchjoin(X_9,X_13); |
| X_15 := algebra.leftfetchjoin(r1_18,X_13); |
| X_26:bat[:oid,:bit] := batcalc.>=(X_14,X_15); |
| X_16 := sql.bind(X_1,"spinque","treeitems","size",0); |
| X_20:bat[:oid,:lng] := algebra.leftfetchjoinPath(r1_18,X_2,X_16); |
| X_21:bat[:oid,:lng] := batcalc.+(X_15,X_20); |
| X_22:bat[:oid,:bit] := batcalc.<=(X_14,X_21); |
| X_23 := algebra.subselect(X_22,true,true,true,true,false); |
| X_27 := algebra.subselect(X_26,X_23,true,true,true,true,false); |
| X_28 := sql.bind(X_1,"spinque","treeitems","subject",0); |
| X_31 := algebra.leftfetchjoin(X_2,X_28); |
| X_32:bat[:oid,:int] := algebra.leftfetchjoinPath(X_27,r1_18,X_31); |
| X_34:bat[:oid,:int] := algebra.leftfetchjoinPath(X_27,X_9,X_31); |
| language.pass(X_8); |
| language.pass(X_13); |
| language.pass(X_15); |
| language.pass(X_14); |
| language.pass(X_2); |
| language.pass(r1_18); |
| language.pass(X_27); |
| language.pass(X_9); |
| language.pass(X_31); |
| exit X_54; |
| X_36 := sql.resultSet(2,1,X_32); |
| sql.rsColumn(X_36,"spinque.t1","id1","int",32,0,X_32); |
| sql.rsColumn(X_36,"spinque.t2","id2","int",32,0,X_34); |
| X_46 := io.stdout(); |
| sql.exportResult(X_46,X_36); |
| end s7_1; |
This version is no option: the crossproduct filled up my entire disk.
Reproducible: Always
### Actual Results:
crossproduct + <= + >=
### Expected Results:
rangejoin
MonetDB 5 server v11.15.4 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.31 2012-07-06 (compiled with 8.31)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e-fips 11 Feb 2013)
libxml2: 2.9.0 (compiled with 2.9.0)
Compiled by: roberto@photon.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18634
Date: 2013-03-21 20:16:07 +0100
From: @njnes
Fixed by improving the function down optimizer (sql_add needs to be done first) and improved renaming of expressions in this optimizer.
## Comment 18635
Date: 2013-03-21 20:19:54 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [6e71a843ec7d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6e71a843ec7d) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6e71a843ec7d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6e71a843ec7d)
Changeset description:
fixed bug #3259
The rel_push_func_down optimizer didn't push down expressions from
joins
## Comment 18646
Date: 2013-03-25 09:47:02 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [ee9ebeb0d48c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ee9ebeb0d48c) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee9ebeb0d48c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee9ebeb0d48c)
Changeset description:
between.Bug-3259: approved single-threaded output (MAL plan)
## Comment 18890
Date: 2013-06-24 00:23:52 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [d8b80fc7ff83](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d8b80fc7ff83) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d8b80fc7ff83](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d8b80fc7ff83)
Changeset description:
between.Bug-3259: propagated changesets [52ed955b70c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=52ed955b70c9) & [054504135056](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=054504135056) to single-threaded output
## Comment 19159
Date: 2013-09-15 22:32:33 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [d0b65a3e8eb6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d0b65a3e8eb6) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d0b65a3e8eb6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d0b65a3e8eb6)
Changeset description:
between.Bug-3259: approved new MAL plan after changeset [79e66f677113](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=79e66f677113)
## Comment 19393
Date: 2013-12-04 20:40:12 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [66984fb5abf0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=66984fb5abf0) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=66984fb5abf0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=66984fb5abf0)
Changeset description:
between.Bug-3259: propagated changeset [bbcf019e6fef](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bbcf019e6fef) to single-threaded output
## Comment 20321
Date: 2014-10-28 23:46:16 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [a7700c816e32](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a7700c816e32) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7700c816e32](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7700c816e32)
Changeset description:
between.Bug-3259: propagated changeset [192a529eaa4a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=192a529eaa4a) to single-threaded output
## Comment 20737
Date: 2015-03-22 00:16:35 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [a5dbe5a04a60](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a5dbe5a04a60) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a5dbe5a04a60](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a5dbe5a04a60)
Changeset description:
between.Bug-3259: approved non-int128 output after recent changes
| BETWEEN clause not producing rangejoin | https://api.github.com/repos/MonetDB/MonetDB/issues/3259/comments | 0 | 2020-11-30T12:30:12Z | 2024-06-27T11:59:25Z | https://github.com/MonetDB/MonetDB/issues/3259 | 753,439,012 | 3,259 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-18 07:51:43 +0100
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.15 (Feb2013-SP4)
Last updated: 2013-12-03 13:59:32 +0100
## Comment 18624
Date: 2013-03-18 07:51:43 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
When you have a big query running, all worker threads are busy.
Then trying to connect with another mclient is hindered, because
all instructions are merged into a global queue. This most likely
means you can not easily stop the big query.
Solutions: either have a worker set per Client connection (preferred) or
change scheduler to better balance instructions.
Reproducible: Always
### Steps to Reproduce:
1. run sf100
2. separate start of mclient to perform a sys.pause(x)
3.
## Comment 19003
Date: 2013-08-15 23:57:29 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3669ddd28bf0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3669ddd28bf0) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3669ddd28bf0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3669ddd28bf0)
Changeset description:
New thread group per dataflow block
The centralized worker thread group could lead to an unacceptable
situation. If a user is heavily processing complex queries, then
no other user could even log into the system, for its MAL statements
ended up at the end of the shared queues.
The problem has been resolved by introducing a thread group per dataflow
block. This may lead to a large number of processes, whose resources
are managed by the OS.
It solves bug #3258
## Comment 19162
Date: 2013-09-18 18:01:45 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8a77f78a4fe4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8a77f78a4fe4) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8a77f78a4fe4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8a77f78a4fe4)
Changeset description:
Revert creating dataflow pools per client and fix problem differently.
When a MAL function calls language.dataflow(), the thread executing
the call waits until the whole dataflow block is executed by the other
threads in the dataflow pool. If this is done recursively, we go
through all available threads and all threads end up waiting for their
dataflow block to finish, which doesn't happen since there are no
worker threads available anymore. The solution that was tried before
was to create N threads whenever language.dataflow() was called, and
those threads never exited. This can very quickly cause very many
threads to be created (I have seen over 1300 threads on a system with
many cores). The current solutions instead creates a single extra
thread whenever a thread is blocked waiting for the dataflow block to
be finished, and when the block is finished, it stops a single thread
(possibly a different one, but who cares: the result is the same).
This may also fix bug #3258 in a different way then the original fix.
## Comment 19163
Date: 2013-09-18 19:33:16 +0200
From: @mlkersten
This 'new' solution does not handle the main problem addressed with the thread
pool per client!
The point is that once a complex/expensive query is started from a fixed pool
it effectively blocks (administrative) SQL access to the server for querying.
Such server access is needed to inspect the query queue and kill e.g. the rogue query. => there should be a worker pool /client session !
Also parallel execution of concurrent queries is left to the OS thread scheduling.
If you want to reduce the poolt hen garbage collect the threads set aside per client when his session terminates.
Recursion will now also still create a large number threads(=equal to the recursion depth. Thereby not addressing the real problem. The MAL interpreter
has a high-water mark to stop too deeply recursive function calls (against
stack overflow). A similar approach should be considered if you want to
control the number processes. => The stack depth can be used to assess if dataflow parallelism should be used. Otherwise, simply continue in serial mode.
(I thought it already did so)
I propose to revert this patch in the light of this consideration.
## Comment 19164
Date: 2013-09-18 19:51:19 +0200
From: @mlkersten
DFLOWinitialize... here we stop parallel interpretation and continue serial
MT_lock_unset(&mal_contextLock, "DFLOWinitialize");
if (grp > THREADS) {
// continue non-parallel
return -1;
}
runMALdataflow.... here we stop parallel processing if there are too many pools
/* too many threads turns dataflow processing off */
if ( cntxt->idx > MAXQ){
*ret = TRUE;
return MAL_SUCCEED;
}
Recursive calls can 'steal' a worker pool, because the recursive function may
have to be ran in parallel as well.
Also if you can not create a worker thread we continue with serial execution
On a large multicore system you may end up with MAXQ * THREADS processes
## Comment 19165
Date: 2013-09-18 20:42:27 +0200
From: @mlkersten
A test like this could be used also in dataflow to turn off parallel processing
if ((unsigned)stk->stkdepth > THREAD_STACK_SIZE / sizeof(mb->var[0]) / 4 && THRhighwater())
/* we are running low on stack space */
## Comment 19323
Date: 2013-11-05 14:05:56 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [21892a4f04a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=21892a4f04a1) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21892a4f04a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21892a4f04a1)
Changeset description:
Fix for bug #3258.
We now maintain a pool of N-1 generic worker threads which is extended
by one client-specific worker thread for each client that enters the
dataflow code.
## Comment 19324
Date: 2013-11-05 15:20:20 +0100
From: @sjoerdmullender
Unless proven otherwise, this is now fixed.
## Comment 19376
Date: 2013-12-03 13:59:32 +0100
From: @sjoerdmullender
Feb2013-SP6 has been released.
| Scheduling issues | https://api.github.com/repos/MonetDB/MonetDB/issues/3258/comments | 0 | 2020-11-30T12:30:09Z | 2024-06-27T11:59:24Z | https://github.com/MonetDB/MonetDB/issues/3258 | 753,438,971 | 3,258 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-15 02:58:53 +0100
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: ajdamico, @hannesmuehleisen
Last updated: 2013-04-29 14:51:27 +0200
## Comment 18618
Date: 2013-03-15 02:58:53 +0100
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
sql>select stddev_pop(pppymt_ip) from b09;
sql>select stddev_samp(pppymt_ip) from b09;
But then include any GROUP BY and they break--
sql>select stddev_pop(pppymt_ip) from b09 group by metro;
sql>select stddev_samp(pppymt_ip) from b09 group by metro;
Reproducible: Always
### Steps to Reproduce:
1. run any select statement using stddev_samp and stddev_pop without aggregation
2. run the same select statement, using GROUP BY
### Actual Results:
TypeException:user.s6_1[9]:'aggr.substdev' undefined in: _17:bat[:any,:dbl] := a
ggr.substdev(_3:bat[:oid,:dbl], _14:bat[:oid,:oid], r1_14:bat[:oid,:oid], _1:bit
)
program contains errors
TypeException:user.s5_1[9]:'aggr.substdevp' undefined in: _17:bat[:any,:dbl] :=
aggr.substdevp(_3:bat[:oid,:dbl], _14:bat[:oid,:oid], r1_14:bat[:oid,:oid], _1:b
it)
program contains errors
### Expected Results:
aggregated standard deviation calculations
## Comment 18621
Date: 2013-03-15 14:48:54 +0100
From: @sjoerdmullender
Changeset [862c0ec8510d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=862c0ec8510d) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=862c0ec8510d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=862c0ec8510d)
Changeset description:
aggr.stdev{,] and aggr.variance{,p} need "abort_on_error" argument.
This fixes bug #3257.
## Comment 18622
Date: 2013-03-15 14:56:11 +0100
From: @sjoerdmullender
Changeset [c2f138d54d2e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c2f138d54d2e) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c2f138d54d2e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c2f138d54d2e)
Changeset description:
Added test for bug #3257.
| stddev_pop and stddev_samp break during a GROUP BY | https://api.github.com/repos/MonetDB/MonetDB/issues/3257/comments | 0 | 2020-11-30T12:30:07Z | 2024-06-27T11:59:22Z | https://github.com/MonetDB/MonetDB/issues/3257 | 753,438,947 | 3,257 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-13 03:21:15 +0100
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.3 (Feb2013-SP1)
CC: @mlkersten
Last updated: 2013-03-27 00:31:48 +0100
## Comment 18616
Date: 2013-03-13 03:21:15 +0100
From: @drstmane
Since changeset [2663022e4670](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2663022e4670) tests
monetdb5/optimizer/Tests/tst4631.mal
and
monetdb5/optimizer/Tests/common.mal
fail with Feb2013 branch.
It looks as if they no longer produce a listing of the (optimized?) MAL plan !??
## Comment 18630
Date: 2013-03-21 01:51:37 +0100
From: @drstmane
For the records, these tests are no longer active in the development branch, as they us group.refine respectively group.new/group.derive ; cf.,
http://dev.monetdb.org/hg/MonetDB/diff/b420d353d3b4/monetdb5/optimizer/Tests/All
## Comment 18651
Date: 2013-03-26 23:36:06 +0100
From: @drstmane
The difference stems from the fact the mdb.list() does not produce any output anymore.
The reason for this is that OPTwrapper() (monetdb5/optimizer/opt_wrapper.c) now (since changeset 2663022e4670) triggers an exception on missing/unknown optimizers. The tests ask for optimizer constants, which does exist, but is unknown to OPTwrapper() (not listed in the codes array) and thus OPTwrapper() triggers an exception.
However, this exception never surfaces as it is silently swallowed by runScenarioBody() (monetdb5/mal/mal_scenario.c).
Simply not swallowing but showing the exception in runScenarioBody(), e.g., via
diff -r [2c16ac0e23ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2c16ac0e23ba) monetdb5/mal/mal_scenario.c
--- a/monetdb5/mal/mal_scenario.c Tue Mar 26 19:35:27 2013 +0100
+++ b/monetdb5/mal/mal_scenario.c Tue Mar 26 23:33:21 2013 +0100
@@ -542,6 +542,7 @@
/* we should actually show it [postponed]
mnstr_printf(c->fdout,"!%s\n",msg);
*/
+ showException(GDKout, MAL, "runScenarioBody", "%s", msg);
if (msg != M5OutOfMemory)
GDKfree(msg);
msg = MAL_SUCCEED;
appears to cause more harm than solving this problem.
Thus, I'll most probably resort to merely avoiding the initial trigger (for this very case, only) by adding the constants optimizer to the codes array in monetdb5/optimizer/opt_wrapper.c ...
## Comment 18652
Date: 2013-03-27 00:05:41 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [8f0ef1f692c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8f0ef1f692c9) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8f0ef1f692c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8f0ef1f692c9)
Changeset description:
OPTwrapper: add optimizer "constants"
this keeps OPTwrapper() from raising an exception with tests
monetdb5/optimizer/Tests/tst4631.mal
and
monetdb5/optimizer/Tests/common.mal
(which is later silently swalled by runScenarioBody();
see bug #3256 for details)
and thus makes these tests work, again.
Also approved minor output changes.
## Comment 18653
Date: 2013-03-27 00:05:45 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [942a9594e434](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=942a9594e434) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=942a9594e434](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=942a9594e434)
Changeset description:
check the return value of optimizeMALBlock() and propagate exceptions as necessary
Thus, changeset [2663022e4670](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2663022e4670) finally has a (visible) effect,
except from the case where runScenarioBody() silently swallows exceptions
(cf., bug #3256).
## Comment 18654
Date: 2013-03-27 00:31:48 +0100
From: @drstmane
Tests work, again. closing.
| M5 tests monetdb5/optimizer/Tests/tst4631.mal & monetdb5/optimizer/Tests/common.mal fail after changeset 2663022e4670 | https://api.github.com/repos/MonetDB/MonetDB/issues/3256/comments | 0 | 2020-11-30T12:30:04Z | 2024-06-27T11:59:21Z | https://github.com/MonetDB/MonetDB/issues/3256 | 753,438,916 | 3,256 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-12 23:22:46 +0100
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.11 (Feb2013-SP3)
CC: @mlkersten
Last updated: 2013-09-27 13:47:18 +0200
## Comment 18615
Date: 2013-03-12 23:22:46 +0100
From: @drstmane
In the Feb2013 branch, tests
monetdb5/optimizer/Tests/inlineFunction.mal
and
monetdb5/optimizer/Tests/ifthencst.mal
fail since changeset [207ed7d7e03a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=207ed7d7e03a)
(cf. http://dev.monetdb.org/hg/MonetDB/rev/207ed7d7e03a)
as the optimizer(s) now seem to produce different output / MAL plans;
see also
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46925:1a234210f142&target=GNU-Fedora-x86_64-propcheck-assert&module=monetdb5&test=monetdb5%2Foptimizer%2FinlineFunction&which=out
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46925:1a234210f142&target=GNU-Fedora-x86_64-propcheck-assert&module=monetdb5&test=monetdb5%2Foptimizer%2Fifthencst&which=out
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46925:1a234210f142/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/monetdb5%2Foptimizer%2FinlineFunction
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46925:1a234210f142/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/monetdb5%2Foptimizer%2Fifthencst
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46925:1a234210f142/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer%2FinlineFunction
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46925:1a234210f142/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer%2Fifthencst
In case these are acceptable / expected / intended / desired changes, the new output should be approved accordingly.
Otherwise, the respective code should be fixed.
## Comment 19004
Date: 2013-08-16 07:57:38 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ee10d1630870](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ee10d1630870) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee10d1630870](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee10d1630870)
Changeset description:
Look for constants after evaluation
This should fix bug #3255
## Comment 19005
Date: 2013-08-16 07:59:49 +0200
From: @mlkersten
should be done with
## Comment 19006
Date: 2013-08-16 08:51:50 +0200
From: @drstmane
These tests did & do fail in the Feb2013 branch, only,
but did and do not fail in the default branch.
## Comment 19007
Date: 2013-08-16 13:26:25 +0200
From: @drstmane
In the Feb2013 branch, these test, and this this bug appear to be fixed by changeset [62ed11377998](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=62ed11377998) (i.e., not changeset ee10d1630870).
| M5 tests inlineFunction & ifthencst fail since changeset 207ed7d7e03a | https://api.github.com/repos/MonetDB/MonetDB/issues/3255/comments | 0 | 2020-11-30T12:30:02Z | 2024-06-27T11:59:20Z | https://github.com/MonetDB/MonetDB/issues/3255 | 753,438,886 | 3,255 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-12 11:15:17 +0100
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @gijzelaerr, @mlkersten
Last updated: 2013-03-15 09:31:01 +0100
## Comment 18613
Date: 2013-03-12 11:15:17 +0100
From: @drstmane
cf.
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47169:7d1c376e995f&target=GNU-Fedora-x86_64-propcheck-assert&module=sql&test=sql%2Ftest%2Fconcurrent%2Fcrash_on_concurrent_use.SF-1411926&which=out
Not sure, whether this is due to querylog related changes or possibly due to Python API changes (this ".py" test makes any use of the actual python API at all) ...
## Comment 18614
Date: 2013-03-12 22:53:15 +0100
From: @drstmane
The test now also fails on the Feb2013 branch; cf.,
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47184:6cdd774f7dc5&target=GNU-Fedora-x86_64-propcheck-assert&module=sql&test=sql%2Ftest%2Fconcurrent%2Fcrash_on_concurrent_use.SF-1411926&which=out
Hence, it is likely to be related to / triggered by the Python API changes in changeset [87b4e5b9b5c0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=87b4e5b9b5c0)
(http://dev.monetdb.org/hg/MonetDB/rev/87b4e5b9b5c0)
## Comment 18617
Date: 2013-03-14 13:32:44 +0100
From: @gijzelaerr
I think the new behavior is the behavior we want to have.
There is a set of queries executed in the script:
'''
select count(*) from tables;
create table t1(i int);
insert into t1 values(1);
insert into t1 values(2);
insert into t1 values(3);
insert into t1 values(4);
insert into t1 values(5);
insert into t1 values(6);
insert into t1 values(7);
insert into t1 values(8);
insert into t1 values(9);
insert into t1 values(0);
select * from t1;
drop table t1;
'''
Previously the API would accept multiple queries, as long as no multiple SELECTs where executed with different column type and count. The results returned by fetchall() would give the latest result of a SELECT.
This behavior has changed, that you can do as many weird queries as you want in one execute() statement. fetchall() returns the results of the lasts query, which in this case is "DROP table t1", which should return nothing.
I think the test is a valid test again by removing the "DROP TABLE t1" statement, since this is done in a uncommited transaction anyway.
## Comment 18619
Date: 2013-03-15 09:30:07 +0100
From: @drstmane
Changeset [1c06075da019](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1c06075da019) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1c06075da019](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1c06075da019)
Changeset description:
crash_on_concurrent_use.SF-1411926: updated test according to recent Python API changes:
From bug #3254:
"
Previously the API would accept multiple queries, as long as no multiple
SELECTs where executed with different column type and count. The results
returned by fetchall() would give the latest result of a SELECT.
This behavior has changed, that you can do as many weird queries as you want in
one execute() statement. fetchall() returns the results of the lasts query,
which in this case is "DROP table t1", which should return nothing.
I think the test is a valid test again by removing the "DROP TABLE t1"
statement, since this is done in a uncommited transaction anyway.
"
## Comment 18620
Date: 2013-03-15 09:31:01 +0100
From: @drstmane
Gijs,
thanks for the analysis and explanation!
I updated the test accordingly.
Stefan
| test sql/test/concurrent/Tests/crash_on_concurrent_use.SF-1411926.SQL.py fails after recent checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/3254/comments | 0 | 2020-11-30T12:29:59Z | 2024-06-27T11:59:19Z | https://github.com/MonetDB/MonetDB/issues/3254 | 753,438,849 | 3,254 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-12 11:10:24 +0100
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @mlkersten, @njnes
Last updated: 2013-03-22 13:39:42 +0100
## Comment 18612
Date: 2013-03-12 11:10:24 +0100
From: @drstmane
cf.
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=47169:7d1c376e995f&target=GNU-Fedora-x86_64-propcheck-assert&module=sql&test=sql%2Ftest%2FDump%2Freload&which=err
possibly because the new querylog related tables are not properly administred/marked as system tables?
## Comment 18636
Date: 2013-03-21 20:36:15 +0100
From: @njnes
we removed the extra schema, which solved this issue.
## Comment 18644
Date: 2013-03-22 13:39:42 +0100
From: @sjoerdmullender
This was not a bug in a released version.
| Test sql/test/Dump/Tests/reload.SQL.py fails after recent checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/3253/comments | 0 | 2020-11-30T12:29:56Z | 2024-06-27T11:59:18Z | https://github.com/MonetDB/MonetDB/issues/3253 | 753,438,814 | 3,253 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-12 01:44:24 +0100
From: Masood Mortazavi <<masoodmortazavi>>
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: masoodmortazavi, @njnes
Last updated: 2013-03-21 21:22:45 +0100
## Comment 18604
Date: 2013-03-12 01:44:24 +0100
From: Masood Mortazavi <<masoodmortazavi>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
11.16.0 / development/unreleased branch, probably @ changeset: 47036:a6120285222e
MAL code generated for simple selects on VIEWs does not work in the mal interpreter while the MAL generated for the base tables on which VIEWs are built seems to work fine.
$ mserver5 --version
MonetDB 5 server v11.16.0 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.30 2012-02-04 (compiled with 8.30)
openssl: OpenSSL 1.0.1c 10 May 2012 (compiled with OpenSSL 1.0.1c 10 May 2012)
libxml2: 2.8.0 (compiled with 2.8.0)
Compiled by: root@masood-ThinkCentre-M91p (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64
Reproducible: Always
### Steps to Reproduce:
1. Create database described
2. Load data
3. Generate MAL using Explain in the SQL interpreter for "select *" queries on either tables or views
4. Try to run these generated MAL code in the interpreter, and observe that while the MAL generated for the base tables (i.e. parents1/2, teachers, students1/2) work, the MAL for parents (a view) doesn't.
START TRANSACTION;
CREATE TABLE Students1 (id INT NOT NULL, name VARCHAR(64) NOT NULL, parent_id INT NOT NULL, teacher_id INT NOT NULL) ;
CREATE TABLE Students2 (id INT NOT NULL, name VARCHAR(64) NOT NULL, parent_id INT NOT NULL, teacher_id INT NOT NULL) ;
CREATE TABLE Parents1 (id INT NOT NULL, name VARCHAR(64) NOT NULL) ;
CREATE TABLE Parents2 (id INT NOT NULL, name VARCHAR(64) NOT NULL) ;
CREATE TABLE Teachers (id INT NOT NULL, name VARCHAR(64) NOT NULL) ;
create view Students as
(select * from Students1
union all
select * from Students2);
create view Parents as
(select * from Parents1
union all
select * from Parents2);
COMMIT;
========================
$ cat parents1.txt
10|Gillian|
1|Moore|
2|Thompson|
9|Lee|
========================
$ cat parents2.txt
5|Gore|
7|McIntyre|
8|Lee|
======================== Working MAL
$ cat simple-select-from-parents1.txt
function user.s1_1{autoCommit=true}():void;
X_15 := nil:bat[:oid,:int];
X_22 := nil:bat[:oid,:str];
barrier X_42 := language.dataflow();
X_2 := sql.mvc();
X_3:bat[:oid,:oid] := sql.tid(X_2,"TS","parents1");
X_6 := sql.bind(X_2,"TS","parents1","id",0);
(X_9,r1_9) := sql.bind(X_2,"TS","parents1","id",2);
X_12 := sql.bind(X_2,"TS","parents1","id",1);
X_14 := sql.delta(X_6,X_9,r1_9,X_12);
X_15 := algebra.leftfetchjoin(X_3,X_14);
X_16 := sql.bind(X_2,"TS","parents1","name",0);
(X_18,r1_22) := sql.bind(X_2,"TS","parents1","name",2);
X_20 := sql.bind(X_2,"TS","parents1","name",1);
X_21 := sql.delta(X_16,X_18,r1_22,X_20);
X_22 := algebra.leftfetchjoin(X_3,X_21);
language.pass(X_3);
exit X_42;
X_23 := sql.resultSet(2,1,X_15);
sql.rsColumn(X_23,"TS.parents1","id","int",32,0,X_15);
sql.rsColumn(X_23,"TS.parents1","name","varchar",64,0,X_22);
X_31 := io.stdout();
sql.exportResult(X_31,X_23);
end s1_1;
========= Non-working MAL generated by EXPLAIN select * from parents;
$ cat simple-select-from-parents.txt
function user.s3_1{autoCommit=true}():void;
X_28 := nil:bat[:oid,:int];
X_53 := nil:bat[:oid,:str];
barrier X_80 := language.dataflow();
X_3:bat[:oid,:int] := bat.new(nil:oid,nil:int);
X_2 := sql.mvc();
X_6:bat[:oid,:oid] := sql.tid(X_2,"TS","parents1");
X_9 := sql.bind(X_2,"TS","parents1","id",0);
(X_12,r1_12) := sql.bind(X_2,"TS","parents1","id",2);
X_15 := sql.bind(X_2,"TS","parents1","id",1);
X_17 := sql.delta(X_9,X_12,r1_12,X_15);
X_18 := algebra.leftfetchjoin(X_6,X_17);
X_19 := bat.append(X_3,X_18,true);
X_20:bat[:oid,:oid] := sql.tid(X_2,"TS","parents2");
X_22 := sql.bind(X_2,"TS","parents2","id",0);
(X_23,r1_28) := sql.bind(X_2,"TS","parents2","id",2);
X_25 := sql.bind(X_2,"TS","parents2","id",1);
X_26 := sql.delta(X_22,X_23,r1_28,X_25);
X_27 := algebra.leftfetchjoin(X_20,X_26);
X_28 := bat.append(X_19,X_27,true);
X_30:bat[:oid,:str] := bat.new(nil:oid,nil:str);
X_33 := sql.bind(X_2,"TS","parents1","name",0);
(X_38,r1_52) := sql.bind(X_2,"TS","parents1","name",2);
X_41 := sql.bind(X_2,"TS","parents1","name",1);
X_43 := sql.delta(X_33,X_38,r1_52,X_41);
X_44 := algebra.leftfetchjoin(X_6,X_43);
X_45 := bat.append(X_30,X_44,true);
X_46 := sql.bind(X_2,"TS","parents2","name",0);
(X_48,r1_67) := sql.bind(X_2,"TS","parents2","name",2);
X_50 := sql.bind(X_2,"TS","parents2","name",1);
X_51 := sql.delta(X_46,X_48,r1_67,X_50);
X_52 := algebra.leftfetchjoin(X_20,X_51);
X_53 := bat.append(X_45,X_52,true);
language.pass(X_6);
language.pass(X_20);
exit X_80;
X_55 := sql.resultSet(2,1,X_28);
sql.rsColumn(X_55,".parents","id","int",32,0,X_28);
sql.rsColumn(X_55,".parents","name","varchar",64,0,X_53);
X_66 := io.stdout();
sql.exportResult(X_66,X_55);
end s3_1;
## Comment 18605
Date: 2013-03-12 01:52:34 +0100
From: Masood Mortazavi <<masoodmortazavi>>
Created attachment 186
DD for the test case
> Attached file: [TS-shell.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3252_TS-shell.sql_186) (text/x-sql, 647 bytes)
> Description: DD for the test case
## Comment 18606
Date: 2013-03-12 01:53:34 +0100
From: Masood Mortazavi <<masoodmortazavi>>
Created attachment 187
What appears to be faulty MAL generated by explain (for a VIEW)
> Attached file: [simple-select-from-parents.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3252_simple-select-from-parents.txt_187) (text/plain, 2773 bytes)
> Description: What appears to be faulty MAL generated by explain (for a VIEW)
## Comment 18607
Date: 2013-03-12 01:54:21 +0100
From: Masood Mortazavi <<masoodmortazavi>>
Created attachment 188
What appears to be working MAL for a base table
> Attached file: [simple-select-from-parents1.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3252_simple-select-from-parents1.txt_188) (text/plain, 1608 bytes)
> Description: What appears to be working MAL for a base table
## Comment 18608
Date: 2013-03-12 01:54:48 +0100
From: Masood Mortazavi <<masoodmortazavi>>
Created attachment 189
Datafile for one base table
> Attached file: [parents1.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3252_parents1.txt_189) (text/plain, 40 bytes)
> Description: Datafile for one base table
## Comment 18609
Date: 2013-03-12 01:55:15 +0100
From: Masood Mortazavi <<masoodmortazavi>>
Created attachment 190
Datafile for another base table
> Attached file: [parents2.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3252_parents2.txt_190) (text/plain, 27 bytes)
> Description: Datafile for another base table
## Comment 18633
Date: 2013-03-21 20:11:39 +0100
From: @njnes
Could you also include the error? Generated mal (explain output) requires a
sql context.
## Comment 18637
Date: 2013-03-21 21:04:01 +0100
From: Masood Mortazavi <<masoodmortazavi>>
When running the attached (non-working) mal on the "parents" view, I get the following error returned by the mclient:
ERROR = !TypeException:user.s3_1[12]:'bat.append' undefined in: X_19:any := bat.append(X_3:bat[:oid,:int], X_18:bat[:oid,:any], _1:bit)
!TypeException:user.s3_1[19]:'bat.append' undefined in: X_28:bat[:oid,:int] := bat.append(X_19:any, X_27:bat[:oid,:any], _1:bit)
!TypeException:user.s3_1[26]:'bat.append' undefined in: X_45:any := bat.append(X_30:bat[:oid,:str], X_44:bat[:oid,:any], _43:bit)
!TypeException:user.s3_1[32]:'bat.append' undefined in: X_53:bat[:oid,:str] := bat.append(X_45:any, X_52:bat[:oid,:any], _43:bit)
mal>
after it ingests the mal from the file and prints it out exactly as in the attached.
If you need further information, please do let me know.
## Comment 18638
Date: 2013-03-21 21:22:45 +0100
From: @njnes
MAL is a fully type language. The explain output however leaves out some of the type specifics. The working example the output type of the leftfetchjoin is known
while in the non working this isn't the case. We however do not support using the output of explain directly as mal input, its there just for debugging.
| EXPLAIN doesn't seem to generate valid MAL program for VIEWs | https://api.github.com/repos/MonetDB/MonetDB/issues/3252/comments | 0 | 2020-11-30T12:29:53Z | 2024-06-28T07:23:19Z | https://github.com/MonetDB/MonetDB/issues/3252 | 753,438,780 | 3,252 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-11 00:32:30 +0100
From: Pete Hollobon <<pete>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.3 (Feb2013-SP1)
CC: @mlkersten, pete, @drstmane
Last updated: 2013-04-29 14:51:29 +0200
## Comment 18602
Date: 2013-03-11 00:32:30 +0100
From: Pete Hollobon <<pete>>
The name of the coercions optimizer is wrong in opt_wrapper.c, so it's never used, despite being in several of the optimizer pipelines.
Here's patch
--- a/monetdb5/optimizer/opt_wrapper.c
+++ b/monetdb5/optimizer/opt_wrapper.c
@@ -84,7 +84,7 @@
{"aliases", &OPTaliasesImplementation},
{"centipede", &OPTcentipedeImplementation},
{"cluster", &OPTclusterImplementation},
- {"coercion", &OPTcoercionImplementation},
+ {"coercions", &OPTcoercionImplementation},
{"commonTerms", &OPTcommonTermsImplementation},
{"compression", &OPTcompressionImplementation},
{"costModel", &OPTcostModelImplementation},
## Comment 18610
Date: 2013-03-12 03:17:49 +0100
From: @drstmane
Changeset [30c2d470a73d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30c2d470a73d) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the
MonetDB repo, refers to this bug.
For complete details, see
[http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30c2d470a73d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30c2d470a73d)
Changeset description:
opt_support.c & opt_wrapper.c: "coercion" -> "coercions",
i.e., using the correct optimizer name "coercions"
to ensure the optimizer is indeed activated/used.
Approved related changes in test output (modified MAL plans
due to now active coercions optimizer).
This should fix bug #3251.
Thanks to Pete Hollobon for reporting and proving the initial fix!
Open question:
Why is an incorrect / non-exiting optimizer name silently ignored??
## Comment 18625
Date: 2013-03-18 08:28:15 +0100
From: @mlkersten
Exception is thrown when the optimizer does not exist.
| Name of coercions optimizer wrong in opt_wrapper.c | https://api.github.com/repos/MonetDB/MonetDB/issues/3251/comments | 0 | 2020-11-30T12:29:51Z | 2024-06-27T11:59:16Z | https://github.com/MonetDB/MonetDB/issues/3251 | 753,438,747 | 3,251 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-09 15:01:24 +0100
From: Christian Braun <<hcb>>
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: hcb, @njnes
Last updated: 2013-07-31 12:49:40 +0200
## Comment 18601
Date: 2013-03-09 15:01:24 +0100
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
Welcome to mclient, the MonetDB/SQL interactive terminal (Feb2013-SP1)
Database: MonetDB v11.15.3 (Feb2013-SP1), 'mapi:monetdb://etna:50000/broken2'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select * from mytest;
+------+------+------+
| id | n | flag |
+======+======+======+
| 1 | 1 | null |
| 2 | 1 | null |
| 3 | 1 | null |
| 4 | 2 | null |
| 5 | 1 | 42 |
| 6 | 1 | 42 |
+------+------+------+
6 tuples (0.622ms)
sql>select id, n, flag, (select count(*) from mytest as i where i.id < mytest.id and i.n = mytest.n) from mytest order by id;
+------+------+------+------+
| id | n | flag | L2 |
+======+======+======+======+
| 1 | 1 | null | 0 |
| 2 | 1 | null | 1 |
| 3 | 1 | null | 2 |
| 4 | 2 | null | 0 |
| 5 | 1 | 42 | 3 |
| 6 | 1 | 42 | 4 |
+------+------+------+------+
6 tuples (1.952ms)
sql>select id, n, flag, (select count(*) from mytest as i where i.id < mytest.id and i.n = mytest.n and flag is not null) from mytest order by id;
SELECT: subquery result missing
sql>
Reproducible: Always
## Comment 18639
Date: 2013-03-21 22:54:29 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [8e3776585f91](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8e3776585f91) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8e3776585f91](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8e3776585f91)
Changeset description:
fixed bug #3250 (handle join and select expressions in the correlated subquery)
## Comment 18640
Date: 2013-03-21 22:55:07 +0100
From: @njnes
fixed, handle both join and select expressions in correlated subqueries
## Comment 18961
Date: 2013-07-31 12:49:40 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bb7bf53eaf84](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bb7bf53eaf84) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bb7bf53eaf84](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bb7bf53eaf84)
Changeset description:
fixed bug #3250, handle correlation using apply operator
| SELECT fails with subquery result missing when adding condition | https://api.github.com/repos/MonetDB/MonetDB/issues/3250/comments | 0 | 2020-11-30T12:18:04Z | 2024-06-27T11:59:15Z | https://github.com/MonetDB/MonetDB/issues/3250 | 753,430,776 | 3,250 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-08 17:17:23 +0100
From: Percy Wegmann <<percy>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-07-03 13:56:40 +0200
## Comment 18600
Date: 2013-03-08 17:17:23 +0100
From: Percy Wegmann <<percy>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.155 Safari/537.22
Build Identifier:
Using an OFFSET clause in an INSERT INTO ... SELECT * FROM ... query leaves the destination table in an inconsistent state. Querying that table with an OFFSET returns a result that indicates we got rows, but no rows are actually returned.
Note - this problem is only reproduceable once the source table reaches a certain size. I haven't figured out what size that is, but when I tried it with really small tables it was fine.
Reproducible: Always
### Steps to Reproduce:
Transcript from mclient session (with comments inline)
sql>CREATE TABLE TA(CA VARCHAR(9999999), CB VARCHAR(9999999));
operation successful (26.946ms)
sql>CREATE TABLE TB(CA VARCHAR(9999999), CB VARCHAR(9999999));
operation successful (25.819ms)
sql>INSERT INTO TA VALUES('A', 'B');
1 affected row (9.548ms)
sql>INSERT INTO TA SELECT * FROM TA;
1 affected row (13.130ms)
sql>INSERT INTO TA SELECT * FROM TA;
2 affected rows (5.538ms)
... and so on to load up TA
sql>SELECT COUNT(*) FROM TA;
+----------+
| L1 |
+==========+
| 16777216 |
+----------+
1 tuple (1.608ms)
sql>INSERT INTO TB SELECT * FROM TA OFFSET 8000000;
16777216 affected rows (2.7s)
-- Here is the first hint that something is wrong -- I should have gotten 8777216 affected rows, but shell reported 16777216 rows
sql>SELECT * FROM TB LIMIT 2 OFFSET 8000000;
+------+------+
| ca | cb |
+======+======+
+------+------+
2 tuples (682.929ms)
-- Hmm, it says there are 2 tuples, but it doesn't show any ...
sql>DROP TABLE TB;
operation successful (26.977ms)
sql>CREATE TABLE TB(CA VARCHAR(9999999), CB VARCHAR(9999999));
operation successful (69.594ms)
sql>INSERT INTO TB SELECT * FROM TA LIMIT 8777216;
8777216 affected rows (2.0s)
-- LIMIT seems to work fine though
sql>SELECT * FROM TB LIMIT 2 OFFSET 8000000;
+------+------+
| ca | cb |
+======+======+
| A | B |
| A | B |
+------+------+
2 tuples (651.026ms)
-- Yes, LIMIT works
-- Does it work if I use a bind parameter for OFFSET?
sql>DROP TABLE TB;
operation successful (43.317ms)
sql>CREATE TABLE TB(CA VARCHAR(9999999), CB VARCHAR(9999999));
operation successful (93.950ms)
sql>PREPARE INSERT INTO TB SELECT * FROM TA OFFSET ?;
execute prepared statement using: EXEC 14(...)
+------+--------+-------+--------+-------+--------+
| type | digits | scale | schema | table | column |
+======+========+=======+========+=======+========+
| wrd | 64 | 0 | null | null | null |
+------+--------+-------+--------+-------+--------+
1 tuple (1.673ms)
sql>EXEC 14(8000000);
16777216 affected rows (2.7s)
sql>SELECT * FROM TB LIMIT 2 OFFSET 8000000;
+------+------+
| ca | cb |
+======+======+
+------+------+
2 tuples (669.347ms)
-- No, it doesn't work with bind parameters either
sql>
### Actual Results:
The table created by using this query is missing data and seems to be in a strange state:
INSERT INTO TB SELECT * FROM TA OFFSET 8000000;
The table created with this query is fine though:
INSERT INTO TB SELECT * FROM TA LIMIT 8777216;
### Expected Results:
Both OFFSET and LIMIT should work
If the OFFSET clause isn't supportable in an INSERT query, a minimum step would be to remove support for it from the parser.
## Comment 18902
Date: 2013-07-03 13:56:40 +0200
From: @njnes
Could you test the current version
| INSERT INTO ... SELECT * FROM ... OFFSET X seems to leave destination table in an inconsistent state | https://api.github.com/repos/MonetDB/MonetDB/issues/3249/comments | 0 | 2020-11-30T12:18:01Z | 2024-06-27T11:59:14Z | https://github.com/MonetDB/MonetDB/issues/3249 | 753,430,739 | 3,249 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-08 09:56:19 +0100
From: first.li
To: clients devs <<bugs-clients>>
Version: 11.15.19 (Feb2013-SP6)
CC: @hannesmuehleisen
Last updated: 2014-02-04 13:00:47 +0100
## Comment 18599
Date: 2013-03-08 09:56:19 +0100
From: first.li
User-Agent: Mozilla/5.0 (Compatible win32 67.119.6.164; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Build Identifier:
When DBVisualizer connected to server by JDBC, server stoped immediately.
Reproducible: Always
## Comment 19020
Date: 2013-08-18 14:09:57 +0200
From: @hannesmuehleisen
Created attachment 220
Screenshot of DbVisualizer
> Attached file: [Screen Shot 2013-08-18 at 14.08.03.png](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3248_Screen_Shot_2013-08-18_at_14.08.03.png_220) (image/png, 481367 bytes)
> Description: Screenshot of DbVisualizer
## Comment 19021
Date: 2013-08-18 14:11:10 +0200
From: @hannesmuehleisen
Could not reproduce issue here (see http://bugs.monetdb.org/attachment.cgi?id=220). Please provide more details on your environment, operating system, database version, JDBC driver version, DbVisualizer version etc.
## Comment 19522
Date: 2014-02-04 13:00:47 +0100
From: @sjoerdmullender
Please provide details.
| When DBVisualizar connect server by JDBC, server stoped immediately | https://api.github.com/repos/MonetDB/MonetDB/issues/3248/comments | 0 | 2020-11-30T12:17:59Z | 2024-06-27T11:59:13Z | https://github.com/MonetDB/MonetDB/issues/3248 | 753,430,712 | 3,248 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-08 04:46:55 +0100
From: first.li
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes, @drstmane
Last updated: 2013-05-14 16:56:31 +0200
## Comment 18595
Date: 2013-03-08 04:46:55 +0100
From: first.li
User-Agent: Mozilla/5.0 (Compatible win32 67.119.6.164; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Build Identifier:
I execute the sql:"select substring(code,1,4) as code1,sum(open) from test group by code1",get the error:"b and g must be aligned".
Reproducible: Always
## Comment 18623
Date: 2013-03-16 11:03:42 +0100
From: @njnes
For the example to be executed we need also the DDL statements, ie create table test etc. Possibly some example data.
## Comment 18661
Date: 2013-03-31 17:39:26 +0200
From: first.li
DDL:
CREATE TABLE TEST(Date date,Open double,High double,Low double,Close double,Volume double,Adj_Close double,Code VARCHAR(255));
example data:
2010-12-31,7.78,7.88,7.67,7.83,22468900,7.83,600811
2010-12-30,7.57,7.95,7.50,7.82,37663200,7.82,600811
2010-12-29,7.40,7.60,7.31,7.59,22047800,7.59,600811
2010-12-28,7.61,7.70,7.34,7.37,23575900,7.37,600811
## Comment 18662
Date: 2013-03-31 18:02:30 +0200
From: @drstmane
Works fine with me (post-Feb2013-SP1 Feb2013 branch, changeset 1218c4cf758f):
sql>CREATE TABLE TEST(Date date,Open double,High double,Low double,Close double,Volume double,Adj_Close double,Code VARCHAR(255));
operation successful (1.474ms)
sql>copy 4 records into test from stdin delimiters ',','\n';
more>2010-12-31,7.78,7.88,7.67,7.83,22468900,7.83,600811
more>2010-12-30,7.57,7.95,7.50,7.82,37663200,7.82,600811
more>2010-12-29,7.40,7.60,7.31,7.59,22047800,7.59,600811
more>2010-12-28,7.61,7.70,7.34,7.37,23575900,7.37,600811
more>
4 affected rows (11.277ms)
sql>select * from test;
+------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------+
| date | open | high | low | close | volume | adj_close | code |
+============+==========================+==========================+==========================+==========================+==========================+==========================+========+
| 2010-12-31 | 7.7800000000000002 | 7.8799999999999999 | 7.6699999999999999 | 7.8300000000000001 | 22468900 | 7.8300000000000001 | 600811 |
| 2010-12-30 | 7.5700000000000003 | 7.9500000000000002 | 7.5 | 7.8200000000000003 | 37663200 | 7.8200000000000003 | 600811 |
| 2010-12-29 | 7.4000000000000004 | 7.5999999999999996 | 7.3099999999999996 | 7.5899999999999999 | 22047800 | 7.5899999999999999 | 600811 |
| 2010-12-28 | 7.6100000000000003 | 7.7000000000000002 | 7.3399999999999999 | 7.3700000000000001 | 23575900 | 7.3700000000000001 | 600811 |
+------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------+
4 tuples (1.776ms)
sql>select substring(code,1,4) as code1,sum(open) from test group by code1;
+-------+--------------------------+
| code1 | L1 |
+=======+==========================+
| 6008 | 30.359999999999999 |
+-------+--------------------------+
1 tuple (1.661ms)
## Comment 18731
Date: 2013-05-14 16:56:31 +0200
From: @sjoerdmullender
Also works for me on a fresh install of Feb2013-SP1.
Please reopen if you have more information about how to reproduce the problem.
| sql error: b and g must be aligned | https://api.github.com/repos/MonetDB/MonetDB/issues/3247/comments | 0 | 2020-11-30T12:17:56Z | 2024-06-28T07:23:19Z | https://github.com/MonetDB/MonetDB/issues/3247 | 753,430,689 | 3,247 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-08 02:15:29 +0100
From: first.li
To: SQL devs <<bugs-sql>>
Version: 11.15.3 (Feb2013-SP1)
CC: @njnes
Last updated: 2013-03-21 20:06:19 +0100
## Comment 18594
Date: 2013-03-08 02:15:29 +0100
From: first.li
User-Agent: Mozilla/5.0 (Compatible win32 67.119.6.164; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Build Identifier:
I execute the sql:select * from test where code like '60%',but get the result "program contains errors".
the details:
TypeException:user.s2_1[12]:'pcre.like_filter' undefined in: _22:any := pcre.lik
e_filter(_16:bat[:oid,:str], _19:str, _20:str, _23:bit)
TypeException:user.s2_1[20]:'algebra.leftfetchjoin' undefined in: _33:any := alg
ebra.leftfetchjoin(_22:any, _30:bat[:oid,:date])
TypeException:user.s2_1[30]:'algebra.leftfetchjoin' undefined in: _47:any := alg
ebra.leftfetchjoin(_22:any, _44:bat[:oid,:dbl])
TypeException:user.s2_1[40]:'algebra.leftfetchjoin' undefined in: _62:any := alg
ebra.leftfetchjoin(_22:any, _59:bat[:oid,:dbl])
TypeException:user.s2_1[50]:'algebra.leftfetchjoin' undefined in: _74:any := alg
ebra.leftfetchjoin(_22:any, _71:bat[:oid,:dbl])
TypeException:user.s2_1[60]:'algebra.leftfetchjoin' undefined in: _88:any := alg
ebra.leftfetchjoin(_22:any, _85:bat[:oid,:dbl])
TypeException:user.s2_1[70]:'algebra.leftfetchjoin' undefined in: _103:any := al
gebra.leftfetchjoin(_22:any, _100:bat[:oid,:dbl])
TypeException:user.s2_1[80]:'algebra.leftfetchjoin' undefined in: _117:any := al
gebra.leftfetchjoin(_22:any, _114:bat[:oid,:dbl])
TypeException:user.s2_1[83]:'algebra.leftfetchjoin' undefined in: _120:any := al
gebra.leftfetchjoin(_22:any, _16:bat[:oid,:str])
Reproducible: Always
## Comment 18598
Date: 2013-03-08 09:24:22 +0100
From: @sjoerdmullender
What version of mserser5 are you running (on Windows, open a cmd shell and run the command
"C:\Program Files\MonetDB\MonetDB5\M5server.bat" --version
on other systems, run
mserver5 --version
and paste the output here)?
What is the upgrade history of the database that is failing? In other words, with which version of MonetDB was it created, and which versions have you used on it since?
## Comment 18632
Date: 2013-03-21 20:06:19 +0100
From: @njnes
We are unable to reproduce your problem.
| sql error: like contain '%' not support | https://api.github.com/repos/MonetDB/MonetDB/issues/3246/comments | 0 | 2020-11-30T12:17:53Z | 2024-06-28T07:23:18Z | https://github.com/MonetDB/MonetDB/issues/3246 | 753,430,668 | 3,246 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-03-06 19:52:53 +0100
From: b0b0b0b
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: @njnes
Last updated: 2013-04-29 14:51:28 +0200
## Comment 18584
Date: 2013-03-06 19:52:53 +0100
From: b0b0b0b
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.33 (KHTML, like Gecko) Chrome/27.0.1430.0 Safari/537.33
Build Identifier:
TypeException:user.s1_1[63]:'algebra.subselect' undefined in: _111:any := algebra.subselect(_107:bat[:oid,:oid], _110:bit, _110:bit, _93:bit, _93:bit, _94:bit)
TypeException:user.s1_1[64]:'algebra.crossproduct' undefined in: (_112:any, r1_112:any) := algebra.crossproduct(_100:bat[:oid,:oid], _111:any)
TypeException:user.s1_1[72]:'algebra.leftfetchjoin' undefined in: _129:any := algebra.leftfetchjoin(_112:any, _125:bat[:oid,:str])
TypeException:user.s1_1[81]:'algebra.join' undefined in: (_141:any, r1_141:any) := algebra.join(_129:any, _137:bat[:oid,:str])
TypeException:user.s1_1[82]:'algebra.leftfetchjoin' undefined in: _143:any := algebra.leftfetchjoin(r1_141:any, _137:bat[:oid,:str])
TypeException:user.s1_1[93]:'algebra.join' undefined in: (_162:any, r1_162:any) := algebra.join(_143:any, _158:bat[:oid,:str])
TypeException:user.s1_1[101]:'algebra.leftfetchjoin' undefined in: _175:any := algebra.leftfetchjoin(_112:any, _171:bat[:oid,:str])
TypeException:user.s1_1[102]:'algebra.leftfetchjoin' undefined in: _176:any := algebra.leftfetchjoin(_141:any, _175:any)
TypeException:user.s1_1[105]:'algebra.leftfetchjoin' undefined in: _179:any := algebra.leftfetchjoin(_162:any, _176:any)
TypeException:user.s1_1[157]:'algebra.join' undefined in: (_261:any, r1_261:any) := algebra.join(_179:any, _258:bat[:oid,:str])
.
.
.
.
Reproducible: Always
### Steps to Reproduce:
create table tbl_a (id int primary key,
c_id int,
str1 varchar(128),
str2 varchar(128),
str3 varchar(128),
int1 int,
str4 varchar(128));
create table tbl_b (id int primary key,
int1 int);
create table tbl_c (id int primary key,
str1 varchar(128),
str2 varchar(128),
str3 varchar(128));
create table tbl_d (a_id int, str1 varchar(128));
create view view_a as
select a.*,b.int1 as bint1,d.str1 as dstr1
from tbl_a a
inner join tbl_b b on a.id=b.id
inner join tbl_d d on a.id=d.a_id;
create view view_b as
select view_a.*
from view_a
inner join tbl_c on view_a.c_id=tbl_c.id
where 1=1
and view_a.str1 = 'foo'
and view_a.str2 = 'bar'
and view_a.str3 = 'baz'
and tbl_c.str1 <> 'foobar'
and tbl_c.str2 = 'foobarbaz'
and tbl_c.str3 is null;
create view view_c as
select * from view_b
where 1=1
and view_b.int1 = 0;
create view view_d as
select * from view_c
where str4 < 'zzzzz';
select * from view_d order by id;
--failure here
### Actual Results:
some kind of query plan exception
### Expected Results:
no exception
This also fails on mac osx for me, where I've installed monetdb using homebrew (so the issue isn't my compiler or environment AFAICT).
## Comment 18585
Date: 2013-03-06 22:13:16 +0100
From: @sjoerdmullender
Changeset [765ddafed310](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=765ddafed310) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=765ddafed310](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=765ddafed310)
Changeset description:
Added test for bug #3245.
## Comment 18626
Date: 2013-03-20 15:55:17 +0100
From: @njnes
Changeset [59ae06013de6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=59ae06013de6) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=59ae06013de6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=59ae06013de6)
Changeset description:
approved output
fixed bug view-view, bug #3245
## Comment 18627
Date: 2013-03-20 17:01:25 +0100
From: @njnes
Changeset [fbe6baf096f2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fbe6baf096f2) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbe6baf096f2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbe6baf096f2)
Changeset description:
backported fix for bug #3245
## Comment 18629
Date: 2013-03-20 20:05:37 +0100
From: @njnes
fixed, the handling of 1=1 needed improvement after the move to subselect and friends
| SELECT from a view of a view | https://api.github.com/repos/MonetDB/MonetDB/issues/3245/comments | 0 | 2020-11-30T12:17:50Z | 2024-06-27T11:59:10Z | https://github.com/MonetDB/MonetDB/issues/3245 | 753,430,625 | 3,245 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-28 17:03:57 +0100
From: @hannesmuehleisen
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2013-02-28 17:03:57 +0100
## Comment 18582
Date: 2013-02-28 17:03:57 +0100
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.97 Safari/537.22
Build Identifier:
After installation, MonetDB starts serving a "demo" database. Contrary to mserver5's behaviour on linux, where the demo database contains actual data, the "demo" database on Windows installations is just an empty database with a dbfarm in the user's home directory. It can safely be assumed that many users will never create another database, but instead live their life using the "demo" database. Recommend to do the same thing other systems such as MySQL or PostgreSQL do, and rename the "demo" database to something more lasting, for example "default". This could then also be used to simplify connectivity from clients by assuming this value as default for the database name.
Reproducible: Always
### Steps to Reproduce:
1. Install MonetDB on Windows
2. Start MonetDB SQL Server from Start Menu
3. "demo" database is created and served
### Actual Results:
"demo" database is created and served by default
### Expected Results:
used a name that has a chance of being permanently used
There is no Bugzilla component for installers yet, this is where this enhancement request actually belongs.
| Rename default database "demo" | https://api.github.com/repos/MonetDB/MonetDB/issues/3244/comments | 0 | 2020-11-30T12:17:48Z | 2024-06-28T13:40:10Z | https://github.com/MonetDB/MonetDB/issues/3244 | 753,430,595 | 3,244 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-26 17:52:49 +0100
From: Percy Wegmann <<percy>>
To: GDK devs <<bugs-common>>
Version: 11.15.15 (Feb2013-SP4)
CC: ashishk, @njnes
Last updated: 2013-12-03 13:59:37 +0100
## Comment 18572
Date: 2013-02-26 17:52:49 +0100
From: Percy Wegmann <<percy>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.99 Safari/537.22
Build Identifier:
We periodically shut down our Monet database. Sometimes, after performing a shutdown, the database gets into a state where it fails to startup. This appears to be related to the data files, because if I take the same data files to a different machine, I can reproduce the issue on startup.
The shutdown that seems to cause the issue shows up in the log as follows:
2013-02-25 12:56:22 MSG merovingian[16884]: sending process 17528 (database 'click') the TERM signal
2013-02-25 12:56:22 MSG merovingian[16884]: database 'click' (17528) has exited with exit status 0
2013-02-25 12:56:22 MSG merovingian[16884]: database 'click' has shut down
2013-02-25 12:56:22 MSG control[16884]: (local): stopped database 'click'
This seems to indicate a clean shutdown.
At startup, we get a segmentation fault. We took a core dump and I've attached the backtrace from it. After the dataset gets corrupted, the failure happens in the exact same place every time.
We reran our scenario and did find a Valgrind error that may be related - that report is also attached.
Reproducible: Always
### Steps to Reproduce:
We have a specific dataset with which we're testing. Unfortunately, the data is confidential, so we can't share it here. The general characteristics of what we're doing are:
- Tables are loaded via a COPY INTO that is reading from files on /dev/shm (shared memory)
- Multiple tables are loaded concurrently in separate transactions
- Periodically, we automatically restart MonetDB by using "monetdb stop click" to shut it down and then reconnecting to let monetdbd start it again. We do this in order to bring down Monet's memory usage to within a configured limit. Our app specifically halts all other database activity during the shutdown/restart operation.
What we've found is that if we run with the same data set but don't do the restart, we can run well past the point of failure. If we let the system quiesce and then restart MonetDB manually, it comes back up fine, which seems to suggest it's not something specific to a particular datum that we're writing.
### Actual Results:
Data is corrupted and mserver5 enters a restart loop
### Expected Results:
Data is not corrupted and mserver5 starts successfully
## Comment 18573
Date: 2013-02-26 17:54:25 +0100
From: Percy Wegmann <<percy>>
Information about Core Dump
==================
The error is happening on line 1142 of gdk_atoms.c:
if (GDK_STRCMP(v, (str) (next + 1) + extralen) == 0) {
Examining the core dump revealed that (next + 1) + extralen is referring to an out of bounds address. Here's the backtrace:
0 0x00007faf58414829 in strPut (h=0x1e2d180, dst=0x7fff592cf8f8, v=0x314dac0 "SAD014H1") at gdk_atoms.c:1142
1 0x00007faf582dc935 in BATappend (b=0x1e2cf90, n=0x32dfdb0, force=1 '\001') at gdk_batop.c:578
2 0x00007faf584c301e in la_bat_updates (lg=0x2d9b030, la=0x2c3ef48) at gdk_logger.c:429
3 0x00007faf584c3cf9 in la_apply (lg=0x2d9b030, c=0x2c3ef48) at gdk_logger.c:645
4 0x00007faf584c3f26 in tr_commit (lg=0x2d9b030, tr=0x2e247d0) at gdk_logger.c:705
5 0x00007faf584c4533 in logger_readlog (lg=0x2d9b030,
filename=0x7fff592d1e80 "/opt/clicksecurity/data/_monetdb/click/sql_logs/sql/log.56") at gdk_logger.c:823
6 0x00007faf584c482a in logger_readlogs (lg=0x2d9b030, fp=0x2d9b160,
filename=0x7fff592d3f90 "/opt/clicksecurity/data/_monetdb/click/sql_logs/sql/log") at gdk_logger.c:896
7 0x00007faf584c6f3e in logger_new (debug=0, fn=0x7faf500adfa8 "sql", logdir=0x7faf50090a08 "sql_logs", dbname=0x1fa3da0 "click",
version=52001, prefuncp=0x7faf500746a1 <bl_preversion>, postfuncp=0x7faf500747ed <bl_postversion>) at gdk_logger.c:1420
8 0x00007faf584c704e in logger_create (debug=0, fn=0x7faf500adfa8 "sql", logdir=0x7faf50090a08 "sql_logs", dbname=0x1fa3da0 "click",
version=52001, prefuncp=0x7faf500746a1 <bl_preversion>, postfuncp=0x7faf500747ed <bl_postversion>) at gdk_logger.c:1446
9 0x00007faf50075b19 in bl_create (logdir=0x7faf50090a08 "sql_logs", dbname=0x1fa3da0 "click", cat_version=52001) at bat_logger.c:249
10 0x00007faf50060ce4 in store_init (debug=0, store=store_bat, logdir=0x7faf50090a08 "sql_logs", dbname=0x1fa3da0 "click", stk=0)
at store.c:1287
11 0x00007faf4ffe3d3c in mvc_init (dbname=0x1fa3da0 "click", debug=0, store=store_bat, stk=0) at sql_mvc.c:51
12 0x00007faf4ff66874 in SQLinit () at sql_scenario.c:230
13 0x00007faf4ff6651f in SQLprelude () at sql_scenario.c:159
14 0x00007faf58b3085d in malCommandCall (stk=0x2d36e80, pci=0x2ea5520) at mal_interpreter.c:137
15 0x00007faf58b331b5 in runMALsequence (cntxt=0x7faf5988c020, mb=0x1e04310, startpc=1, stoppc=0, stk=0x2d36e80, env=0x0, pcicaller=0x0)
at mal_interpreter.c:710
16 0x00007faf58b323c1 in runMAL (cntxt=0x7faf5988c020, mb=0x1e04310, startpc=1, mbcaller=0x0, env=0x0, pcicaller=0x0)
at mal_interpreter.c:454
17 0x00007faf58b60a08 in MALengine (c=0x7faf5988c020) at mal_session.c:619
18 0x00007faf58b5f21f in malBootstrap () at mal_session.c:64
19 0x00007faf58b1313b in mal_init () at mal.c:244
20 0x000000000040340e in main (argc=22, av=0x7fff592db568) at mserver5.c:582
## Comment 18574
Date: 2013-02-26 17:56:50 +0100
From: Percy Wegmann <<percy>>
Created attachment 185
Results of running mserver5 in Valgrind while feeding in test data
This shows the results of running mserver5 in Valgrind. Notice the below error in a call to MT_msync:
Address 0x1ee3334a is not stack'd, malloc'd or (recently) free'd
> Attached file: [valgrind.out.gz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3243_valgrind.out.gz_185) (application/x-gzip, 31129 bytes)
> Description: Results of running mserver5 in Valgrind while feeding in test data
## Comment 18575
Date: 2013-02-26 17:57:30 +0100
From: Percy Wegmann <<percy>>
We tried installing version 11.13.9 and running with that, but we got the same problem.
## Comment 18576
Date: 2013-02-26 18:33:50 +0100
From: @njnes
Could you test with the Feb2013-branch? Or the to be released Feb2013-sp1.
There have been related fixes recently.
## Comment 18577
Date: 2013-02-26 18:37:41 +0100
From: Percy Wegmann <<percy>>
Will do. Stay tuned.
## Comment 18578
Date: 2013-02-26 21:10:03 +0100
From: Percy Wegmann <<percy>>
I just cloned the Feb2013 branch from mercurial and still have the same problem. I have been able to replicate it using some non-confidential data. The monet data files are 126 MB zipped. I'm happy to share these if that'll help.
## Comment 18579
Date: 2013-02-26 21:15:53 +0100
From: @njnes
Did you see the problem again after reloading or did you upgrade the
db from the old test? In case of the first mail me the download details, such that I can continue to debug.
## Comment 18580
Date: 2013-02-26 21:24:49 +0100
From: Percy Wegmann <<percy>>
I installed the newer version of Monet, deleted the old database, recreated and ran my test data through. After a few restarts, I ended up with the crashing issue again.
I'll email you a link to the data.
Thanks
## Comment 18581
Date: 2013-02-27 08:19:24 +0100
From: @njnes
The reason for the crash is indeed coming from the loading phase. The data on
disk seems already corrupt. Could we some how test with the loading scripts?
## Comment 18996
Date: 2013-08-13 17:47:26 +0200
From: Ashish Kumar Singh <<ashishk>>
Similar issue was found by me also using latest released version of monet DB.
## Comment 19346
Date: 2013-11-19 20:56:54 +0100
From: @sjoerdmullender
Although we haven't been able to reproduce this, we feel that changesets [aa2e3065be7e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=aa2e3065be7e) [486f2ab17d12](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=486f2ab17d12) and [054b82fd68c2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=054b82fd68c2) may well have fixed these issues.
Our analysis was that the hash table that is used to do double elimination in the string heap (partial elmination when the heap grows large) was corrupted after strings were added to the heap, but the transaction in which this happened was rolled back.
A related issue has to do with string offsets that grow, causing a widening of the offset column. If the transaction in which this happens is rolled back, similar problems could occur.
Hopefully the aforementioned changesets fix these issues, so I'm closing this bug. Feel free to reopen when the issue was not resolved.
## Comment 19384
Date: 2013-12-03 13:59:37 +0100
From: @sjoerdmullender
Feb2013-SP6 has been released.
| Segmentation fault (possible data corruption) after clean shutdown | https://api.github.com/repos/MonetDB/MonetDB/issues/3243/comments | 0 | 2020-11-30T12:17:46Z | 2024-06-27T11:59:08Z | https://github.com/MonetDB/MonetDB/issues/3243 | 753,430,559 | 3,243 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-25 12:23:11 +0100
From: mdobryakov
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2013-02-25 16:22:40 +0100
## Comment 18555
Date: 2013-02-25 12:23:11 +0100
From: mdobryakov
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
Hi,
If I have a DB in crash state:
user@stat-0-0 ~ monetdb status
name state uptime health
test crashed 37%, 5h crash 2013-02-22 18:02:28
Which steps can I do for repair DB? I don't found it on your manual or web-site, but I think this information will be very useful for MonetDB users.
Thanks
Reproducible: Always
### Expected Results:
Manual or web-site should have a section which describe steps about how to repair MonetDB database.
## Comment 18567
Date: 2013-02-25 16:22:40 +0100
From: @sjoerdmullender
The server crashed for some reason. It would be interesting to know why, so please take a look at the log file that monetdbd maintains (usually called merovingian.log).
If you're not too unlucky, you may be able to recover by just starting the server again. We try to always leave the database in a consistent state.
| Steps for repair database | https://api.github.com/repos/MonetDB/MonetDB/issues/3242/comments | 0 | 2020-11-30T12:17:43Z | 2024-06-28T07:19:40Z | https://github.com/MonetDB/MonetDB/issues/3242 | 753,430,533 | 3,242 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-25 11:56:49 +0100
From: @swingbit
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.1 (Feb2013)
CC: @mlkersten, @drstmane
Last updated: 2013-03-07 12:41:20 +0100
## Comment 18553
Date: 2013-02-25 11:56:49 +0100
From: @swingbit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
Build Identifier:
The sql file in attachment, ran on an empty database, crashes with a SEGFAULT.
The debugger suggests the crash happens in optimizer.reduce().
Indeed, the same SQL dos not crash when simply removing optimizer.reduce() from the default_pipe.
gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fe983d4c700 (LWP 12246)]
0x00007fe98d2128ca in runMALsequence (cntxt=0x173c768, mb=0x7fe974075b50, startpc=1, stoppc=49, stk=0x7fe9741fe540, env=0x7fe97423f0e0, pcicaller=0x7fe974232d90)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:801
801 if (isaBatType(getArgType(mb, pci, i))) {
(gdb) bt
0 0x00007fe98d2128ca in runMALsequence (cntxt=0x173c768, mb=0x7fe974075b50, startpc=1, stoppc=49, stk=0x7fe9741fe540, env=0x7fe97423f0e0, pcicaller=0x7fe974232d90)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:801
1 0x00007fe98d2122b3 in runMALsequence (cntxt=0x173c768, mb=0x7fe974075fb0, startpc=1, stoppc=0, stk=0x7fe97423f0e0, env=0x0, pcicaller=0x0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:720
2 0x00007fe98d211335 in callMAL (cntxt=0x173c768, mb=0x7fe974075fb0, env=0x7fe983d4bba0, argv=0x7fe983d4bc20, debug=0 '\000') at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:469
3 0x00007fe984fc5f56 in SQLexecutePrepared (c=0x173c768, be=0x7fe974074910, q=0x7fe97408a370) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:1840
4 0x00007fe984fc6345 in SQLengineIntern (c=0x173c768, be=0x7fe974074910) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:1907
5 0x00007fe984fc68ba in SQLengine (c=0x173c768) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:2008
6 0x00007fe98d23ea95 in runPhase (c=0x173c768, phase=4) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:522
7 0x00007fe98d23ec82 in runScenarioBody (c=0x173c768) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:567
8 0x00007fe98d23edb4 in runScenario (c=0x173c768) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:586
9 0x00007fe98d23fe4a in MSserveClient (dummy=0x173c768) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_session.c:431
10 0x0000003599007761 in start_thread () from /lib64/libpthread.so.0
11 0x0000003598ce098d in clone () from /lib64/libc.so.6
(gdb) p *pci
$3 = {token = 54 '6', barrier = 0 '\000', typechk = 2 '\002', gc = 3 '\003', polymorphic = 0 '\000', varargs = 0 '\000', recycle = 0, jump = 0, fcn = 0x7fe98d49391c <OPTwrapper>, blk = 0x290b6e0, modname = 0x1d500a0 "optimizer",
fcnname = 0x290b540 "reduce", argc = 1, retc = 1, maxarg = 4, argv = 0x7fe9741f4c40}
Reproducible: Always
### Steps to Reproduce:
1.run the SQL in attachment on an empty database
2.
3.
### Actual Results:
SEGFAULT
MonetDB 5 server v11.15.2 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 35.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0d 8 Feb 2011 (compiled with OpenSSL 1.0.0d-fips 8 Feb 2011)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: roberto@spinque01.ins.cwi.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wmissing-include-dirs
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18554
Date: 2013-02-25 12:03:11 +0100
From: @swingbit
The file turns out to be too big to be stored as an attachment.
I made it available (for limited time) here:
~roberto/tmp/bug-3241.sql
## Comment 18558
Date: 2013-02-25 12:42:02 +0100
From: @drstmane
This seems to be a MAL interpreter / optimizer problem.
Here's a first gdb trace:
[...]
[ 2441, "start", "12:27:48.745072", 3, 0, "optimizer.reduce();", ]
[New Thread 0x7fffee7ff700 (LWP 10890)]
[New Thread 0x7fffee5fe700 (LWP 10891)]
[New Thread 0x7fffee3fd700 (LWP 10928)]
[New Thread 0x7fffee1fc700 (LWP 10929)]
[New Thread 0x7fffedffb700 (LWP 10930)]
[New Thread 0x7fffeddfa700 (LWP 10931)]
[New Thread 0x7fffedbf9700 (LWP 10932)]
[New Thread 0x7fffed9f8700 (LWP 10933)]
[New Thread 0x7fffed7f7700 (LWP 10934)]
[New Thread 0x7fffed5f6700 (LWP 10935)]
[New Thread 0x7fffed3f5700 (LWP 10936)]
[New Thread 0x7fffec9f4700 (LWP 10937)]
[New Thread 0x7fffec7f3700 (LWP 10938)]
[New Thread 0x7fffec5f2700 (LWP 10939)]
[Thread 0x7fffec5f2700 (LWP 10939) exited]
[Thread 0x7fffec7f3700 (LWP 10938) exited]
[Thread 0x7fffec9f4700 (LWP 10937) exited]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffee3fd700 (LWP 10928)]
0x00007ffff7a4cec2 in instruction2str (mb=0x7fffe00c7c60, stk=0x7fffe023db00, p=0x7fffe00c6440, flg=330) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_listing.c:316
316 if (p->argc > 0 && isTmpVar(mb, getArg(p, 0))) {
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-3.fc15.x86_64 cfitsio-3.280-2.fc16.x86_64 cyrus-sasl-lib-2.1.23-27.fc16.x86_64 geos-3.3.1-1.fc16.x86_64 glibc-2.14.90-24.fc16.9.x86_64 keyutils-libs-1.5.2-1.fc16.x86_64 krb5-libs-1.9.4-3.fc16.x86_64 libcom_err-1.41.14-2.fc15.x86_64 libcurl-7.21.7-8.fc16.x86_64 libgcc-4.6.3-2.fc16.x86_64 libidn-1.22-3.fc16.x86_64 libselinux-2.1.6-6.fc16.x86_64 libssh2-1.2.7-4.fc16.x86_64 libstdc++-4.6.3-2.fc16.x86_64 libuuid-2.20.1-2.3.fc16.x86_64 libxml2-2.7.8-8.fc16.x86_64 ncurses-libs-5.9-2.20110716.fc16.x86_64 nspr-4.9.4-1.fc16.x86_64 nss-3.14.1-3.fc16.x86_64 nss-softokn-freebl-3.14.1-3.fc16.x86_64 nss-util-3.14.1-1.fc16.x86_64 openldap-2.4.26-8.fc16.x86_64 openssl-1.0.0j-1.fc16.x86_64 pcre-8.12-9.fc16.x86_64 readline-6.2-2.fc16.x86_64 zlib-1.2.5-7.fc16.x86_64
(gdb) bt
0 0x00007ffff7a4cec2 in instruction2str (mb=0x7fffe00c7c60, stk=0x7fffe023db00, p=0x7fffe00c6440, flg=330) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_listing.c:316
1 0x00007ffff7a5dea7 in offlineProfilerEvent (idx=1, mb=0x7fffe00c7c60, stk=0x7fffe023db00, pc=48, start=0) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_profiler.c:450
2 0x00007ffff7a5bd41 in profilerEvent (idx=1, mb=0x7fffe00c7c60, stk=0x7fffe023db00, pc=48, start=0) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_profiler.c:218
3 0x00007ffff7a3b068 in runtimeProfileExit (cntxt=0x62d088, mb=0x7fffe00c7c60, stk=0x7fffe023db00, prof=0x7fffee3fc360) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_runtime.c:101
4 0x00007ffff7a45fb9 in runMALsequence (cntxt=0x62d088, mb=0x7fffe00c7c60, startpc=1, stoppc=49, stk=0x7fffe023db00, env=0x7fffe00eac80, pcicaller=0x7fffe00c8be0) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_interpreter.c:761
5 0x00007ffff7a45d29 in runMALsequence (cntxt=0x62d088, mb=0x7fffe014ef40, startpc=1, stoppc=0, stk=0x7fffe00eac80, env=0x0, pcicaller=0x0) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_interpreter.c:720
6 0x00007ffff7a44dd2 in callMAL (cntxt=0x62d088, mb=0x7fffe014ef40, env=0x7fffee3fcb78, argv=0x7fffee3fcc20, debug=0 '\000') at .../Feb2013/source/MonetDB/monetdb5/mal/mal_interpreter.c:469
7 0x00007fffef411eb3 in SQLexecutePrepared (c=0x62d088, be=0x7fffe002b470, q=0x7fffe00beea0) at .../Feb2013/source/MonetDB/sql/backends/monet5/sql_scenario.c:1840
8 0x00007fffef41229a in SQLengineIntern (c=0x62d088, be=0x7fffe002b470) at .../Feb2013/source/MonetDB/sql/backends/monet5/sql_scenario.c:1907
9 0x00007fffef4127fb in SQLengine (c=0x62d088) at .../Feb2013/source/MonetDB/sql/backends/monet5/sql_scenario.c:2008
10 0x00007ffff7a7334b in runPhase (c=0x62d088, phase=4) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:522
11 0x00007ffff7a73534 in runScenarioBody (c=0x62d088) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:566
12 0x00007ffff7a73657 in runScenario (c=0x62d088) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_scenario.c:586
13 0x00007ffff7a746d0 in MSserveClient (dummy=0x62d088) at .../Feb2013/source/MonetDB/monetdb5/mal/mal_session.c:431
14 0x0000003cf3c07d90 in start_thread () from /lib64/libpthread.so.0
15 0x0000003cf30f119d in clone () from /lib64/libc.so.6
(gdb) li
311 }
312 if (flg & LIST_MAL_LNR){
313 snprintf(t,len-1,"%3d ",getPC(mb,p));
314 advance(t,base,len);
315 }
316 if (p->argc > 0 && isTmpVar(mb, getArg(p, 0))) {
317 if (isVarUsed(mb, getDestVar(p))) {
318 snprintf(nmebuf, PATHLENGTH, "%c%d", TMPMARKER, getVarTmp(mb, getArg(p, 0)));
319 } else
320 nmebuf[0] = 0;
(gdb) p p
$1 = (InstrPtr) 0x7fffe00c6440
(gdb) p *p
$2 = {token = 54 '6', barrier = 0 '\000', typechk = 2 '\002', gc = 3 '\003', polymorphic = 0 '\000', varargs = 0 '\000', recycle = 0, jump = 0, fcn = 0x7ffff7ccefa0 <OPTwrapper>, blk = 0x17fc5c0, modname = 0xc3f040 "optimizer", fcnname = 0x17fc420 "reduce", argc = 1, retc = 1, maxarg = 4,
(gdb) p p->argc
$3 = 1
(gdb) p mb
$4 = (MalBlkPtr) 0x7fffe00c7c60
(gdb) p *mb
$5 = {binding = 0x0, help = 0x0, alternative = 0x0, vtop = 51, vsize = 64, var = 0x7fffe00e57a0, stop = 48, ssize = 81, stmt = 0x7fffe00eb600, ptop = 2, psize = 32, prps = 0x7fffe00d6100, errors = 0, typefixed = 0, flowfixed = 1, profiler = 0x7fffe0245bd0, history = 0x0, keephistory = 0,
dotfile = 0, marker = 0x0, maxarg = 8, replica = 0x0, recycle = 0, recid = 0, legid = -4774451407313060419, trap = 0, starttime = 34743987}
(gdb) p getArg(p, 0)
No symbol "getArg" in current context.
(gdb) p p->argv[0]
$6 = 51
(gdb) p isTmpVar(mb, 51)
No symbol "isTmpVar" in current context.
(gdb) p mb->var[51]->tmpindex
Cannot access memory at address 0x10
(gdb) p mb->var[51]
$7 = (VarRecord *) 0x0
(gdb) quit
## Comment 18559
Date: 2013-02-25 12:54:22 +0100
From: @sjoerdmullender
The crash happens after a call to optimizer.reduce(). The interpreter looks at the return value (which should be str), but it looks like the code doesn't fill in a return value.
Martin, what's the deal here?
## Comment 18560
Date: 2013-02-25 13:06:35 +0100
From: @mlkersten
The optimizer.reduce() is called by the optimizer wrapper, not directly from MAL unless it is part of a MAL test case. The wrapper returns the (exception) result from the program check.
## Comment 18561
Date: 2013-02-25 14:02:00 +0100
From: @mlkersten
Splitting the script into three phases shows that
you need the copy.sql part to trigger the error.
If you reduce the copy.sql to a single record,
it works without problems.
monetdb destroy bug -f; monetdb create bug; monetdb release bug; mclient -d bug create.sql ; mclient -d bug copy.sql ;mclient -d bug fcn.sql
## Comment 18562
Date: 2013-02-25 15:03:22 +0100
From: @sjoerdmullender
You only need 6 elements in the test table. 5 is not enough.
An execution trace is interesting. After each return gettype, the next optimizer.something() instruction is executed, until reduce hits and causes a crash.
Run mserver5 and execute
profiler.openStream("console");
profiler.setAll();
profiler.activate("event","time","thread","ticks","stmt","start");
profiler.start();
on the console before running the mclient.
## Comment 18564
Date: 2013-02-25 15:32:19 +0100
From: @sjoerdmullender
Changeset [335efc7b71a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=335efc7b71a1) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=335efc7b71a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=335efc7b71a1)
Changeset description:
Added test for bug #3241.
## Comment 18568
Date: 2013-02-26 11:16:57 +0100
From: @sjoerdmullender
Changeset [be7612616e15](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=be7612616e15) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=be7612616e15](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=be7612616e15)
Changeset description:
Off by one error. This fixes bug #3241.
Also approve test output that now works.
## Comment 18569
Date: 2013-02-26 14:16:55 +0100
From: @sjoerdmullender
If this wasn't fixed, please reopen.
## Comment 18587
Date: 2013-03-07 12:41:20 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| SEGFAULT on string processing when using optimizer.reduce() | https://api.github.com/repos/MonetDB/MonetDB/issues/3241/comments | 0 | 2020-11-30T12:17:40Z | 2024-06-27T11:59:06Z | https://github.com/MonetDB/MonetDB/issues/3241 | 753,430,493 | 3,241 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-25 11:49:49 +0100
From: mdobryakov
To: clients devs <<bugs-clients>>
Version: 11.15.1 (Feb2013)
Last updated: 2013-02-25 12:38:30 +0100
## Comment 18552
Date: 2013-02-25 11:49:49 +0100
From: mdobryakov
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20100101 Firefox/19.0
Build Identifier:
Hi,
I want to clarify the following:
MonetDB don't provide ability to cancel or abort queries. Is it true?
Is it mean, for example, what after closing/aborting JDBC connection to MonetDB the queries created in this session continue executing?
Thanks
P.S.
I want to describe why I want to clarify this. I have found the following code in JDBC driver:
/**
* Cancels this Statement object if both the DBMS and driver support
* aborting an SQL statement. This method can be used by one thread to
* cancel a statement that is being executed by another thread.
*
* @throws SQLException if a database access error occurs or the cancel
* operation is not supported
*/
public void cancel() throws SQLException {
throw new SQLException("Query cancelling is currently not supported by the DBMS.", "0A000");
}
So, I want to exactly understand this is restriction of JDBC driver or MonetDB?
Reproducible: Always
## Comment 18557
Date: 2013-02-25 12:38:30 +0100
From: @sjoerdmullender
(In reply to comment 0)
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0)
> Gecko/20100101 Firefox/19.0
> Build Identifier:
>
> Hi,
>
> I want to clarify the following:
>
> MonetDB don't provide ability to cancel or abort queries. Is it true?
>
> Is it mean, for example, what after closing/aborting JDBC connection to MonetDB
> the queries created in this session continue executing?
That is correct.
By the way, a question like this is more appropriate for the mailing list users-list@monetdb.org.
| Cancel/abort query | https://api.github.com/repos/MonetDB/MonetDB/issues/3240/comments | 0 | 2020-11-30T12:17:38Z | 2024-06-28T07:23:18Z | https://github.com/MonetDB/MonetDB/issues/3240 | 753,430,458 | 3,240 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-22 20:09:53 +0100
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.13.9 (Oct2012-SP3)
CC: ajdamico, @mlkersten
Last updated: 2013-02-22 22:00:27 +0100
## Comment 18547
Date: 2013-02-22 20:09:53 +0100
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
Hi, I am using a brand new mserver.exe instance of MonetDB5 on Windows. I am getting the error: "COMMIT: transaction is aborted because of concurency conflicts, will ROLLBACK instead" that I'm not sure I should? Shouldn't I be able to use the COPY command on two separate CSV files into two separate data tables at once? I don't think this behavior is correct, but maybe I'm wrong? :/
Reproducible: Always
### Steps to Reproduce:
The files you can use to re-create this error are:
http://downloads.cms.gov/BSAPUF/2008_BSA_PartD_Events_PUF_1.zip
http://downloads.cms.gov/BSAPUF/2008_BSA_PartD_Events_PUF_2.zip
I create an mserver.exe instance with:
MonetDB 5 server v11.13.9 "Oct2012-SP3"
Serving database 'bsapuf', using 8 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 7.860 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50003/
MonetDB/JAQL module loaded
MonetDB/SQL module loaded
Then I ran this command in the first mclient:
CREATE TABLE bsa1 (PDE_EVENT_ID VARCHAR(255), BENE_SEX_IDENT_CD DOUBLE PRECISION, BENE_AGE_CAT_CD DOUBLE PRECISION, PDE_DRUG_CD DOUBLE PRECISION, PDE_DRUG_STR_CD DOUBLE PRECISION, PDE_DRUG_STR_UNITS_CD DOUBLE PRECISION, PDE_DRUG_DOSE_CD DOUBLE PRECISION, PDE_DRUG_CLASS_CD DOUBLE PRECISION, PDE_DRUG_QTY_DIS DOUBLE PRECISION, PDE_DRUG_DAY_SPLY_CD DOUBLE PRECISION, PDE_DRUG_COST DOUBLE PRECISION, PDE_DRUG_PAT_PAY_CD DOUBLE PRECISION, PDE_DRUG_TYPE_CD DOUBLE PRECISION) ;
copy 1000000 offset 2 records into bsa1 from 'c:\\temp\\2008_BSA_PartD_Events_PUF_1.csv' using delimiters ',' NULL AS '' ;
And (at the same time) ran this command in the second mclient:
CREATE TABLE bsa2 (PDE_EVENT_ID VARCHAR(255), BENE_SEX_IDENT_CD DOUBLE PRECISION, BENE_AGE_CAT_CD DOUBLE PRECISION, PDE_DRUG_CD DOUBLE PRECISION, PDE_DRUG_STR_CD DOUBLE PRECISION, PDE_DRUG_STR_UNITS_CD DOUBLE PRECISION, PDE_DRUG_DOSE_CD DOUBLE PRECISION, PDE_DRUG_CLASS_CD DOUBLE PRECISION, PDE_DRUG_QTY_DIS DOUBLE PRECISION, PDE_DRUG_DAY_SPLY_CD DOUBLE PRECISION, PDE_DRUG_COST DOUBLE PRECISION, PDE_DRUG_PAT_PAY_CD DOUBLE PRECISION, PDE_DRUG_TYPE_CD DOUBLE PRECISION) ;
copy 1000000 offset 2 records into bsa2 from 'c:\\temp\\2008_BSA_PartD_Events_PUF_2.csv' using delimiters ',' NULL AS '' ;
Here were the results. One worked, one didn't:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\anthonyd.KFF>cd ..
C:\Users>cd ..
C:\>cd "Program Files\MonetDB\MonetDB5"
C:\Program Files\MonetDB\MonetDB5>mclient -p 50003 "bsapuf"
user(win32):monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012-SP3)
Database: MonetDB v11.13.9 (Oct2012-SP3), 'bsapuf'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>
sql>
sql>CREATE TABLE bsa2 (PDE_EVENT_ID VARCHAR(255), BENE_SEX_IDENT_CD DOUBLE PRECI
SION, BENE_AGE_CAT_CD DOUBLE PRECISION, PDE_DRUG_CD DOUBLE PRECISION, PDE_DRUG_S
TR_CD DOUBLE PRECISION, PDE_DRUG_STR_UNITS_CD DOUBLE PRECISION, PDE_DRUG_DOSE_CD
DOUBLE PRECISION, PDE_DRUG_CLASS_CD DOUBLE PRECISION, PDE_DRUG_QTY_DIS DOUBLE P
RECISION, PDE_DRUG_DAY_SPLY_CD DOUBLE PRECISION, PDE_DRUG_COST DOUBLE PRECISION,
PDE_DRUG_PAT_PAY_CD DOUBLE PRECISION, PDE_DRUG_TYPE_CD DOUBLE PRECISION) ;
operation successful (9.511ms)
sql>
sql>copy 1000000 offset 2 records into bsa2 from 'c:\\temp\\2008_BSA_PartD_Event
s_PUF_2.csv' using delimiters ',' NULL AS '' ;
1000000 affected rows (42.4s)
sql>
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\anthonyd.KFF>cd ..
C:\Users>cd ..
C:\>cd "Program Files\MonetDB\MonetDB5"
C:\Program Files\MonetDB\MonetDB5>mclient -p 50003 "bsapuf"
user(win32):monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012-SP3)
Database: MonetDB v11.13.9 (Oct2012-SP3), 'bsapuf'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>\d
sql>CREATE TABLE bsa1 (PDE_EVENT_ID VARCHAR(255), BENE_SEX_IDENT_CD DOUBLE PRECI
SION, BENE_AGE_CAT_CD DOUBLE PRECISION, PDE_DRUG_CD DOUBLE PRECISION, PDE_DRUG_S
TR_CD DOUBLE PRECISION, PDE_DRUG_STR_UNITS_CD DOUBLE PRECISION, PDE_DRUG_DOSE_CD
DOUBLE PRECISION, PDE_DRUG_CLASS_CD DOUBLE PRECISION, PDE_DRUG_QTY_DIS DOUBLE P
RECISION, PDE_DRUG_DAY_SPLY_CD DOUBLE PRECISION, PDE_DRUG_COST DOUBLE PRECISION,
PDE_DRUG_PAT_PAY_CD DOUBLE PRECISION, PDE_DRUG_TYPE_CD DOUBLE PRECISION) ;
operation successful (8.636ms)
sql>
sql>copy 1000000 offset 2 records into bsa1 from 'c:\\temp\\2008_BSA_PartD_Event
s_PUF_1.csv' using delimiters ',' NULL AS '' ;
1000000 affected rows (41.6s)
COMMIT: transaction is aborted because of concurency conflicts, will ROLLBACK in
stead
sql>
sql>
### Actual Results:
COMMIT: transaction is aborted because of concurency conflicts, will ROLLBACK instead
### Expected Results:
both COPY INTO commands should work?
## Comment 18548
Date: 2013-02-22 22:00:27 +0100
From: @mlkersten
MonetDB uses an optimistic concurrency control scheme, which means that when you run two concurrent COPY operations, one is bound to fail at commit time.
See: http://www.monetdb.org/Documentation/Manuals/SQLreference/Transactions
regards, Martin
| Windows Concurrency Error when accessing two separate tables in two separate mclient instances connected to the same mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/3239/comments | 0 | 2020-11-30T12:17:35Z | 2024-06-28T07:23:18Z | https://github.com/MonetDB/MonetDB/issues/3239 | 753,430,433 | 3,239 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-22 15:18:03 +0100
From: Ashish Kumar Singh <<ashishk>>
To: GDK devs <<bugs-common>>
Version: 11.21.19 (Jul2015-SP4)
CC: ashishk, @hannesmuehleisen, @PedroTadim, renalkoclok
Last updated: 2020-06-15 17:22:53 +0200
## Comment 18544
Date: 2013-02-22 15:18:03 +0100
From: Ashish Kumar Singh <<ashishk>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
Build Identifier:
Dear MonetDB Team,
When I try to compile monetdb latest and Feb release with --enable-debug=no --enable-assert=no --enable-optimize=yes options enabled in configure I am observing a massive increase of memory consumption and machine getting hanged as a result!
you can run test case as attached with Bug #3233 for reproducing this issue. with default configure options it is working fine!
Regards,
Ashish
Reproducible: Always
### Steps to Reproduce:
see description
### Actual Results:
memory increases
### Expected Results:
memory consumption should be as good or less than default configure options.
## Comment 19267
Date: 2013-10-10 19:45:35 +0200
From: @hannesmuehleisen
Hello Ashish,
is this still an issue and if so, which platform and which compiler?
Best,
Hannes
## Comment 27764
Date: 2020-06-03 09:09:47 +0200
From: @sjoerdmullender
The content of attachment 665 has been deleted for the following reason:
spam
| Optimise option is not optimising | https://api.github.com/repos/MonetDB/MonetDB/issues/3238/comments | 0 | 2020-11-30T12:17:33Z | 2024-06-27T11:59:02Z | https://github.com/MonetDB/MonetDB/issues/3238 | 753,430,396 | 3,238 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-21 13:25:24 +0100
From: @swingbit
To: GDK devs <<bugs-common>>
Version: 11.15.1 (Feb2013)
CC: @drstmane
Last updated: 2013-03-07 12:41:23 +0100
## Comment 18534
Date: 2013-02-21 13:25:24 +0100
From: @swingbit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
Build Identifier:
Unfortunately it is not easy to make this issue reproducible.
I got the issue on a query that looks like this:
CREATE TABLE "_attributesString" (
"subject" INTEGER,
"attribute" CHARACTER LARGE OBJECT,
"value" CHARACTER LARGE OBJECT,
"prob" DOUBLE DEFAULT 1.0
);
SELECT subject, attribute, value, MAX(prob) as prob FROM "_attributesString" GROUP BY subject, attribute, value;
However, the failure is data-dependent and the data that triggers the failure is produced inside an iterative process.
I got two types of error, depending on the data at hand:
An assertion: gdk/gdk_group.c:482: BATgroup_internal: Assertion `hs->link[hb] == ((BUN) 9223372036854775807LL) || hs->link[hb] < hb' failed.
And a SEGFAULT (I am relatively sure this happens when evaluating the same query):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f9fbc3ff700 (LWP 17502)]
0x00007f9fc74cf8ca in runMALsequence (cntxt=0xf86630, mb=0x7f9f941c24e0, startpc=1, stoppc=49, stk=0x7f9f94e5dc50, env=0x7f9f94e198f0, pcicaller=0x7f9f94debfa0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:801
801 if (isaBatType(getArgType(mb, pci, i))) {
(gdb) bt
0 0x00007f9fc74cf8ca in runMALsequence (cntxt=0xf86630, mb=0x7f9f941c24e0, startpc=1, stoppc=49, stk=0x7f9f94e5dc50, env=0x7f9f94e198f0, pcicaller=0x7f9f94debfa0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:801
1 0x00007f9fc74cf2b3 in runMALsequence (cntxt=0xf86630, mb=0x7f9f941b4860, startpc=1, stoppc=0, stk=0x7f9f94e198f0, env=0x0, pcicaller=0x0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:720
2 0x00007f9fc74ce335 in callMAL (cntxt=0xf86630, mb=0x7f9f941b4860, env=0x7f9fbc3feba0, argv=0x7f9f94c96ee0, debug=0 '\000')
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_interpreter.c:469
3 0x00007f9fbf282f56 in SQLexecutePrepared (c=0xf86630, be=0x7f9f94164740, q=0x7f9f9415c600) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:1840
4 0x00007f9fbf283345 in SQLengineIntern (c=0xf86630, be=0x7f9f94164740) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:1907
5 0x00007f9fbf2838ba in SQLengine (c=0xf86630) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/sql/backends/monet5/sql_scenario.c:2008
6 0x00007f9fc74fba95 in runPhase (c=0xf86630, phase=4) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:522
7 0x00007f9fc74fbc82 in runScenarioBody (c=0xf86630) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:567
8 0x00007f9fc74fbdb4 in runScenario (c=0xf86630) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_scenario.c:586
9 0x00007f9fc74fce4a in MSserveClient (dummy=0xf86630) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/mal/mal_session.c:431
10 0x0000003599007761 in start_thread () from /lib64/libpthread.so.0
11 0x0000003598ce098d in clone () from /lib64/libc.so.6
Reproducible: Sometimes
MonetDB 5 server v11.15.2 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 35.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0d 8 Feb 2011 (compiled with OpenSSL 1.0.0d-fips 8 Feb 2011)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: roberto@spinque01.ins.cwi.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wmissing-include-dirs
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18535
Date: 2013-02-21 14:13:17 +0100
From: @sjoerdmullender
This is the assertion that our hashes link backwards. Apparently they don't always.
Roberto, when this happens in the debugger, can you print both hb and hs->link[hb]?
## Comment 18536
Date: 2013-02-21 14:37:54 +0100
From: @swingbit
(gdb) p hb
$1 = 140
(gdb) p hs->link[hb]
$2 = 282
(gdb)
A bit more context:
0 0x0000003598c328f5 in raise () from /lib64/libc.so.6
1 0x0000003598c340d5 in abort () from /lib64/libc.so.6
2 0x0000003598c2b8b5 in __assert_fail () from /lib64/libc.so.6
3 0x00007f1bb3421368 in BATgroup_internal (groups=0x7f1ba8481448, extents=0x7f1ba8481440, histo=0x7f1ba8481438, b=0x7f1b5c3c7610, g=0x7f1b5cac82b0, e=0x0, h=0x0, subsorted=0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/gdk/gdk_group.c:481
4 0x00007f1bb3427762 in BATgroup (groups=0x7f1ba8481448, extents=0x7f1ba8481440, histo=0x7f1ba8481438, b=0x7f1b5c3c7610, g=0x7f1b5cac82b0, e=0x0, h=0x0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/gdk/gdk_group.c:734
5 0x00007f1bb3baad52 in GRPsubgroup4 (ngid=0x7f1b5c5945f0, next=0x7f1b5c594600, nhis=0x7f1b5c594610, bid=0x7f1b5c5944f0, gid=0x7f1b5c5945c0, eid=0x0, hid=0x0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/modules/kernel/group.mx:565
6 0x00007f1bb3baae93 in GRPsubgroup2 (ngid=0x7f1b5c5945f0, next=0x7f1b5c594600, nhis=0x7f1b5c594610, bid=0x7f1b5c5944f0, gid=0x7f1b5c5945c0)
at /opt/spinque/MonetDBServer/MonetDB.Spinque_Feb2013/src/monetdb5/modules/kernel/group.mx:586
## Comment 18537
Date: 2013-02-21 14:56:05 +0100
From: @sjoerdmullender
It would be interesting to know how the bat (the first argument to the MAL function) got its hash table. Do you know?
Is it possible that the hash table was updated after it was created?
The simple solution would be to not depend on the supposed fact that the linked list in the hash table always point towards lower BUNs. But it would be interesting where in the code that supposition is broken.
## Comment 18538
Date: 2013-02-21 15:06:02 +0100
From: @swingbit
Unfortunately I have difficulties getting the MAL plan of the failing transaction.
## Comment 18541
Date: 2013-02-22 11:06:56 +0100
From: @sjoerdmullender
Changeset [88acc1bec9c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=88acc1bec9c7) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=88acc1bec9c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=88acc1bec9c7)
Changeset description:
We can't exploit hash links being in reverse order for existing hash tables.
We tried to exploit the supposed fact that links in the collision
lists of our hash tables were in reverse order of the BUN number. It
seems this assumption was not correct, at least not in all cases.
This should fix bug #3237.
## Comment 18542
Date: 2013-02-22 11:07:20 +0100
From: @sjoerdmullender
Roberto, can you test please.
## Comment 18543
Date: 2013-02-22 13:35:41 +0100
From: @swingbit
The problem seems indeed solved, thanks!
## Comment 18545
Date: 2013-02-22 15:31:59 +0100
From: @swingbit
The SEGFAULT mentioned in the initial bug report is apparently not (directly) related to the bug fix, as it still occurs (changing the bug title accordingly).
## Comment 18546
Date: 2013-02-22 15:49:43 +0100
From: @sjoerdmullender
Can you then submit a fresh bug report for the segfault?
## Comment 18549
Date: 2013-02-23 00:06:32 +0100
From: @drstmane
Does that segfault also occur with assertions enabled?
## Comment 18550
Date: 2013-02-25 10:07:44 +0100
From: @swingbit
Stefan, I will try that.
What I found so far is that the SEGFAULT does not seem to be related to grouping at all.
I have reduced it now to a simple selection on a view with an user function that does string processing (pcre). But again, it seems data-dependent, so I will file a bug report as soon as I can make it somewhat reproducible (unfortunately I am not allowed to share the whole data as they are).
## Comment 18551
Date: 2013-02-25 10:17:53 +0100
From: @swingbit
Stefan,
Now that I think about it, I am compiling as developer, so assertions are enabled:
--enable-strict --enable-assert --enable-debug --disable-optimize
## Comment 18593
Date: 2013-03-07 12:41:23 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| Assertion on BATgroup_internal | https://api.github.com/repos/MonetDB/MonetDB/issues/3237/comments | 0 | 2020-11-30T12:17:29Z | 2024-06-27T11:59:01Z | https://github.com/MonetDB/MonetDB/issues/3237 | 753,430,366 | 3,237 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-19 13:41:32 +0100
From: Christian Braun <<hcb>>
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: hcb, @njnes
Last updated: 2013-03-07 12:41:22 +0100
## Comment 18520
Date: 2013-02-19 13:41:32 +0100
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
Hello,
i updated from v11.13.9 "Oct2012-SP3" to v11.15.1 "Feb2013" (Debian packages). When connection to a local database with the mclient tool the "\d" command produces no output.
Kind regards,
Christian.
Reproducible: Always
### Steps to Reproduce:
1.mclient db
2.\L trace.txt
3.\d
## Comment 18521
Date: 2013-02-19 13:42:38 +0100
From: Christian Braun <<hcb>>
Created attachment 184
client/server log
> Attached file: [trace.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3236_trace.txt_184) (text/plain, 20401 bytes)
> Description: client/server log
## Comment 18523
Date: 2013-02-19 14:00:42 +0100
From: Christian Braun <<hcb>>
Any statement containing a like seems to fail:
sql>select name from sys.tables where name like 'qwe%';
TypeException:user.s7_1[23]:'pcre.like_filter' undefined in: _40:any := pcre.like_filter(_19:bat[:oid,:str], _38:bat[:oid,:oid], _23:str, _24:str, _41:bit)
TypeException:user.s7_1[24]:'algebra.leftfetchjoin' undefined in: _42:any := algebra.leftfetchjoin(_40:any, _19:bat[:oid,:str])
TypeException:user.s7_1[27]:'bat.append' undefined in: _47:any := bat.append(_4:bat[:oid,:str], _42:any, _48:bit)
TypeException:user.s7_1[42]:'pcre.like_filter' undefined in: _69:any := pcre.like_filter(_54:bat[:oid,:str], _68:bat[:oid,:oid], _58:str, _59:str, _41:bit)
TypeException:user.s7_1[43]:'algebra.leftfetchjoin' undefined in: _70:any := algebra.leftfetchjoin(_69:any, _54:bat[:oid,:str])
TypeException:user.s7_1[46]:'bat.append' undefined in: _73:any := bat.append(_47:any, _70:any, _48:bit)
program contains errors
## Comment 18524
Date: 2013-02-19 14:12:46 +0100
From: @sjoerdmullender
How exactly did you do the update?
Can you check whether all monetdb-related packages are actually up-to-date?
It looks like there is a mix of old and new.
## Comment 18525
Date: 2013-02-19 14:35:53 +0100
From: Christian Braun <<hcb>>
Hello,
to update i ran:
apt-get upgrade
apt-get install monetdb5-server monetdb5-sql
dpkg --purge libmonetdb8
I got 6 MonetDB packages installed. All are 11.15.1:
dpkg -l | grep monet
ii libmonetdb-client6 11.15.1-20130212 MonetDB client/server interface library
ii libmonetdb-stream3 11.15.1-20130212 MonetDB stream library
ii libmonetdb8 11.15.1-20130212 MonetDB core library
ii monetdb-client 11.15.1-20130212 MonetDB database client
ii monetdb5-server 11.15.1-20130212 MonetDB database server version 5
ii monetdb5-sql 11.15.1-20130212 MonetDB SQL support for monetdb5
I have 2 databases on this machine. In both a "select name from sys.tables where name like 'qwe%';" fails. I created a new empty database and there the select/like works.
Kind regards,
Christian.
## Comment 18526
Date: 2013-02-19 15:22:00 +0100
From: Christian Braun <<hcb>>
To make sure this is not caused by my databases, i tested in a virtual machine.
Started with a clean installation of Debian Squeeze.
Installed MonetDB 11.13.9-20130115.
Created a new database.
Updated to 11.15.1-20130212
Then the statement fails: "select name from sys.tables where name like '%t%';"
When creating a new database after the update, the select and "\d" works in the new database.
## Comment 18527
Date: 2013-02-19 15:54:34 +0100
From: @sjoerdmullender
The problem is that the implementation for like and ilike changed. This means that during a database update, we should do something.
The problem is, we forgot this, and the necessary queries don't work. :-(
What is needed is pretty simple. In each updated database the following five queries need to be executed:
drop filter function sys."like"(string, string, string);
drop filter function sys."ilike"(string, string, string);
create filter function sys."like"(val string, pat string, esc string) external name algebra.likesubselect;
create filter function sys."ilike"(val string, pat string, esc string) external name algebra.ilikesubselect;
insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('like', 'ilike') and f.type = 4 and f.schema_id = s.id and s.name = 'sys';
However, the first two don't work, and hence the create queries also don't work.
We will fix this in Feb2013-SP1. That should also fix an already updated database.
The upshot of all this is, you can't use like queries in an updated database (as you found out).
## Comment 18539
Date: 2013-02-21 15:56:33 +0100
From: @njnes
fix in feb2013 branch.
## Comment 18590
Date: 2013-03-07 12:41:22 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| mclient \d produces no output | https://api.github.com/repos/MonetDB/MonetDB/issues/3236/comments | 0 | 2020-11-30T12:17:27Z | 2024-06-27T11:59:00Z | https://github.com/MonetDB/MonetDB/issues/3236 | 753,430,333 | 3,236 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-15 18:46:48 +0100
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.15.1 (Feb2013)
Last updated: 2013-03-07 12:41:20 +0100
## Comment 18480
Date: 2013-02-15 18:46:48 +0100
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17
Build Identifier:
while unquoting values received from the server, the unquote subroutine incorrectly returns 'undef' when the value is 0.
Reproducible: Always
### Steps to Reproduce:
1. sample Perl DBI script selecting from a table with some 0's
2. print received data from fetchall_arrayref using Data::Dumper
### Actual Results:
'undef' is printed instead of original '0'
### Expected Results:
a true 0 is printed
I've included a small patch to fix this issue.
## Comment 18481
Date: 2013-02-15 18:47:55 +0100
From: Rémy Chibois <<rchibois>>
Created attachment 179
Patch fixing the unquote issue when value is 0
> Attached file: [MapiPP-unquote.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3235_MapiPP-unquote.patch_179) (text/plain, 596 bytes)
> Description: Patch fixing the unquote issue when value is 0
## Comment 18556
Date: 2013-02-25 12:35:29 +0100
From: @sjoerdmullender
Changeset [37bd050c9cda](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=37bd050c9cda) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=37bd050c9cda](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=37bd050c9cda)
Changeset description:
Don't return "undef" if 0.
This fixes bug #3235.
Thanks to Rémy Chibois for the report and the fix.
## Comment 18563
Date: 2013-02-25 15:27:01 +0100
From: @sjoerdmullender
Changeset [d222c1c35635](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d222c1c35635) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d222c1c35635](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d222c1c35635)
Changeset description:
Added test for bug #3235.
## Comment 18586
Date: 2013-03-07 12:41:20 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| MapiPP.pm unquote '0' as 'undef' | https://api.github.com/repos/MonetDB/MonetDB/issues/3235/comments | 0 | 2020-11-30T12:17:24Z | 2024-06-27T11:58:59Z | https://github.com/MonetDB/MonetDB/issues/3235 | 753,430,301 | 3,235 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-15 17:50:19 +0100
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: ajdamico, @njnes, @drstmane
Last updated: 2013-06-10 13:33:00 +0200
## Comment 18479
Date: 2013-02-15 17:50:19 +0100
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
I am running MonetDB5 Oct 2012 SP3 on my work Windows 7 desktop computer. My office has what I imagine is a pretty typical mix of networked machines, with a few more powerful servers and larger shared drives that everyone can connect to. (1) When I attempt to import a large CSV file into a MonetDB server on the _local_ disk (C:\My Directory\MonetDB\dbfarm), the importation command runs as expected. (2) When I attempt to import the same CSV file to a MonetDB server stored on a networked drive, the import command fails. (3) Finally, when I *remote desktop* into the server that the networked drive is actually attached to, the importation succeeds again! Here's the error seen in scenario (2) --
GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
!OS: The process cannot access the file because it is being used by another process.
GDKunlink(bat\13\1327.theap)
!OS: The process cannot access the file because it is being used by another process.
So it seems pretty clear that something about windows networked drives is the culprit. This error does not occur on every file (larger files seem more prone to the error), but if an import command does not work on a file, it _consistently_ does not work on that file. As an example, importing this large file works with methods (1) and (3) but not (2) --
http://downloads.cms.gov/BSAPUF/2008_BSA_Carrier_Line_Items_PUF_1.zip
I tried disabling the windows firewall and using different server ports, but I still hit the above error.
I spoke with Hannes about it briefly, he said: "The issue is probably related to the Windows mmap() implementation when talking to a SMB filesystem. It is far from certain that there is something we can do about this, but in either case, we'd like to know about it."
Thanks!!!
Reproducible: Always
### Steps to Reproduce:
These are the three different scenarios described in "Details" -- (1) and (3) work, (2) failed.
**************************
(1) - local disk - works -----
fetch next block: start at:196
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
Database: MonetDB v11.13.9 (Oct2012-SP3), 'bsa'
closing result set
Type \q to quit, \? for a list of available commands
auto commit mode: on
mapi_query:46:SET TIME ZONE INTERVAL '-05:00' HOUR TO MINUTE
fetch next block: start at:198
got next block: length:3
text:&3
got complete block:
text:&3
read_line:&3
allocating new result set
fetch next block: start at:201
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
closing result set
sql>create table mytable (
mapi_query_part:23:create table mytable (
fetch next block: start at:203
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:206
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_id VARCHAR(255),
mapi_query_part:27: car_line_id VARCHAR(255),
fetch next block: start at:208
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:211
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_sex_ident_cd INTEGER,
mapi_query_part:28: bene_sex_ident_cd INTEGER,
fetch next block: start at:213
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:216
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_age_cat_cd INTEGER,
mapi_query_part:26: bene_age_cat_cd INTEGER,
fetch next block: start at:218
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:221
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_icd9_dgns_cd VARCHAR(255),
mapi_query_part:37: car_line_icd9_dgns_cd VARCHAR(255),
fetch next block: start at:223
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:226
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_hcpcs_cd VARCHAR(255),
mapi_query_part:33: car_line_hcpcs_cd VARCHAR(255),
fetch next block: start at:228
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:231
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_betos_cd VARCHAR(255),
mapi_query_part:33: car_line_betos_cd VARCHAR(255),
fetch next block: start at:233
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:236
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_srvc_cnt INTEGER,
mapi_query_part:28: car_line_srvc_cnt INTEGER,
fetch next block: start at:238
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:241
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_prvdr_type_cd INTEGER,
mapi_query_part:33: car_line_prvdr_type_cd INTEGER,
fetch next block: start at:243
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:246
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_cms_type_srvc_cd VARCHAR(255),
mapi_query_part:41: car_line_cms_type_srvc_cd VARCHAR(255),
fetch next block: start at:248
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:251
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_place_of_srvc_cd INTEGER,
mapi_query_part:36: car_line_place_of_srvc_cd INTEGER,
fetch next block: start at:253
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:256
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_hcpcs_pmt_amt INTEGER
mapi_query_part:27: car_hcpcs_pmt_amt INTEGER
fetch next block: start at:258
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:261
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more>) ;
mapi_query_part:4:) ;
fetch next block: start at:263
got next block: length:3
text:&3
got complete block:
text:&3
read_line:&3
allocating new result set
fetch next block: start at:266
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
operation successful (118.294ms)
closing result set
sql>
fetch next block: start at:268
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
sql>COPY 9676440 offset 2 records INTO mytable FROM 'C:\My Directory\BSAPUF\2008
\2008_BSA_Carrier_Line_Items_PUF_1.csv' USING DELIMITERS ',','\n','\"' NULL AS '
' ;
mapi_query_part:160:COPY 9676440 offset 2 records INTO mytable FROM 'C:\My Direc
tory\BSAPUF\2008\2008_BSA_Carrier_Line_Items_PUF_1.csv' USING DELIMITERS ',','\n
','\"' NULL AS '' ;
fetch next block: start at:270
got next block: length:14
text:&2 9676439 -1
got complete block:
text:&2 9676439 -1
read_line:&2 9676439 -1
allocating new result set
fetch next block: start at:284
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
9676439 affected rows (3m 26s)
closing result set
sql>
**************************
(2) - networked disk - fails -----
read_line:☺
more> car_line_id VARCHAR(255),
mapi_query_part:27: car_line_id VARCHAR(255),
fetch next block: start at:208
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:211
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_sex_ident_cd INTEGER,
mapi_query_part:28: bene_sex_ident_cd INTEGER,
fetch next block: start at:213
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:216
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_age_cat_cd INTEGER,
mapi_query_part:26: bene_age_cat_cd INTEGER,
fetch next block: start at:218
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:221
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_icd9_dgns_cd VARCHAR(255),
mapi_query_part:37: car_line_icd9_dgns_cd VARCHAR(255),
fetch next block: start at:223
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:226
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_hcpcs_cd VARCHAR(255),
mapi_query_part:33: car_line_hcpcs_cd VARCHAR(255),
fetch next block: start at:228
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:231
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_betos_cd VARCHAR(255),
mapi_query_part:33: car_line_betos_cd VARCHAR(255),
fetch next block: start at:233
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:236
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_srvc_cnt INTEGER,
mapi_query_part:28: car_line_srvc_cnt INTEGER,
fetch next block: start at:238
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:241
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_prvdr_type_cd INTEGER,
mapi_query_part:33: car_line_prvdr_type_cd INTEGER,
fetch next block: start at:243
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:246
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_cms_type_srvc_cd VARCHAR(255),
mapi_query_part:41: car_line_cms_type_srvc_cd VARCHAR(255),
fetch next block: start at:248
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:251
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_place_of_srvc_cd INTEGER,
mapi_query_part:36: car_line_place_of_srvc_cd INTEGER,
fetch next block: start at:253
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:256
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_hcpcs_pmt_amt INTEGER
mapi_query_part:27: car_hcpcs_pmt_amt INTEGER
fetch next block: start at:258
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:261
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more>) ;
mapi_query_part:4:) ;
fetch next block: start at:263
got next block: length:3
text:&3
got complete block:
text:&3
read_line:&3
allocating new result set
fetch next block: start at:266
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
operation successful (289.145ms)
closing result set
sql>
fetch next block: start at:268
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
sql>COPY 9676440 offset 2 records INTO mytable FROM 'C:\My Directory\BSAPUF\2008
\2008_BSA_Carrier_Line_Items_PUF_1.csv' USING DELIMITERS ',','\n','\"' NULL AS '
' ;
mapi_query_part:160:COPY 9676440 offset 2 records INTO mytable FROM 'C:\My Direc
tory\BSAPUF\2008\2008_BSA_Carrier_Line_Items_PUF_1.csv' USING DELIMITERS ',','\n
','\"' NULL AS '' ;
fetch next block: start at:270
got next block: length:252
text:!GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!GDKunlink(bat\13\1327.theap)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!
got complete block:
text:!GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!GDKunlink(bat\13\1327.theap)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!
read_line:!GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
allocating new result set
got complete block:
text:!!OS: The process cannot access the file because it is being used by anothe
r process.
!GDKunlink(bat\13\1327.theap)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!
read_line:!!OS: The process cannot access the file because it is being used by a
nother process.
got complete block:
text:!GDKunlink(bat\13\1327.theap)
!!OS: The process cannot access the file because it is being used by another pro
cess.
!
read_line:!GDKunlink(bat\13\1327.theap)
got complete block:
text:!!OS: The process cannot access the file because it is being used by anothe
r process.
!
read_line:!!OS: The process cannot access the file because it is being used by a
nother process.
got complete block:
text:!
read_line:!
fetch next block: start at:522
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
!OS: The process cannot access the file because it is being used by another proc
ess.
GDKunlink(bat\13\1327.theap)
!OS: The process cannot access the file because it is being used by another proc
ess.
closing result set
sql>
**************************
(3) - remote desktop into server so networked disk becomes local disk - works -----
read_line:[ "monet_release", "Oct2012-SP3" ]
fetch next block: start at:196
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
Database: MonetDB v11.13.9 (Oct2012-SP3), 'bsa'
closing result set
Type \q to quit, \? for a list of available commands
auto commit mode: on
mapi_query:46:SET TIME ZONE INTERVAL '-05:00' HOUR TO MINUTE
fetch next block: start at:198
got next block: length:3
text:&3
got complete block:
text:&3
read_line:&3
allocating new result set
fetch next block: start at:201
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
closing result set
sql>create table mytable3 (
mapi_query_part:24:create table mytable3 (
fetch next block: start at:203
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:206
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_id VARCHAR(255),
mapi_query_part:27: car_line_id VARCHAR(255),
fetch next block: start at:208
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:211
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_sex_ident_cd INTEGER,
mapi_query_part:28: bene_sex_ident_cd INTEGER,
fetch next block: start at:213
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:216
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> bene_age_cat_cd INTEGER,
mapi_query_part:26: bene_age_cat_cd INTEGER,
fetch next block: start at:218
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:221
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_icd9_dgns_cd VARCHAR(255),
mapi_query_part:37: car_line_icd9_dgns_cd VARCHAR(255),
fetch next block: start at:223
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:226
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_hcpcs_cd VARCHAR(255),
mapi_query_part:33: car_line_hcpcs_cd VARCHAR(255),
fetch next block: start at:228
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:231
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_betos_cd VARCHAR(255),
mapi_query_part:33: car_line_betos_cd VARCHAR(255),
fetch next block: start at:233
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:236
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_srvc_cnt INTEGER,
mapi_query_part:28: car_line_srvc_cnt INTEGER,
fetch next block: start at:238
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:241
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_prvdr_type_cd INTEGER,
mapi_query_part:33: car_line_prvdr_type_cd INTEGER,
fetch next block: start at:243
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:246
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_cms_type_srvc_cd VARCHAR(255),
mapi_query_part:41: car_line_cms_type_srvc_cd VARCHAR(255),
fetch next block: start at:248
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:251
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_line_place_of_srvc_cd INTEGER,
mapi_query_part:36: car_line_place_of_srvc_cd INTEGER,
fetch next block: start at:253
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:256
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more> car_hcpcs_pmt_amt INTEGER
mapi_query_part:27: car_hcpcs_pmt_amt INTEGER
fetch next block: start at:258
got next block: length:3
text:☺☻
got complete block:
text:☺☻
read_line:☺☻
fetch next block: start at:261
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
more>) ;
mapi_query_part:4:) ;
fetch next block: start at:263
got next block: length:3
text:&3
got complete block:
text:&3
read_line:&3
allocating new result set
fetch next block: start at:266
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
operation successful (276.500ms)
closing result set
sql>
fetch next block: start at:268
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
sql>COPY 9676440 offset 2 records INTO mytable3 FROM 'v:\temp\2008_BSA_Carrier_L
ine_Items_PUF_1.csv' USING DELIMITERS ',','\n','\"' NULL AS '' ;
mapi_query_part:141:COPY 9676440 offset 2 records INTO mytable3 FROM 'v:\temp\20
08_BSA_Carrier_Line_Items_PUF_1.csv' USING DELIMITERS ',','\n','\"' NULL AS '' ;
fetch next block: start at:270
got next block: length:14
text:&2 9676439 -1
got complete block:
text:&2 9676439 -1
read_line:&2 9676439 -1
allocating new result set
fetch next block: start at:284
got next block: length:0
text:
got complete block:
text:☺
read_line:☺
9676439 affected rows (2m 14s)
closing result set
sql>
### Actual Results:
GDKerror:!ERROR: GDKunlink(bat\13\1327.tail)
!OS: The process cannot access the file because it is being used by another process.
GDKunlink(bat\13\1327.theap)
!OS: The process cannot access the file because it is being used by another process.
### Expected Results:
9676439 affected rows (2m 14s)
closing result set
MonetDB 5 server v11.13.9 "Oct2012-SP3"
Serving database 'bsa', using 2 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 15.873 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
MonetDB/JAQL module loaded
MonetDB/SQL module loaded
## Comment 18566
Date: 2013-02-25 16:19:57 +0100
From: @sjoerdmullender
There may be several reasons why you would get this error.
One is indeed the windows implementation of memory mapped files over network drives. We have not experimented with this, so I can't say whether it really is an issue.
Another issue is the Windows indexing service. Normally the database is stored inside the %APPDATA% folder which is not indexed, but if your data is on another system and in a folder that the indexing service on that system indexes, it may well happen that the indexing service is working on a file when MonetDB decides that it wants to delete the file. I have seen things like this happen in the past on a local drive. So, please make sure the database is not getting indexed.
Having said this, we have not really tried the server with data on remote systems. And honestly, we don't recommend it. It would be better to run the server where the data is. I do understand the use case, though.
## Comment 18807
Date: 2013-06-10 09:12:42 +0200
From: @njnes
could you verify if the index service was running.
## Comment 18808
Date: 2013-06-10 13:26:42 +0200
From: Anthony Damico <<ajdamico>>
it was, but we turned it off, and had the same problem. i understand this is a low-priority for your team, but i do not believe this problem has been resolved :)
## Comment 18809
Date: 2013-06-10 13:33:00 +0200
From: @drstmane
Any virus scanner or any other background job accessing files might be another candidate that might cause such problems ...
| Windows Networked Drive Issue with COPY INTO | https://api.github.com/repos/MonetDB/MonetDB/issues/3234/comments | 0 | 2020-11-30T12:17:19Z | 2024-06-27T11:58:58Z | https://github.com/MonetDB/MonetDB/issues/3234 | 753,430,242 | 3,234 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-12 19:45:54 +0100
From: Ashish Kumar Singh <<ashishk>>
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: ashishk, @mlkersten, @njnes, @drstmane
Last updated: 2013-03-07 12:41:22 +0100
## Comment 18467
Date: 2013-02-12 19:45:54 +0100
From: Ashish Kumar Singh <<ashishk>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
Build Identifier:
We got below when a monet db compiled against sles 10 SP4 was run on SLES 11 SP2. Any suggestion filing as a bug as don't have access to my registered email any poionter wil help!
cat /var/log/messages | grep mserver Feb 12 14:54:17 blrec3vm6 kernel: mserver5[26559]: segfault at 2000 ip 00007fa105edb4d5 sp 00007fa0ffffee30 error 6 in lib_sql.so[7fa105dd8000+140000] Feb 12 15:03:03 blrec3vm6 kernel: mserver5[32124]: segfault at 28 ip 00007fc0eb916e95 sp 00007fc0e78d4f20 error 6 in libmonetdb5.so.13[7fc0eb467000+63b000]
Feb 12 15:17:38 blrec3vm6 kernel: mserver5[12463]: segfault at 28 ip 00007f6b7b1dae95 sp 00007f6b77198f20 error 6 in libmonetdb5.so.13[7f6b7ad2b000+63b000]
Feb 12 15:36:29 blrec3vm6 kernel: mserver5[15897]: segfault at 8 ip 00007f9e9858baf1 sp 00007f9e941d6420 error 4 in libbat.so.8[7f9e9853e000+28a000] Feb 12 16:09:41 blrec3vm6 kernel: mserver5[17883]: segfault at 18 ip 00007fabed454708 sp 00007fabec74cde0 error 4 in lib_sql.so[7fabed359000+140000] Feb 12 17:40:43 blrec3vm6 kernel: mserver5[24264]: segfault at 0 ip 00007fa921c7876e sp 00007fa91fb63d10 error 6 in libc-2.9.so[7fa921b93000+14f000] Feb 12 17:44:18 blrec3vm6 kernel: mserver5[26067]: segfault at 2000 ip 00007fb5048144d5 sp 00007fb503d05e30 error 6 in lib_sql.so[7fb504711000+140000] Feb 12 18:52:54 blrec3vm6 kernel: mserver5[28356]: segfault at 2000 ip 00007f0c3a93b4d5 sp 00007f0c39e2ce30 error 6 in lib_sql.so[7f0c3a838000+140000]
Reproducible: Always
## Comment 18473
Date: 2013-02-13 17:26:43 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi Guys,
This I got with latest candidate build also, any suggestions when this can happen?
Feb 13 14:16:36 blrec3vm30 kernel: mserver5[12299]: segfault at 28 ip 00007f712a08de95 sp 00007f71260cbf20 error 6 in libmonetdb5.so.13[7f7129bde000+63b000]
Feb 13 14:38:39 blrec3vm30 kernel: mserver5[11872]: segfault at 20 ip 00007fb85c420e1d sp 00007fb85ae72810 error 4 in lib_sql.so[7fb85c325000+140000]
Feb 13 14:52:21 blrec3vm30 kernel: mserver5[11876]: segfault at 28 ip 00007feb7af57e95 sp 00007feb76f95f20 error 6 in libmonetdb5.so.13[7feb7aaa8000+63b000]
Feb 13 15:28:19 blrec3vm30 kernel: mserver5[3541]: segfault at 20 ip 00007fbc8ec56932 sp 00007fbc8dcad020 error 4 in lib_sql.so[7fbc8eb5b000+140000]
Feb 13 15:30:43 blrec3vm30 kernel: mserver5[8618]: segfault at 20 ip 00007f604502cf75 sp 00007f6043cdd760 error 6 in lib_sql.so[7f6044fad000+140000]
Feb 13 16:18:42 blrec3vm30 kernel: mserver5[8674]: segfault at 28 ip 00007f4b011d4e95 sp 00007f4afd212f20 error 6 in libmonetdb5.so.13[7f4b00d25000+63b000]
Feb 13 16:38:33 blrec3vm30 kernel: mserver5[8994]: segfault at 28 ip 00007f45352cce95 sp 00007f453130af20 error 6 in libmonetdb5.so.13[7f4534e1d000+63b000]
Feb 13 17:27:08 blrec3vm30 kernel: mserver5[9300]: segfault at 28 ip 00007fc87c115e95 sp 00007fc878153f20 error 6 in libmonetdb5.so.13[7fc87bc66000+63b000]
Feb 13 17:47:06 blrec3vm30 kernel: mserver5[9463]: segfault at 28 ip 00007fd5fd88ce95 sp 00007fd5f98caf20 error 6 in libmonetdb5.so.13[7fd5fd3dd000+63b000]
Feb 13 21:18:21 blrec3vm30 kernel: mserver5[8465]: segfault at 158a5000 ip 00007fd8175cb703 sp 00007fd80fbfc700 error 4 in libbat.so.9[7fd81757d000+2ee000]
Feb 13 21:35:13 blrec3vm30 kernel: mserver5[9599]: segfault at 7f2ab304b000 ip 00007f2abbcd5703 sp 00007f2ab5129700 error 4 in libbat.so.9[7f2abbc87000+2ee000]
Feb 13 21:35:52 blrec3vm30 kernel: mserver5[11622]: segfault at 5c2e000 ip 00007fa96787d703 sp 00007fa95fe48700 error 4 in libbat.so.9[7fa96782f000+2ee000]
Feb 13 21:38:01 blrec3vm30 kernel: mserver5[18981]: segfault at 9012000 ip 00007ff8db76f703 sp 00007ff8d3b39700 error 4 in libbat.so.9[7ff8db721000+2ee000]
## Comment 18474
Date: 2013-02-13 17:40:24 +0100
From: @mlkersten
Hi Ashish
No, for sensible information you should use compilation with
--enable-assert --enable-debug --disable-optimize --enable-strict
Followed by a backtrace of the threads, e.g.
thr apply all where
regards, Martin
## Comment 18475
Date: 2013-02-14 10:00:03 +0100
From: Ashish Kumar Singh <<ashishk>>
Guys,
When I was comiling with these options as suggested by you it is giving me error below any pointers please ?
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../common/options -I./../common/options -I../common/stream -I./../common/stream -I../common/utils -I./../common/utils -DLIBGDK -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wmissing-include-dirs -D_REENTRANT -c -o libbat_la-gdk_utils.lo `test -f 'gdk_utils.c' || echo './'`gdk_utils.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../common/options -I./../common/options -I../common/stream -I./../common/stream -I../common/utils -I./../common/utils -DLIBGDK -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wmissing-include-dirs -D_REENTRANT -c gdk_utils.c -fPIC -DPIC -o .libs/libbat_la-gdk_utils.o
cc1: warnings being treated as errors
gdk_utils.c: In function 'GDKmallocmax':
gdk_utils.c:689: warning: value computed is not used
gdk_utils.c: In function 'GDKfree_':
gdk_utils.c:750: warning: value computed is not used
gdk_utils.c: In function 'GDKreallocmax':
gdk_utils.c:812: warning: value computed is not used
gdk_utils.c:813: warning: value computed is not used
gdk_utils.c: In function 'GDKmmap':
gdk_utils.c:863: warning: value computed is not used
gdk_utils.c: In function 'GDKmunmap':
gdk_utils.c:877: warning: value computed is not used
make[3]: *** [libbat_la-gdk_utils.lo] Error 1
make[3]: Leaving directory `/opt/MonetDB-11.15.1/gdk'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/opt/MonetDB-11.15.1/gdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/MonetDB-11.15.1'
make: *** [all] Error 2
[root@localhost MonetDB-11.15.1]
## Comment 18476
Date: 2013-02-14 10:19:04 +0100
From: @drstmane
a)
which exact code version of MonetDB are we talking about? HG changeset? tarball of when from where?
b)
omit --enable-strict
## Comment 18477
Date: 2013-02-14 10:21:01 +0100
From: @drstmane
Moreover, with out knowing at what your doing (e.g., which kind of workload you run on what kind of data) that does/might trigger the segfault, we cannot say much about why they happen ...
## Comment 18478
Date: 2013-02-14 10:33:31 +0100
From: Ashish Kumar Singh <<ashishk>>
removing enable strict did the trick.
## Comment 18482
Date: 2013-02-18 14:03:17 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi ,
I have created core dump files with backtrack which shall be helpful for you.
Core was generated by `/usr/local/bin/mserver5 --dbpath=/opt/ashishtest/testfarm/pbsworksdb --set mero'.
Program terminated with signal 6, Aborted.
0 0x0000003722430285 in raise () from /lib64/libc.so.6
(gdb) thr app all bt
Thread 9 (Thread 0x2b73390a7f90 (LWP 7635)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b73383175bb in MT_sleep_ms (ms=5000) at gdk_posix.c:1003
2 0x0000000000403596 in main (argc=20, av=0x7ffff60d0d98) at mserver5.c:626
Thread 8 (Thread 7636):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b73383175bb in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002b73382446ee in GDKvmtrim (limit=0x2b733895c0d8) at gdk_utils.c:918
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 7 (Thread 7637):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b73383175bb in MT_sleep_ms (ms=1000) at gdk_posix.c:1003
2 0x00002b7337be68ea in profilerHeartbeat (dummy=0x0) at mal_profiler.c:1431
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 6 (Thread 7638):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b7337d81a39 in SERVERlistenThread (Sock=0xf339a70) at mal_mapi.c:209
---Type <return> to continue, or q <return> to quit---
2 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
3 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 5 (Thread 7640):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b73383175bb in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002aaaab153b30 in store_manager () at store.c:1533
3 0x00002aaaab0eb4ae in mvc_logmanager () at sql_mvc.c:149
4 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
5 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 4 (Thread 7796):
0 0x0000003722c0d9eb in read () from /lib64/libpthread.so.0
1 0x00002b7338c94959 in socket_read (s=0xf1f0d60, buf=0x411e4ec6, elmsize=2,
cnt=1) at stream.c:1455
2 0x00002b7338c97b1d in mnstr_readSht (s=0xf1f0d60, val=0x411e4ec6)
at stream.c:2867
3 0x00002b7338c96eef in bs_read (ss=0xf1e0f40, buf=0xf682760, elmsize=1,
cnt=1048320) at stream.c:2556
4 0x00002b7338c98ad5 in bstream_read (s=0xf1c0190, size=1048320)
at stream.c:3122
5 0x00002b7338c98e4e in bstream_next (s=0xf1c0190) at stream.c:3189
6 0x00002aaaab04e584 in SQLreader (c=0xe030b20) at sql_scenario.c:1216
---Type <return> to continue, or q <return> to quit---
7 0x00002b7337bf4d2a in runPhase (c=0xe030b20, phase=0) at mal_scenario.c:522
8 0x00002b7337bf4e07 in runScenarioBody (c=0xe030b20) at mal_scenario.c:552
9 0x00002b7337bf4fd1 in runScenario (c=0xe030b20) at mal_scenario.c:586
10 0x00002b7337bf5e5a in MSserveClient (dummy=0xe030b20) at mal_session.c:431
11 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
12 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 3 (Thread 7797):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002b7337bcf5f1 in q_dequeue (q=0xe112dd0) at mal_dataflow.c:196
2 0x00002b7337bcf7f5 in DFLOWworker (t=0x2b73380b4f60) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 2 (Thread 7798):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002b7337bcf5f1 in q_dequeue (q=0xe112dd0) at mal_dataflow.c:196
2 0x00002b7337bcf7f5 in DFLOWworker (t=0x2b73380b4f68) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x41a93940 (LWP 9131)):
0 0x0000003722430285 in raise () from /lib64/libc.so.6
---Type <return> to continue, or q <return> to quit---
1 0x0000003722431d30 in abort () from /lib64/libc.so.6
2 0x0000003722429706 in __assert_fail () from /lib64/libc.so.6
3 0x00002aaaab162b73 in delta_append_val (bat=0xfa398e0, i=0xf2ab300)
at bat_storage.c:319
4 0x00002aaaab162def in append_col (tr=0xfa3a200, c=0xfc03890, i=0xf2ab300,
tpe=11) at bat_storage.c:343
5 0x00002aaaab084ae4 in mvc_append_wrap (cntxt=0xe030838, mb=0xfd31980,
stk=0xf2ab170, pci=0xfca2b80) at sql.mx:3261
6 0x00002b7337bcc737 in runMALsequence (cntxt=0xe030838, mb=0xfd31980,
startpc=1, stoppc=0, stk=0xf2ab170, env=0x0, pcicaller=0x0)
at mal_interpreter.c:641
7 0x00002b7337bcbc4a in callMAL (cntxt=0xe030838, mb=0xfd31980,
env=0x41a92e48, argv=0xf439ca0, debug=0 '\000') at mal_interpreter.c:469
8 0x00002aaaab0507b7 in SQLexecutePrepared (c=0xe030838, be=0xfa30ca0,
q=0xfbc19a0) at sql_scenario.c:1773
9 0x00002aaaab050b27 in SQLengineIntern (c=0xe030838, be=0xfa30ca0)
at sql_scenario.c:1840
10 0x00002aaaab050fd8 in SQLengine (c=0xe030838) at sql_scenario.c:1941
11 0x00002b7337bf4d2a in runPhase (c=0xe030838, phase=4) at mal_scenario.c:522
12 0x00002b7337bf4ee8 in runScenarioBody (c=0xe030838) at mal_scenario.c:566
13 0x00002b7337bf4fd1 in runScenario (c=0xe030838) at mal_scenario.c:586
14 0x00002b7337bf5e5a in MSserveClient (dummy=0xe030838) at mal_session.c:431
15 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
---Type <return> to continue, or q <return> to quit---
16 0x00000037224d3c1d in clone () from /lib64/libc.so.6
## Comment 18483
Date: 2013-02-18 14:03:55 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 180
trace 1
> Attached file: [core-1](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3233_core-1_180) (application/octet-stream, 5483 bytes)
> Description: trace 1
## Comment 18484
Date: 2013-02-18 14:04:07 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 181
trace 2
> Attached file: [core-2](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3233_core-2_181) (application/octet-stream, 4021 bytes)
> Description: trace 2
## Comment 18485
Date: 2013-02-18 14:06:45 +0100
From: Ashish Kumar Singh <<ashishk>>
A description of our use case is :
One of our application component does following activities:
1. Insertion of data
2. Updation of data when updates are available
3. Deletion of data when record is stale from business perspective
4. Reading of data to calculate some derived matrices
Above can happen in parallel.
Please guide this crash issue is very critical for our successful usage of monetdb and is kind of showstopper for us.
## Comment 18486
Date: 2013-02-18 14:09:49 +0100
From: Ashish Kumar Singh <<ashishk>>
This is using feb candidate build from http://dev.monetdb.org/downloads/testing/sources/Latest/
## Comment 18487
Date: 2013-02-18 17:07:27 +0100
From: Ashish Kumar Singh <<ashishk>>
Just wondering if anyone can have a look on the issue , and can suggest some workarounds / fixes??
## Comment 18488
Date: 2013-02-18 17:16:03 +0100
From: @sjoerdmullender
Does this still happen with the latest nightly build?
You can either get the latest version from Mercurial repository (hg clone -u Feb2013 http://dev.monetdb.org/hg/MonetDB) or you can get a pre-bootstrapped tar ball from the nightly testing (http://monetdb.cwi.nl/testweb/web/status.php, go to the highest finished run on the Feb2013 branch, click on the link on the first line that says XX files, then download the tar ball).
## Comment 18489
Date: 2013-02-18 17:18:56 +0100
From: Ashish Kumar Singh <<ashishk>>
I took one posted in latest testing area, which was placed on 12 th of this month, are you suggesting something like this was fixed after that?
## Comment 18490
Date: 2013-02-18 18:06:45 +0100
From: Ashish Kumar Singh <<ashishk>>
Latest is not building from feb branch!
## Comment 18491
Date: 2013-02-18 18:24:03 +0100
From: @sjoerdmullender
You took the sources of the Feb2013 release candidate. After the release candidate was built there have been fixes to the Feb2013 branch from which it was built. What I want to know is whether one of those fixes fixed your issue already (in which case I may decide to build a new relase candidate).
I hope this is clear.
## Comment 18492
Date: 2013-02-18 18:33:38 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi ,
Yes this is clear , when I am trying to compile latest from February 2013 dev branch it is giving me errors below:
I am doing :
1. bootstrap
2. ./configure --enable-assert --enable-debug --disable-optimize
3. make
Change list I took is [f82d192b0bf7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f82d192b0bf7)
12th Feb release candidate was building fine though.
-I../common/stream -I./../common/stream -I../common/utils -I./../common/utils -DLIBGDK -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wmissing-include-dirs -D_REENTRANT -c gdk_search.c -fPIC -DPIC -o .libs/libbat_la-gdk_search.o
cc1: warnings being treated as errors
gdk_search.c: In function 'BAThash':
gdk_search.c:239: warning: value computed is not used
gdk_search.c:239: warning: value computed is not used
gdk_search.c:239: warning: value computed is not used
make[3]: *** [libbat_la-gdk_search.lo] Error 1
make[3]: Leaving directory `/opt/MonetDB-f82d192b0bf7/gdk'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/opt/MonetDB-f82d192b0bf7/gdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/MonetDB-f82d192b0bf7'
make: *** [all] Error 2
[root@localhost MonetDB-f82d192b0bf7]
## Comment 18493
Date: 2013-02-18 18:51:26 +0100
From: @sjoerdmullender
(In reply to comment 17)
> Hi ,
>
> Yes this is clear , when I am trying to compile latest from February 2013 dev
> branch it is giving me errors below:
>
> I am doing :
>
> 1. bootstrap
> 2. ./configure --enable-assert --enable-debug --disable-optimize
> 3. make
>
> Change list I took is [f82d192b0bf7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f82d192b0bf7)
That is not the correct branch. Please use the command I gave you:
hg clone -u Feb2013 http://dev.monetdb.org/hg/MonetDB
(Or clean up everything that was created by this attempt and then do:
hg update Feb2013
./bootstrap
./configure ...
etc.)
## Comment 18494
Date: 2013-02-18 18:56:46 +0100
From: @grobian
(In reply to comment 13)
> Does this still happen with the latest nightly build?
> You can either get the latest version from Mercurial repository (hg clone -u
> Feb2013 http://dev.monetdb.org/hg/MonetDB) or you can get a pre-bootstrapped
> tar ball from the nightly testing
> (http://monetdb.cwi.nl/testweb/web/status.php, go to the highest finished run
> on the Feb2013 branch, click on the link on the first line that says XX files,
> then download the tar ball).
or just
http://monetdb.cwi.nl/testweb/web/MonetDB-Feb2013-latest.tar.bz2
## Comment 18495
Date: 2013-02-18 19:15:32 +0100
From: Ashish Kumar Singh <<ashishk>>
Thanks! now tests are running will let you know about outcome.
## Comment 18496
Date: 2013-02-18 19:27:36 +0100
From: Ashish Kumar Singh <<ashishk>>
No Luck, Houston we have a problem!!
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x407f8940 (LWP 1865)]
0x0000003722430285 in raise () from /lib64/libc.so.6
(gdb) thr app all bt
Thread 46 (Thread 0x407f8940 (LWP 1865)):
0 0x0000003722430285 in raise () from /lib64/libc.so.6
1 0x0000003722431d30 in abort () from /lib64/libc.so.6
2 0x0000003722429706 in __assert_fail () from /lib64/libc.so.6
3 0x00002aaaab16516f in tr_update_delta (tr=0x15fcdef0, obat=0x16093910,
cbat=0x161ddee0, snapshot_minsize=1024) at bat_storage.c:1441
4 0x00002aaaab165d0f in update_table (tr=0x15fcdef0, ft=0x163a4dd0,
tt=0x16084930) at bat_storage.c:1563
5 0x00002aaaab1567dd in rollforward_update_table (tr=0x15fcdef0,
ft=0x163a4dd0, tt=0x16084930, mode=3) at store.c:2671
6 0x00002aaaab155789 in rollforward_changeset_updates (tr=0x15fcdef0,
fs=0x16383d00, ts=0x15ff0270, b=0x15ff0250,
rollforward_updates=0x2aaaab15644d <rollforward_update_table>,
rollforward_creates=0x2aaaab155d62 <rollforward_create_table>,
rollforward_deletes=0x2aaaab156248 <rollforward_drop_table>,
fd=0x2aaaab1568b7 <conditional_table_dup>, mode=3) at store.c:2284
7 0x00002aaaab156c1f in rollforward_update_schema (tr=0x15fcdef0,
fs=0x16383ce0, ts=0x15ff0250, mode=3) at store.c:2746
8 0x00002aaaab155789 in rollforward_changeset_updates (tr=0x15fcdef0,
fs=0x15fcdf20, ts=0x161c6720, b=0x161c66f0,
rollforward_updates=0x2aaaab1569a8 <rollforward_update_schema>,
rollforward_creates=0x2aaaab156403 <rollforward_create_schema>,
---Type <return> to continue, or q <return> to quit---
rollforward_deletes=0x2aaaab156397 <rollforward_drop_schema>,
fd=0x2aaaab154ebd <schema_dup>, mode=3) at store.c:2284
9 0x00002aaaab156dc1 in rollforward_trans (tr=0x15fcdef0, mode=3)
at store.c:2768
10 0x00002aaaab1581f4 in sql_trans_commit (tr=0x15fcdef0) at store.c:3170
11 0x00002aaaab0ea742 in mvc_commit (m=0x1643d390, chain=0, name=0x0)
at sql_mvc.c:267
12 0x00002aaaab04d0da in SQLautocommit (c=0x14dec838, m=0x1643d390)
at sql_scenario.c:1116
13 0x00002aaaab04d314 in SQLreader (c=0x14dec838) at sql_scenario.c:1204
14 0x00002af73ca6cad2 in runPhase (c=0x14dec838, phase=0)
at mal_scenario.c:522
15 0x00002af73ca6cbaf in runScenarioBody (c=0x14dec838) at mal_scenario.c:552
16 0x00002af73ca6cd79 in runScenario (c=0x14dec838) at mal_scenario.c:586
17 0x00002af73ca6dc02 in MSserveClient (dummy=0x14dec838) at mal_session.c:431
18 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
19 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 7 (Thread 0x41edf940 (LWP 1130)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002af73d18a27f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002af73d0b73b2 in GDKvmtrim (limit=0x2af73d7ce358) at gdk_utils.c:918
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
---Type <return> to continue, or q <return> to quit---
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 6 (Thread 0x40312940 (LWP 1131)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002af73d18a27f in MT_sleep_ms (ms=1000) at gdk_posix.c:1003
2 0x00002af73ca5e692 in profilerHeartbeat (dummy=0x0) at mal_profiler.c:1431
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 5 (Thread 0x420e0940 (LWP 1132)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002af73cbf97e1 in SERVERlistenThread (Sock=0x160f5a70)
at mal_mapi.c:209
2 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
3 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 4 (Thread 0x4194b940 (LWP 1133)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002af73d18a27f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002aaaab152a90 in store_manager () at store.c:1533
3 0x00002aaaab0ea222 in mvc_logmanager () at sql_mvc.c:149
4 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
5 0x00000037224d3c1d in clone () from /lib64/libc.so.6
---Type <return> to continue, or q <return> to quit---
Thread 3 (Thread 0x41631940 (LWP 1215)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002af73ca473cd in q_dequeue (q=0x14eb4010) at mal_dataflow.c:196
2 0x00002af73ca475d1 in DFLOWworker (t=0x2af73cf2bf40) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x422e1940 (LWP 1216)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002af73ca473cd in q_dequeue (q=0x14eb4010) at mal_dataflow.c:196
2 0x00002af73ca475d1 in DFLOWworker (t=0x2af73cf2bf48) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x2af73df16f30 (LWP 1129)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002af73d18a27f in MT_sleep_ms (ms=5000) at gdk_posix.c:1003
2 0x0000000000403596 in main (argc=20, av=0x7fffaff24338) at mserver5.c:626
(gdb)
## Comment 18497
Date: 2013-02-18 19:37:49 +0100
From: @njnes
did your last run start with a clean database or some older (and therefor possibly corrupt) db? Just to exclude this case..
## Comment 18498
Date: 2013-02-18 19:47:05 +0100
From: Ashish Kumar Singh <<ashishk>>
That was with OLD database:
Below is the crash with a fresh DB farm :
(gdb) thr app all bt
Thread 40 (Thread 0x4201a940 (LWP 4668)):
0 0x0000003722430285 in raise () from /lib64/libc.so.6
1 0x0000003722431d30 in abort () from /lib64/libc.so.6
2 0x0000003722429706 in __assert_fail () from /lib64/libc.so.6
3 0x00002aaaab161b40 in delta_append_val (bat=0x1d14e310, i=0x1e2e3350) at bat_storage.c:327
4 0x00002aaaab161dbc in append_col (tr=0x1e0e3ed0, c=0x1e61f150, i=0x1e2e3350, tpe=11) at bat_storage.c:351
5 0x00002aaaab08389c in mvc_append_wrap (cntxt=0x1cd07768, mb=0x1d31f040, stk=0x1e2e31c0, pci=0x1e063620) at sql.mx:3261
6 0x00002b502b61e515 in runMALsequence (cntxt=0x1cd07768, mb=0x1d31f040, startpc=1, stoppc=0, stk=0x1e2e31c0, env=0x0, pcicaller=0x0)
at mal_interpreter.c:642
7 0x00002b502b61da4e in callMAL (cntxt=0x1cd07768, mb=0x1d31f040, env=0x42019e48, argv=0x1cddd9a0, debug=0 '\000') at mal_interpreter.c:469
8 0x00002aaaab04f666 in SQLexecutePrepared (c=0x1cd07768, be=0x1ce5a000, q=0x1df76380) at sql_scenario.c:1779
9 0x00002aaaab04f9d6 in SQLengineIntern (c=0x1cd07768, be=0x1ce5a000) at sql_scenario.c:1846
10 0x00002aaaab04fe98 in SQLengine (c=0x1cd07768) at sql_scenario.c:1947
11 0x00002b502b646ad2 in runPhase (c=0x1cd07768, phase=4) at mal_scenario.c:522
12 0x00002b502b646c90 in runScenarioBody (c=0x1cd07768) at mal_scenario.c:566
13 0x00002b502b646d79 in runScenario (c=0x1cd07768) at mal_scenario.c:586
14 0x00002b502b647c02 in MSserveClient (dummy=0x1cd07768) at mal_session.c:431
15 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
16 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 7 (Thread 0x40cac940 (LWP 4190)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b502bd6427f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002b502bc913b2 in GDKvmtrim (limit=0x2b502c3a8358) at gdk_utils.c:918
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 6 (Thread 0x41e19940 (LWP 4191)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b502bd6427f in MT_sleep_ms (ms=1000) at gdk_posix.c:1003
2 0x00002b502b638692 in profilerHeartbeat (dummy=0x0) at mal_profiler.c:1431
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 5 (Thread 0x40a0a940 (LWP 4192)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b502b7d37e1 in SERVERlistenThread (Sock=0x1e010e30) at mal_mapi.c:209
2 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
3 0x00000037224d3c1d in clone () from /lib64/libc.so.6
---Type <return> to continue, or q <return> to quit---
Thread 4 (Thread 0x417e4940 (LWP 4193)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b502bd6427f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002aaaab152a90 in store_manager () at store.c:1533
3 0x00002aaaab0ea222 in mvc_logmanager () at sql_mvc.c:149
4 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
5 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x41bb3940 (LWP 4227)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002b502b6213cd in q_dequeue (q=0x1ce63820) at mal_dataflow.c:196
2 0x00002b502b6215d1 in DFLOWworker (t=0x2b502bb05f40) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x4221b940 (LWP 4228)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002b502b6213cd in q_dequeue (q=0x1ce63820) at mal_dataflow.c:196
2 0x00002b502b6215d1 in DFLOWworker (t=0x2b502bb05f48) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x2b502caf0f30 (LWP 4189)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b502bd6427f in MT_sleep_ms (ms=5000) at gdk_posix.c:1003
2 0x0000000000403596 in main (argc=20, av=0x7ffff9ec17e8) at mserver5.c:626
## Comment 18499
Date: 2013-02-18 20:03:17 +0100
From: @drstmane
Ashish,
in your debugger, once the assertion happens, could you please go to the very thread that it happened in (thread 40 in your latest trace), there "up" to the function where the assertion was triggered ("delta_append_val()"), execute the following print commands, and share their output:
p c
p *c
p *c->U
p *c->P
p bat
p *bat
p bat->ibase
Thanks!
## Comment 18500
Date: 2013-02-18 20:12:04 +0100
From: Ashish Kumar Singh <<ashishk>>
HI Neil,
That session got closed , and a new crash is showing different log: Do you want me to run same commands and share output?
0 0x0000003722430285 in raise () from /lib64/libc.so.6
1 0x0000003722431d30 in abort () from /lib64/libc.so.6
2 0x0000003722429706 in __assert_fail () from /lib64/libc.so.6
3 0x00002aaaab16516f in tr_update_delta (tr=0x1446fb30, obat=0x13ef8410,
cbat=0x13eba370, snapshot_minsize=1024) at bat_storage.c:1441
4 0x00002aaaab165d0f in update_table (tr=0x1446fb30, ft=0x14945ef0,
tt=0x1444c3c0) at bat_storage.c:1563
5 0x00002aaaab1567dd in rollforward_update_table (tr=0x1446fb30,
ft=0x14945ef0, tt=0x1444c3c0, mode=3) at store.c:2671
6 0x00002aaaab155789 in rollforward_changeset_updates (tr=0x1446fb30,
fs=0x14932f00, ts=0x14095200, b=0x140951e0,
rollforward_updates=0x2aaaab15644d <rollforward_update_table>,
rollforward_creates=0x2aaaab155d62 <rollforward_create_table>,
rollforward_deletes=0x2aaaab156248 <rollforward_drop_table>,
fd=0x2aaaab1568b7 <conditional_table_dup>, mode=3) at store.c:2284
7 0x00002aaaab156c1f in rollforward_update_schema (tr=0x1446fb30,
fs=0x14932ee0, ts=0x140951e0, mode=3) at store.c:2746
8 0x00002aaaab155789 in rollforward_changeset_updates (tr=0x1446fb30,
fs=0x1446fb60, ts=0x14151360, b=0x14151330,
rollforward_updates=0x2aaaab1569a8 <rollforward_update_schema>,
rollforward_creates=0x2aaaab156403 <rollforward_create_schema>,
---Type <return> to continue, or q <return> to quit---
rollforward_deletes=0x2aaaab156397 <rollforward_drop_schema>,
fd=0x2aaaab154ebd <schema_dup>, mode=3) at store.c:2284
9 0x00002aaaab156dc1 in rollforward_trans (tr=0x1446fb30, mode=3)
at store.c:2768
10 0x00002aaaab1581f4 in sql_trans_commit (tr=0x1446fb30) at store.c:3170
11 0x00002aaaab0ea742 in mvc_commit (m=0x143a7190, chain=0, name=0x0)
at sql_mvc.c:267
12 0x00002aaaab04d0da in SQLautocommit (c=0x12dd90d0, m=0x143a7190)
at sql_scenario.c:1116
13 0x00002aaaab04d314 in SQLreader (c=0x12dd90d0) at sql_scenario.c:1204
14 0x00002b2a4729bad2 in runPhase (c=0x12dd90d0, phase=0)
at mal_scenario.c:522
15 0x00002b2a4729bbaf in runScenarioBody (c=0x12dd90d0) at mal_scenario.c:552
16 0x00002b2a4729bd79 in runScenario (c=0x12dd90d0) at mal_scenario.c:586
17 0x00002b2a4729cc02 in MSserveClient (dummy=0x12dd90d0) at mal_session.c:431
18 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
19 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 56 (Thread 0x40cea940 (LWP 7012)):
0 0x0000003722c0d9eb in read () from /lib64/libpthread.so.0
1 0x00002b2a48334073 in socket_read (s=0x146dea00, buf=0x40ce9ebe,
elmsize=2, cnt=1) at stream.c:1455
2 0x00002b2a483369f7 in mnstr_readSht (s=0x146dea00, val=0x40ce9ebe)
---Type <return> to continue, or q <return> to quit---
at stream.c:2867
3 0x00002b2a48335ff9 in bs_read (ss=0x1452eb20, buf=0x1424dbd0, elmsize=1,
cnt=1048320) at stream.c:2556
4 0x00002b2a48337779 in bstream_read (s=0x143a9960, size=1048320)
at stream.c:3122
5 0x00002b2a48337aac in bstream_next (s=0x143a9960) at stream.c:3189
6 0x00002aaaab04d3b5 in SQLreader (c=0x12dd8de8) at sql_scenario.c:1217
7 0x00002b2a4729bad2 in runPhase (c=0x12dd8de8, phase=0)
at mal_scenario.c:522
8 0x00002b2a4729bbaf in runScenarioBody (c=0x12dd8de8) at mal_scenario.c:552
9 0x00002b2a4729bd79 in runScenario (c=0x12dd8de8) at mal_scenario.c:586
10 0x00002b2a4729cc02 in MSserveClient (dummy=0x12dd8de8) at mal_session.c:431
11 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
12 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 7 (Thread 0x4128d940 (LWP 6804)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b2a479b927f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002b2a478e63b2 in GDKvmtrim (limit=0x2b2a47ffd358) at gdk_utils.c:918
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 6 (Thread 0x41ad0940 (LWP 6805)):
---Type <return> to continue, or q <return> to quit---
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b2a479b927f in MT_sleep_ms (ms=1000) at gdk_posix.c:1003
2 0x00002b2a4728d692 in profilerHeartbeat (dummy=0x0) at mal_profiler.c:1431
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 5 (Thread 0x41eed940 (LWP 6806)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b2a474287e1 in SERVERlistenThread (Sock=0x140e2030)
at mal_mapi.c:209
2 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
3 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 4 (Thread 0x4148e940 (LWP 6807)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b2a479b927f in MT_sleep_ms (ms=50) at gdk_posix.c:1003
2 0x00002aaaab152a90 in store_manager () at store.c:1533
3 0x00002aaaab0ea222 in mvc_logmanager () at sql_mvc.c:149
4 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
5 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x408e8940 (LWP 6819)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
---Type <return> to continue, or q <return> to quit---
1 0x00002b2a472763cd in q_dequeue (q=0x143992d0) at mal_dataflow.c:196
2 0x00002b2a472765d1 in DFLOWworker (t=0x2b2a4775af40) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x40ae9940 (LWP 6820)):
0 0x0000003722c0cd91 in sem_wait () from /lib64/libpthread.so.0
1 0x00002b2a472763cd in q_dequeue (q=0x143992d0) at mal_dataflow.c:196
2 0x00002b2a472765d1 in DFLOWworker (t=0x2b2a4775af48) at mal_dataflow.c:257
3 0x0000003722c0677d in start_thread () from /lib64/libpthread.so.0
4 0x00000037224d3c1d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x2b2a48745f30 (LWP 6803)):
0 0x00000037224ccdb2 in select () from /lib64/libc.so.6
1 0x00002b2a479b927f in MT_sleep_ms (ms=5000) at gdk_posix.c:1003
2 0x0000000000403596 in main (argc=20, av=0x7fff8c0b68c8) at mserver5.c:626
## Comment 18501
Date: 2013-02-18 20:15:41 +0100
From: @njnes
No need now. Lets first have a look at the java code you have..
## Comment 18502
Date: 2013-02-18 20:17:01 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 182
Java Test Case Sources
Make Changes for DB connections in ConfigurationDBConnection.Java Class
Create Schema using schema file
Run com.altair.test.MonetDBLoadTestBasedOnQueueAndQueryFrequently class
> Attached file: [TestCaseSources.zip](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3233_TestCaseSources.zip_182) (application/x-zip-compressed, 470563 bytes)
> Description: Java Test Case Sources
## Comment 18503
Date: 2013-02-18 20:17:25 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 183
Schema File
> Attached file: [schema.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3233_schema.txt_183) (text/plain, 337 bytes)
> Description: Schema File
## Comment 18504
Date: 2013-02-18 20:18:10 +0100
From: Ashish Kumar Singh <<ashishk>>
(In reply to comment 26)
> No need now. Lets first have a look at the java code you have..
Shared Let me know if you need an online skype meeting to get you up to speed with this.
## Comment 18522
Date: 2013-02-19 13:45:45 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi,
Any thoughts on this issue? Work arounds / possible time for fixes?
Regards,
Ashish
## Comment 18528
Date: 2013-02-20 11:08:51 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi team,
One of our appplication release is held waiting for this issue and we are pressed on time, we are ready to try out any work arounds if you can suggest which can help avoiding this issue as an intermediate step.
Any suggestions ill be helpful! Thanks in advance!
Regards,
Ashish
## Comment 18529
Date: 2013-02-20 11:10:24 +0100
From: Ashish Kumar Singh <<ashishk>>
Corrected typo below
(In reply to comment 31)
> Hi team,
>
> One of our appplication release is held waiting for this issue and we are
> pressed on time, we are ready to try out any work arounds if you can suggest
> which can help avoiding this issue as an intermediate step.
>
> Any suggestions will be helpful! Thanks in advance!
>
>
> Regards,
> Ashish
## Comment 18530
Date: 2013-02-20 12:04:27 +0100
From: @mlkersten
Dear Ashish
I remind you that you are relying on the MonetDB as open-source project
without any commercial commitment imposed upon us. We deal with issues
as best as we can. The risks for deploying the code base rest at the user
as clearly identified in its license.
http://www.monetdb.org/Legal/MonetDBLicense
Thank you for reporting the issues. If fixes are required they will appear
regular bug-fix releases.
regards, Martin Kersten
## Comment 18531
Date: 2013-02-20 14:27:23 +0100
From: Ashish Kumar Singh <<ashishk>>
Dear Martin,
I understand it. Your technology was surely very useful for us!
Regarding this bug I was interested to see if we can work around this particular issue or not?
Regards,
Ashish
## Comment 18532
Date: 2013-02-21 08:28:15 +0100
From: Ashish Kumar Singh <<ashishk>>
Dear Niels and all,
I ran a slightly modified tests today which has not crashed so far in 10 hours, description is below:
1. removed use of sequences from schema in the table set default value for roe_id to 1, result is no crash.
2. removed use of sequences from schema in the table set default value for roe_id to 1, while inserting data I am using my java code to create an auto increment value and use it in insert statement,result no crash so far.
Observations:
Earlier we use to get crash with in 10-20 minutes, now for more than 10 hours no crash.
Insert performance seems to increase by avoiding sequences.
I hope this info might be useful in digging down the issue. Please share your thoughts, findings , suggestions on the same.
Regards,
Ashish
## Comment 18533
Date: 2013-02-21 12:47:30 +0100
From: @njnes
Changeset [ba7ad0186586](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ba7ad0186586) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ba7ad0186586](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ba7ad0186586)
Changeset description:
way more stricked table_validate. This will heart concurrency but solves
the continues story with inconsistent dbs.
See also bug #3233
## Comment 18540
Date: 2013-02-22 08:10:35 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi Niels,
Fix works great, straight 10 hours no crash so far. Will it be possible to have a February 2013 SP1 with this fix any time soon, I think it's important as it was leading to invalid database state/corruption?
Regards,
Ashish
## Comment 18565
Date: 2013-02-25 16:12:41 +0100
From: @sjoerdmullender
I assume that the bug is now fixed.
I hope to be able to create an SP1 this week, but it depends on some other bugs that I still want to see fixed.
## Comment 18591
Date: 2013-03-07 12:41:22 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| getting a crash of server with segmentation fault on SLES 11 64 SP2 | https://api.github.com/repos/MonetDB/MonetDB/issues/3233/comments | 0 | 2020-11-30T12:17:15Z | 2024-06-27T11:58:57Z | https://github.com/MonetDB/MonetDB/issues/3233 | 753,430,190 | 3,233 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-12 15:14:40 +0100
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-09-30 11:22:58 +0200
## Comment 18466
Date: 2013-02-12 15:14:40 +0100
From: Alfred Nordman <<alfred.nordman>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
Build Identifier:
Results are seemed to be offseted by 1 year
DATE weekofyear ->ISO8601 weekofyear-> MonetDb
1-1-1986 1 1
1-1-1987 1 53
1-1-1988 53 52
1-1-1989 52 1
1-1-1990 1 1
Reproducible: Always
### Steps to Reproduce:
1. I used the following script as a text file
create table weekofyear_test (d date);
insert into weekofyear_test values ('1986-JAN-01');
insert into weekofyear_test values ('1987-JAN-01');
insert into weekofyear_test values ('1988-JAN-01');
insert into weekofyear_test values ('1989-JAN-01');
insert into weekofyear_test values ('1990-JAN-01');
select d, weekofyear(d) from weekofyear_test;
drop table weekofyear_test;
### Actual Results:
d weekofyear
1-1-1986 1
1-1-1987 53
1-1-1988 52
1-1-1989 1
1-1-1990 1
### Expected Results:
d weekofyear
1-1-1986 1
1-1-1987 1
1-1-1988 53
1-1-1989 52
1-1-1990 1
## Comment 19070
Date: 2013-08-25 10:38:28 +0200
From: @njnes
Both dayofweek and weekofyear used sunday to saturday weeks, while iso wants the week to start on a monday.
## Comment 19073
Date: 2013-08-25 16:23:37 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0620e9df2003](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0620e9df2003) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0620e9df2003](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0620e9df2003)
Changeset description:
fixed bug #3232, use dayofweek, starting at Monday
fixed bug #2962, convert timestamp with time zone to local time zone, when used as input to the extract functions.
fixed bug #2781, use correct time zone in mclient
## Comment 19216
Date: 2013-09-30 11:22:58 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [fdd09b97b50b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fdd09b97b50b) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fdd09b97b50b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fdd09b97b50b)
Changeset description:
Properly extract week number from a given date.
Note that if Jan 1 is not on a Monday, it is in the same week as Dec
31 of the year before, and this can be either week 1 (if Jan 1 is on a
Tuesday, Wednesday, or Thursday) of week 52/53 (if it is on a Friday,
Saturday, or Sunday).
This fixes bug #3232 properly.
| The function weekofyear returns results not according to the iso 8601 standard | https://api.github.com/repos/MonetDB/MonetDB/issues/3232/comments | 0 | 2020-11-30T12:17:12Z | 2024-06-27T11:58:56Z | https://github.com/MonetDB/MonetDB/issues/3232 | 753,430,153 | 3,232 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-10 13:35:54 +0100
From: @drstmane
To: clients devs <<bugs-clients>>
Version: 11.15.1 (Feb2013)
CC: @gijzelaerr
Last updated: 2013-02-11 23:13:46 +0100
## Comment 18459
Date: 2013-02-10 13:35:54 +0100
From: @drstmane
Gijs,
since your recent checkins, while working fine with Oct2012, cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=46883:6b751dfe0d7f&order=platform,arch,compiler
test sql/test/mapi/Tests/python3_test_monetdb_sql.SQL.sh fails with Feb2013 (& default); cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=46893:1862b6d69202&order=platform,arch,compiler
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46893:1862b6d69202&target=GNU-Fedora-x86_64-dist&module=sql&test=sql%2Ftest%2Fmapi%2Fpython3_test_monetdb_sql&which=err
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46893:1862b6d69202/GNU-Fedora-x86_64-dist/sql/mTests/sql%2Ftest%2Fmapi%2Fpython3_test_monetdb_sql
It seems the test is now producing extra output that is did not produce before, and that also the respective python2 test does no produce.
Is this intended or a bug/accident?
See also the differences between
diff -rduBbw clients/python[23]
with the Oct2012 branch,
vs.
diff -rduBbw clients/python[23]
with the Feb2013 branch.
## Comment 18460
Date: 2013-02-11 10:22:16 +0100
From: @sjoerdmullender
Changeset [c3d7dc071a15](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c3d7dc071a15) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c3d7dc071a15](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c3d7dc071a15)
Changeset description:
Remove duplicate code. This fixes bug #3231.
## Comment 18461
Date: 2013-02-11 10:44:30 +0100
From: @gijzelaerr
A while ago I did a cleanup in the default branch of the python3 version to get the differences between the python2 and python3 version to a minimum.
I think the merge from the Oct2012 to the Feb2013 failed for the runtests.py file, since I didn't commit the duplicate code as far as I can tell.
But this issue has been solved now right?
## Comment 18462
Date: 2013-02-11 14:41:40 +0100
From: @sjoerdmullender
(In reply to comment 2)
> A while ago I did a cleanup in the default branch of the python3 version to get
> the differences between the python2 and python3 version to a minimum.
There were indeed few differences. There are fewer still now.
> I think the merge from the Oct2012 to the Feb2013 failed for the runtests.py
> file, since I didn't commit the duplicate code as far as I can tell.
Indeed, the merge had gone wrong.
> But this issue has been solved now right?
Tonight's testing will tell for sure, but I fully expect it to be resolved.
## Comment 18463
Date: 2013-02-11 17:08:13 +0100
From: @gijzelaerr
On my system runtests.py for python2 and python3 complete without errors. There are some issues with the tests for the new control module I see now, but probably you didn't add these tests to the build system?
Since the control module can only operate on a remote socket (not file socket yet) a passphrase and control=yes need to be set for a test database. Is this the case? if so i'll update the control module tests (when i find some time) so you can add them to your test run (if you want).
## Comment 18464
Date: 2013-02-11 23:13:46 +0100
From: @drstmane
Nightly testing confirm the fix(es). Thanks!
Closing.
(The discussion about the control module tests should continued elsewhere, e.g., by direct email, on the mailing lists, or in a separate feature request.)
| Test python3_test_monetdb_sql failing with Feb2013 & default | https://api.github.com/repos/MonetDB/MonetDB/issues/3231/comments | 0 | 2020-11-30T12:17:10Z | 2024-06-27T11:58:55Z | https://github.com/MonetDB/MonetDB/issues/3231 | 753,430,127 | 3,231 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-09 17:26:57 +0100
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: @njnes
Last updated: 2013-03-07 12:41:23 +0100
## Comment 18456
Date: 2013-02-09 17:26:57 +0100
From: @bartscheers
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:16.0) Gecko/20100101 Firefox/16.0
Build Identifier:
A user having only select privileges on a table is allowed to do so when a sql function performs the insert into the table.
Reproducible: Always
### Steps to Reproduce:
1. ./setup.sh
2. mclient -dgrantupd < setup.sql
3. mclient -dgrantupd -ubart < insertbug.sql
4. mclient -dgrantupd -ubart < updatebug.sql
5. mclient -dgrantupd -ubart < deletebug.sql
### Actual Results:
row inserted, updated, deleted
### Expected Results:
A insufficient privileges message for all cases, and no execution of function
## Comment 18457
Date: 2013-02-09 17:32:58 +0100
From: @bartscheers
Created attachment 178
contains the necessary test files
> Attached file: [grantfunctionbug.tar](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3230_grantfunctionbug.tar_178) (text/plain, 10240 bytes)
> Description: contains the necessary test files
## Comment 18471
Date: 2013-02-13 16:00:33 +0100
From: @njnes
Changeset [fffd420f1ee8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fffd420f1ee8) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fffd420f1ee8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fffd420f1ee8)
Changeset description:
fixes and test added for bug #3230
## Comment 18472
Date: 2013-02-13 16:02:55 +0100
From: @njnes
fixed. We now check user rights also in recursive sql.
This means tables under views are checked for user rights properly (we don't support materialized views)
## Comment 18592
Date: 2013-03-07 12:41:23 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| GRANT SELECT priveleges not set in SQL FUNCTIONs | https://api.github.com/repos/MonetDB/MonetDB/issues/3230/comments | 0 | 2020-11-30T12:17:07Z | 2024-06-27T11:58:54Z | https://github.com/MonetDB/MonetDB/issues/3230 | 753,430,102 | 3,230 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-07 11:37:11 +0100
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: @njnes
Last updated: 2013-03-07 12:41:22 +0100
## Comment 18455
Date: 2013-02-07 11:37:11 +0100
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
When I create a new user and want to grant her only select access to a table, she can still update the table.
Reproducible: Always
### Steps to Reproduce:
1.monetdb create grantupd; monetdb start grantupd; monetdb release grantupd;
2.mclient -d grantupd
3.sql>create table version (name varchar(10), i int);insert into version (name,i) values ('test1', 1);
4.sql>CREATE USER "bart" WITH PASSWORD 'bart' NAME 'Bart Simpson' SCHEMA "sys";
5.sql>GRANT SELECT ON TABLE version TO bart;
6.sql>\q
7.mclient -d grantupd -ubart
sql>select * from version;
+-------+------+
| name | i |
+=======+======+
| test1 | 1 |
+-------+------+
1 tuple (1.631ms)
sql>delete from version;
DELETE FROM: insufficient privileges for user 'bart' to delete from table 'version'
sql>insert into version (name,i) values ('test3', 3);
INSERT INTO: insufficient privileges for user 'bart' to insert into table 'version'
All correct, but:
sql>update version set i = 2;
1 affected row (32.151ms)
sql>select * from version;
+-------+------+
| name | i |
+=======+======+
| test1 | 2 |
+-------+------+
1 tuple (1.364ms)
### Actual Results:
UPDATE GRANT neglected.
### Expected Results:
insufficient privileges
This is also incorrect when working in another than sys schema.
## Comment 18468
Date: 2013-02-13 13:37:56 +0100
From: @njnes
Changeset [febda30627eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=febda30627eb) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=febda30627eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=febda30627eb)
Changeset description:
add test(s) for bug #3229
## Comment 18469
Date: 2013-02-13 13:39:01 +0100
From: @njnes
proper checks were missing...
## Comment 18589
Date: 2013-03-07 12:41:22 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| GRANT does not work for UPDATE | https://api.github.com/repos/MonetDB/MonetDB/issues/3229/comments | 0 | 2020-11-30T12:17:04Z | 2024-06-27T11:58:53Z | https://github.com/MonetDB/MonetDB/issues/3229 | 753,430,050 | 3,229 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-02-05 12:21:40 +0100
From: Pete Hollobon <<pete>>
To: clients devs <<bugs-clients>>
Version: 11.15.1 (Feb2013)
CC: pete
Last updated: 2013-03-07 12:41:21 +0100
## Comment 18454
Date: 2013-02-05 12:21:40 +0100
From: Pete Hollobon <<pete>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.30 (KHTML, like Gecko) Chrome/26.0.1403.0 Safari/537.30
Build Identifier:
At present, the MonetDB Python client sleeps for one second and loops waiting for data if the length of the result from the socket communicating with the server is 0. However, a zero-length result from socket.recv means the server has closed the connection [1]. This means the client will hang if the server closes the socket for any reason.
In particular this happens when using VirtualBox and port-forwarding to run an OS running MonetDB, where MonetDB is not started. The connection is accepted by VirtualBox before it attempts to connect to the server process inside the VM. It's closed if there is no listening socket to connect to, causing the Python client to sit in this loop without timing out.
Here are patches for the Python 2 and 3 modules, which cause an exception to be thrown instead, which I think is the appropriate behaviour.
--- a/clients/python3/monetdb/mapi.py Thu Jan 31 15:05:41 2013 +0100
+++ b/clients/python3/monetdb/mapi.py Tue Feb 05 11:11:17 2013 +0000
@@ -237,7 +237,7 @@
while count > 0:
recv = self.socket.recv(count)
if len(recv) == 0:
- time.sleep(1)
+ raise OperationalError("Server closed connection")
logger.debug("II: package size: %i payload: %s" % (len(recv), recv))
count -= len(recv)
result.write(recv)
--- a/clients/python2/monetdb/mapi.py Tue Feb 05 11:11:17 2013 +0000
+++ b/clients/python2/monetdb/mapi.py Tue Feb 05 11:19:46 2013 +0000
@@ -235,7 +235,7 @@
try:
recv = self.socket.recv(count)
if len(recv) == 0:
- time.sleep(1)
+ raise OperationalError("Server closed connection")
logger.debug("II: package size: %i payload: %s" % (len(recv), recv))
except socket.error, error:
raise OperationalError(error[1])
[1] man recv
RETURN VALUE
... The return value will be 0 when the peer has performed an orderly shutdown.
Reproducible: Always
## Comment 18570
Date: 2013-02-26 14:36:49 +0100
From: @sjoerdmullender
Changeset [c22d45d3ea7e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c22d45d3ea7e) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c22d45d3ea7e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c22d45d3ea7e)
Changeset description:
Throw exception when server unexpectedly closes connection.
This fixes bug #3228. Thanks to Pete Hollobon.
## Comment 18571
Date: 2013-02-26 14:41:20 +0100
From: @sjoerdmullender
I'm not sure how to test this, so no test provided.
## Comment 18588
Date: 2013-03-07 12:41:21 +0100
From: @sjoerdmullender
Feb2013-SP1 has been released.
| Python client - mapi.Connection.__getbyes should throw exception when 0 bytes received from socket | https://api.github.com/repos/MonetDB/MonetDB/issues/3228/comments | 0 | 2020-11-30T12:17:01Z | 2024-06-27T11:58:52Z | https://github.com/MonetDB/MonetDB/issues/3228 | 753,430,016 | 3,228 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-29 11:32:29 +0100
From: Vasileios Trigonakis <<vasileios.trigonakis>>
To: GDK devs <<bugs-common>>
Version: 11.13.9 (Oct2012-SP3)
CC: @drstmane
Last updated: 2013-02-19 13:17:55 +0100
## Comment 18447
Date: 2013-01-29 11:32:29 +0100
From: Vasileios Trigonakis <<vasileios.trigonakis>>
User-Agent: Opera/9.80 (X11; Linux x86_64; Edition Linux Mint) Presto/2.12.388 Version/12.12
Build Identifier:
the main() in the tools/mserver/mserver5.c makes a call on GDK_malloc() to allocate the monet_script. The GDK_malloc() calls the GDKmallocmax(), which calls the heapinc(). heapinc() is protected by a lock (mbyteslock,) that is not initialized at this time.
Reproducible: Always
### Steps to Reproduce:
1. configure with enable-optimize
2. execute the mserver5
### Actual Results:
the actual and the expected results did not defer
~/monetdb/MonetDB-11.13.9 $ mserver5 --version
MonetDB 5 server v11.13.9 "Oct2012-SP3" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 125.8GiB available memory, 48 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.12)
openssl: OpenSSL 1.0.1 14 Mar 2012 (compiled with OpenSSL 1.0.1 14 Mar 2012)
libxml2: 2.7.8 (compiled with 2.7.8)
Compiled by: trigonak@lpd48core (x86_64-unknown-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 18448
Date: 2013-01-29 11:41:10 +0100
From: @drstmane
Your mserver5 --version output suggests you're using the Oct2012-SP3 release, not the Feb2013 release candidate branch ...
## Comment 18449
Date: 2013-01-29 11:46:07 +0100
From: @sjoerdmullender
Changeset [2a441a22195c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2a441a22195c) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a441a22195c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a441a22195c)
Changeset description:
Use malloc/free instead of GDKmalloc/GDKfree for monetscript.
The malloc is called before the call to monet_init which initializes
the locks used by GDKmalloc.
This fixes bug #3227.
## Comment 18506
Date: 2013-02-19 13:17:55 +0100
From: @sjoerdmullender
Feb2013 has been released.
| MT_set_lock() call on an non-initialized lock | https://api.github.com/repos/MonetDB/MonetDB/issues/3227/comments | 0 | 2020-11-30T12:16:59Z | 2024-06-27T11:58:52Z | https://github.com/MonetDB/MonetDB/issues/3227 | 753,429,989 | 3,227 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-28 08:28:46 +0100
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Last updated: 2013-01-30 08:34:45 +0100
## Comment 18437
Date: 2013-01-28 08:28:46 +0100
From: @drstmane
Only when assertions are enabled, tests
monetdb5/mal/Tests/tst1012.mal
monetdb5/mal/Tests/tst1014.mal
monetdb5/mal/Tests/tst601.mal
appear to hang since recent (Friday January 25 2013) checkins; cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=46771:f024941411ed&order=platform,arch,compiler
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46771:f024941411ed&target=GNU-Fedora-x86_64-propcheck-assert&module=monetdb5&test=monetdb5%2Fmal%2Ftst1012&which=err
http://monetdb.cwi.nl/testweb/web/testchange.php?test=46771:f024941411ed/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/monetdb5%2Fmal%2Ftst1012
http://monetdb.cwi.nl/testweb/web/commits.php?serial=46753:295a2a015d53
## Comment 18439
Date: 2013-01-29 10:06:31 +0100
From: @sjoerdmullender
Changeset [1c20086be294](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1c20086be294) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1c20086be294](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1c20086be294)
Changeset description:
After a lock has been destroyed, it may not be used anymore.
In other words, the lock was destroyed prematurely.
This fixed bug #3226 once the fix is propagated to the default branch.
## Comment 18451
Date: 2013-01-30 08:34:45 +0100
From: @drstmane
Nightly testing confirms fix. Closing.
| M5/mal tests tst1012, tst1014, tst601 hang with assertions enabled since recent (Fri, Jan 25 2013) checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/3226/comments | 0 | 2020-11-30T12:16:57Z | 2024-06-27T11:58:51Z | https://github.com/MonetDB/MonetDB/issues/3226 | 753,429,951 | 3,226 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-20 12:16:57 +0100
From: Christian Braun <<hcb>>
To: SQL devs <<bugs-sql>>
Version: 11.13.7 (Oct2012-SP2)
CC: ashishk, hcb, @njnes, @drstmane
Last updated: 2013-02-19 13:20:03 +0100
## Comment 18348
Date: 2013-01-20 12:16:57 +0100
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
Hello,
when running:
select "eId", min("timeInsert"), max("timeInsert"), count(*) from my.v where "uId" = 312459 group by "eId";
on the attached data set, mserver segfaults. With other data sets it works fine.
Regards,
Christian.
Reproducible: Always
## Comment 18349
Date: 2013-01-20 12:17:26 +0100
From: Christian Braun <<hcb>>
Created attachment 172
mclient session
> Attached file: [monetdb.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3225_monetdb.txt_172) (text/plain, 4875 bytes)
> Description: mclient session
## Comment 18350
Date: 2013-01-20 12:19:01 +0100
From: Christian Braun <<hcb>>
Created attachment 173
test data
> Attached file: [data.gz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3225_data.gz_173) (application/x-gzip, 55706 bytes)
> Description: test data
## Comment 18351
Date: 2013-01-20 18:24:13 +0100
From: @drstmane
Christian's logs suggest he's using Oct2012-SP2.
## Comment 18352
Date: 2013-01-20 18:31:24 +0100
From: @drstmane
Also segfaults with Oct2012-SP3 (most probably in aggregation code).
Appears to work fine with Feb2013 candidate branch from Mercurial (with complete re-implementation of grouping & aggregation code).
## Comment 18353
Date: 2013-01-21 01:36:16 +0100
From: @drstmane
Changeset [dfe24d3e7d6b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dfe24d3e7d6b) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=dfe24d3e7d6b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=dfe24d3e7d6b)
Changeset description:
fixed bug #3225: since changeset [822e78b1baa5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=822e78b1baa5) we need to lookup on e, not on bn
This must NOT be propagated.
## Comment 18354
Date: 2013-01-21 01:38:31 +0100
From: @drstmane
Changeset [40bc241696a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=40bc241696a1) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=40bc241696a1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=40bc241696a1)
Changeset description:
added test for bug #3225
## Comment 18355
Date: 2013-01-21 01:56:25 +0100
From: @drstmane
Thanks for the detailed bug report!
Should be fixed, now, in the Oct2012 branch in Mercurial (and was already working in the Feb2013 branch).
Chances are, though, that we are neither going to re-build the (not yet released) Oct2012-SP3 (as available for testing from http://dev.monetdb.org/downloads/testing/), nor going to release an Oct2012-SP4 before the upcoming Feb2013 release.
## Comment 18518
Date: 2013-02-19 13:20:03 +0100
From: @sjoerdmullender
Feb2013 has been released.
| mserver segfault on select | https://api.github.com/repos/MonetDB/MonetDB/issues/3225/comments | 0 | 2020-11-30T12:16:54Z | 2024-06-27T11:58:50Z | https://github.com/MonetDB/MonetDB/issues/3225 | 753,429,917 | 3,225 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-16 11:19:49 +0100
From: Ashish Kumar Singh <<ashishk>>
To: Merovingian devs <<bugs-merovingian>>
Version: 11.15.1 (Feb2013)
CC: ashishk
Last updated: 2013-02-25 16:07:51 +0100
## Comment 18344
Date: 2013-01-16 11:19:49 +0100
From: Ashish Kumar Singh <<ashishk>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17
Build Identifier:
Need info : How to enable rolling log file in monetdb, is it supported?
Reproducible: Always
## Comment 18440
Date: 2013-01-29 10:11:58 +0100
From: @sjoerdmullender
What exactly do you mean?
Do you mean, how does the write-ahead log get rolled into the database?
This log is rolled into the database when the server is quiescent, or when the server is started up.
| Need info : How to enable rolling log file in monetdb | https://api.github.com/repos/MonetDB/MonetDB/issues/3224/comments | 0 | 2020-11-30T12:16:51Z | 2024-06-27T11:58:49Z | https://github.com/MonetDB/MonetDB/issues/3224 | 753,429,881 | 3,224 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-16 09:54:37 +0100
From: Ashish Kumar Singh <<ashishk>>
To: GDK devs <<bugs-common>>
Version: 11.15.1 (Feb2013)
CC: ashishk
Last updated: 2013-01-16 11:03:47 +0100
## Comment 18342
Date: 2013-01-16 09:54:37 +0100
From: Ashish Kumar Singh <<ashishk>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17
Build Identifier:
I tried pointing to October 2012 SP3 release candidate from my working application on top of October 2012 SP1 build.
With nclient set to 64 it started showing me following error:
maximum concurrent client limit reached (193), please try again later
With nclient =200 it started showing me below error
maximum concurrent client limit reached (601), please try again later
at com.altair.pbsworks.parser.datamodel.ParsedRescourceConatinerEventResourceOccupancyDetails.convertValues(ParsedRescourceConatinerEventResourceOccupancyDetails.java:384)
at com.altair.pbsworks.parser.app.RescourceConatinerEventResourceOccupancyDetailsPopulatorThread.run(RescourceConatinerEventResourceOccupancyDetailsPopulatorThread.java:44)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: nl.cwi.monetdb.mcl.MCLException: maximum concurrent client limit reached (601), please try again later
at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:308)
at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:395)
at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:248)
at nl.cwi.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:232)
... 612 more
Need information on if something got changed in this particular area?
Regards,
Ashish
Reproducible: Always
## Comment 18343
Date: 2013-01-16 11:03:47 +0100
From: Ashish Kumar Singh <<ashishk>>
Not an issue with monetdb, please ignore it.
| Discrepency in maximum number of client connections in latest release candidate | https://api.github.com/repos/MonetDB/MonetDB/issues/3223/comments | 1 | 2020-11-30T12:16:49Z | 2024-06-28T07:23:18Z | https://github.com/MonetDB/MonetDB/issues/3223 | 753,429,849 | 3,223 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-15 15:15:18 +0100
From: Ashish Kumar Singh <<ashishk>>
To: SQL devs <<bugs-sql>>
Version: 11.13.5 (Oct2012-SP1)
CC: hcb, @njnes, @drstmane
Last updated: 2013-02-19 13:23:51 +0100
## Comment 18334
Date: 2013-01-15 15:15:18 +0100
From: Ashish Kumar Singh <<ashishk>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17
Build Identifier:
We are facing one strange behavior with Monetdb. We have a simple table called test with following structure:
CREATE SEQUENCE "testtable_seq" as bigint START WITH 1;
CREATE TABLE testtable
(dim_id bigint DEFAULT NEXT VALUE FOR "testtable_seq",
dim_type varchar(100) NOT NULL,
dim_value varchar(100) NOT NULL,
CONSTRAINT unique_dimension UNIQUE(dim_type,dim_value) ,
CONSTRAINT pk_testtable PRIMARY KEY (dim_id));
We have a program which reads and writes to this table along with other tables using JDBC.
We are facing below problems interminently:
1. When we query back data from this table with query like :
select dim_id,dim_type,dim_value from testtable where dim_type='user' and dim_value=’user1’ we are getting back ID for some other value present in testable .
2. We are also seeing duplicate values getting inserted in to this table.
3. Some times values when queried back from same client program are returning result but when you try from some other client it is not showing at all , and is completely lost!
Need your help in debugging..
Please suggest , we are using Oct SP1 build.
Reproducible: Always
### Steps to Reproduce:
It is happening for random values from the value set being inserted.
## Comment 18338
Date: 2013-01-15 18:49:08 +0100
From: @njnes
similar bug was fixed recently, ie could you try to upgrade to Oct2012-sp3
## Comment 18339
Date: 2013-01-15 18:51:12 +0100
From: Ashish Kumar Singh <<ashishk>>
Can you please let me know issue id of that similar bug? when SP3 is slated for release?
Thanks a bunch!
Regards,
Ashish
## Comment 18340
Date: 2013-01-15 19:05:09 +0100
From: @njnes
For SP3 I saw a pre-announcement within the group, ie should be soon.
There was no exact bug report for the similar report, ie was reported in house. But I have the checkin for you http://dev.monetdb.org/hg/MonetDB/rev/69da46562f4e?revcount=240
## Comment 18341
Date: 2013-01-15 21:33:35 +0100
From: Ashish Kumar Singh <<ashishk>>
Great! Can i get somewhere list of bugs which are fixed in sp3 that will help me a lot.
Thanks!
## Comment 18345
Date: 2013-01-17 18:03:55 +0100
From: Ashish Kumar Singh <<ashishk>>
FYA, with SP3 also we saw an issue of values not coming back correctly after insertion.
## Comment 18356
Date: 2013-01-21 17:21:36 +0100
From: Ashish Kumar Singh <<ashishk>>
Guys any update on this?
## Comment 18388
Date: 2013-01-23 09:07:02 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 174
Java program to reproduce the issue
Java program to reproduce the issue
> Attached file: [monetdbIssues.zip](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3222_monetdbIssues.zip_174) (application/x-zip-compressed, 469006 bytes)
> Description: Java program to reproduce the issue
## Comment 18389
Date: 2013-01-23 09:07:29 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 175
SQL schema
SQL schema
> Attached file: [Scema.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3222_Scema.txt_175) (text/plain, 328 bytes)
> Description: SQL schema
## Comment 18390
Date: 2013-01-23 09:08:21 +0100
From: Ashish Kumar Singh <<ashishk>>
Adding test case to reproduce Duplicate records in database table test.
## Comment 18391
Date: 2013-01-23 09:12:40 +0100
From: Ashish Kumar Singh <<ashishk>>
1. Please create schema
2. Update DB connection properties in ConfigurationDBConnection
3. run MonetDBLoadTestBasedOnQueueAndQueryFrequently to reproduce the issue.
Keep on checking for duplicate IDs using query :
select roe_id ,count(*) from test group by roe_id having count(*) > 1
Regards,
Ashish
## Comment 18392
Date: 2013-01-23 16:26:48 +0100
From: @drstmane
Please bear with us --- we also have "real work" to do ...
Being a Java illiterate , I quickly tried the following, but it does not seem to work; maybe some more detailed instructions or easier to use script would be helpful ...
$ mclient /tmp/Scema.txt
operation successful
operation successful
$ diff -du /tmp/monetdbIssue/src/com/altair/test/ConfigurationDBConnection.java{~,}
--- /tmp/monetdbIssue/src/com/altair/test/ConfigurationDBConnection.java~ 2013-01-22 15:59:56.000000000 +0100
+++ /tmp/monetdbIssue/src/com/altair/test/ConfigurationDBConnection.java 2013-01-23 16:22:41.205961431 +0100
@@ -8,7 +8,7 @@
private String userName = "monetdb";
private String driverName = "nl.cwi.monetdb.jdbc.MonetDriver";
- private String connectionString = "jdbc:monetdb://192.168.15.136:50000/pbsworksdb";
+ private String connectionString = "jdbc:monetdb://localhost:50000/demo";
private String password = "monetdb";
public ConfigurationDBConnection() {
$ java /tmp/monetdbIssue/bin/com/altair/test/MonetDBLoadTestBasedOnQueueAndQueryFrequently.class
Exception in thread "main" java.lang.NoClassDefFoundError: /tmp/monetdbIssue/bin/com/altair/test/MonetDBLoadTestBasedOnQueueAndQueryFrequently/class
Caused by: java.lang.ClassNotFoundException: .tmp.monetdbIssue.bin.com.altair.test.MonetDBLoadTestBasedOnQueueAndQueryFrequently.class
at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: /tmp/monetdbIssue/bin/com/altair/test/MonetDBLoadTestBasedOnQueueAndQueryFrequently.class. Program will exit.
## Comment 18393
Date: 2013-01-23 16:29:35 +0100
From: Ashish Kumar Singh <<ashishk>>
Oh my bad I didn't mentioned that i am giving you java sources :) Its an eclipse project so you can import it and run it from there.
## Comment 18394
Date: 2013-01-23 16:39:32 +0100
From: @drstmane
I confess I hardly know what Eclipse is, let alone how to use it. Sorry ...
## Comment 18395
Date: 2013-01-23 16:46:15 +0100
From: Ashish Kumar Singh <<ashishk>>
Okay let me put a complied jar for you for verifying this issue, you already have java sources when you need it. Hold on!
## Comment 18396
Date: 2013-01-23 16:57:47 +0100
From: Ashish Kumar Singh <<ashishk>>
Do you have a JDK to compile the sources ? I can send you the instructions on how to compile and run it?
## Comment 18397
Date: 2013-01-23 17:20:24 +0100
From: @drstmane
$ java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (fedora-68.1.11.5.fc16-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
$ javac -version
javac 1.6.0_24
I/we would highly appreciate if your instructions were cast into, say, a shell script or alike.
## Comment 18398
Date: 2013-01-23 17:38:28 +0100
From: Ashish Kumar Singh <<ashishk>>
Created attachment 176
Monet DB test case
Please follow below steps:
1. Create schema
2. Unpack attached zip file to some directory say test.and cd to it.
3. modify DBConnection.properties to reflect your DB connection settings
4. run following in command:
Windows: java -classpath monetdbissues.jar;log4j-1.2.14.jar;monetdb-jdbc-2.8.jar;DBConnection.properties com.altair.test.MonetDBLoadTestBasedOnQueueAndQueryFrequently
Linux: java -classpath monetdbissues.jar:log4j-1.2.14.jar:monetdb-jdbc-2.8.jar:DBConnection.properties com.altair.test.MonetDBLoadTestBasedOnQueueAndQueryFrequently
> Attached file: [monetIssue.zip](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3222_monetIssue.zip_176) (application/x-zip-compressed, 467958 bytes)
> Description: Monet DB test case
## Comment 18399
Date: 2013-01-23 18:14:53 +0100
From: @njnes
just run it on the (to be released) feb2013 version and cannot reproduce the problem, ie will try on Oct-2012-sp3 now.
## Comment 18400
Date: 2013-01-23 18:18:13 +0100
From: @njnes
your jar has a fixed connection uri in it, ie how could I override this?
## Comment 18401
Date: 2013-01-23 18:46:01 +0100
From: Ashish Kumar Singh <<ashishk>>
Please update connection settings in DBConnection.properties file and run it.
## Comment 18402
Date: 2013-01-23 18:47:01 +0100
From: Ashish Kumar Singh <<ashishk>>
Also please wait for some time 15-20 minutes ; then you will see duplicate records getting entered.
## Comment 18403
Date: 2013-01-23 18:52:48 +0100
From: @drstmane
I run the following on a post Oct2012-SP3 Oct2012 branch:
$ cat Scema.txt ; echo
CREATE SEQUENCE "test_seq" as bigint START WITH 1;
CREATE TABLE test(roe_id bigint DEFAULT NEXT VALUE FOR "test_seq",
roe_type bigint NOT NULL,
node_event_id bigint NOT NULL,
dc_servername varchar(50),
roe_start_date_withtz varchar(50) ,
usr_id bigint,
customgroup_id bigint,
queuename_id bigint,
exitstatus_id bigint);
$ mclient Scema.txt
operation successful
operation successful
$ diff -du DBConnection.properties{~,}
--- DBConnection.properties~ 2013-01-23 21:34:26.000000000 +0100
+++ DBConnection.properties 2013-01-23 17:45:51.554648440 +0100
@@ -5,6 +5,6 @@
Usage of the software is only as explicitly permitted in the end user software license agreement.
Copyright notice does not imply publication.
DriverName=nl.cwi.monetdb.jdbc.MonetDriver
-ConnectionString=jdbc:monetdb://192.168.15.136:50000/pbsworksdb
+ConnectionString=jdbc:monetdb://localhost:50000/demo
username=monetdb
password=monetdb
$ ( date ; time java -classpath monetdbissues.jar:log4j-1.2.14.jar:monetdb-jdbc-2.8.jar:DBConnection.properties com.altair.test.MonetDBLoadTestBasedOnQueueAndQueryFrequently ; date ) &> MonetDBLoadTestBasedOnQueueAndQueryFrequently.log
has been running for an hour now, producing ~80 MB of output (error messages; see attached log).
checks look fine, though:
$ mclient -e /tmp/check.sql
select count(*) from test;
+-------+
| L1 |
+=======+
| 33100 |
+-------+
1 tuple
select count(roe_id) from test;
+-------+
| L1 |
+=======+
| 33100 |
+-------+
1 tuple
select count(distinct roe_id) from test;
+-------+
| L1 |
+=======+
| 33100 |
+-------+
1 tuple
select roe_id ,count(*) from test group by roe_id having count(*) > 1;
+--------+----+
| roe_id | L1 |
+========+====+
+--------+----+
0 tuples
## Comment 18404
Date: 2013-01-23 18:53:23 +0100
From: @drstmane
Created attachment 177
output log
> Attached file: [MonetDBLoadTestBasedOnQueueAndQueryFrequently.log.xz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3222_MonetDBLoadTestBasedOnQueueAndQueryFrequently.log.xz_177) (application/x-xz, 142352 bytes)
> Description: output log
## Comment 18405
Date: 2013-01-23 19:07:43 +0100
From: Ashish Kumar Singh <<ashishk>>
I am running it on Cent OS 5.8 64 bit? what else I can provide you to narrow down on this issue, It is very frequently reproducible on machines we are having.
## Comment 18406
Date: 2013-01-23 19:13:08 +0100
From: Ashish Kumar Singh <<ashishk>>
Wow I just reviewed the logs you attached and here is my observation :
1.DB service went Down .
2. No suitable driver found for blah.... this is another monet bug.
For one hour number of records are way less than what I was seeing.
Sql State: 08001
Check whether database service is running or not
java.sql.SQLException: No suitable driver found for
at java.sql.DriverManager.getConnection(DriverManager.java:640)
at java.sql.DriverManager.getConnection(DriverManager.java:200)
at com.altair.test.ConfigurationDBConnection.getConnection(ConfigurationDBConnection.java:38)
at com.altair.test.JobInsertionThread.run(JobInsertionThread.java:71)
java.lang.NullPointerException
at com.altair.test.JobInsertionThread.run(JobInsertionThread.java:156)
Could not connect to the database
No suitable driver found for
Sql State: 08001
Check whether database service is running or not
java.sql.SQLException: No suitable driver found for
at java.sql.DriverManager.getConnection(DriverManager.java:640)
at java.sql.DriverManager.getConnection(DriverManager.java:200)
at com.altair.test.ConfigurationDBConnection.getConnection(ConfigurationDBConnection.java:38)
at com.altair.test.JobInsertionThread.run(JobInsertionThread.java:71)
java.lang.NullPointerException
at com.altair.test.JobInsertionThread.run(JobInsertionThread.java:156)
Could not connect to the database
## Comment 18407
Date: 2013-01-23 19:31:26 +0100
From: Ashish Kumar Singh <<ashishk>>
Guys,
Thanks for looking in to it. Here are few proposals I would like to make to help you out on the issue I am facing and have it reproduced at your end:
1. zip Monet DB instance from my machine and send it to you with steps how to run it so you will be able to see final corrupt state of the system if you run it on a cent os operating system.
2. I can create a VM for you with Test program and Monet DB packaged with in it and make it available for you.
3. We can have a Web meeting to show you that.
Regards,
Ashish
## Comment 18408
Date: 2013-01-23 21:55:05 +0100
From: @njnes
Just to make sure. Did you test SP3 starting with a fresh DB. Thats what we are doing now, and indeed sofar we cannot repeat your problem.
## Comment 18409
Date: 2013-01-23 22:01:57 +0100
From: Ashish Kumar Singh <<ashishk>>
Yes we did , on more than one machines.
## Comment 18410
Date: 2013-01-24 08:15:23 +0100
From: @njnes
it seems your test triggered an assert in my testing with oct2012-sp3. Sofar no
inconsistencies, but if compiled without asserts this may have caused this.
So will continue to search for the reason why the assert was triggered.
## Comment 18411
Date: 2013-01-24 08:29:56 +0100
From: Ashish Kumar Singh <<ashishk>>
Thanks Neil , Can you guide how to compile with asserts! Why it is not mandatory setting for
## Comment 18412
Date: 2013-01-24 08:30:24 +0100
From: Ashish Kumar Singh <<ashishk>>
---- monetdb compilation and is default?
Thanks Again
## Comment 18413
Date: 2013-01-24 08:40:35 +0100
From: @njnes
For releases 'asserts' are disabled. This is normal and I would say expected. Asserts will have a big impact on the performance.
To enable asserts, you need to configure with --enable-asserts (and recompile, ie make clean; make install;).
## Comment 18414
Date: 2013-01-24 11:01:24 +0100
From: Ashish Kumar Singh <<ashishk>>
Hi Neil ,
Will you be interested in getting a VM ware with my test and instance of monet db which produces this issue more frequently?
Regards,
Ashish
## Comment 18415
Date: 2013-01-24 12:04:46 +0100
From: @drstmane
For the records:
My Oct2012-SP3++ run was with assertions enabled, but I did not see any assertions during the first hour. I'm now not at the console to check the server output; however, the server is still running, so there cannot have been any assertion so far ...
It seems that also the java program is still running (after ~18 hours!), but it seems to have stopped producing output (errors) after ~4 hours. Checks now say:
$ mclient -e check.sql
select count(*) from test;
+-------+
| L1 |
+=======+
| 99900 |
+-------+
1 tuple
select count(roe_id) from test;
+-------+
| L1 |
+=======+
| 99900 |
+-------+
1 tuple
select count(distinct roe_id) from test;
+-------+
| L1 |
+=======+
| 99900 |
+-------+
1 tuple
select roe_id ,count(*) from test group by roe_id having count(*) > 1;
+--------+----+
| roe_id | L1 |
+========+====+
+--------+----+
0 tuples
## Comment 18416
Date: 2013-01-24 12:08:20 +0100
From: Ashish Kumar Singh <<ashishk>>
Okay so when you say Oct SP3++ , it is Feb candidate branch.
## Comment 18417
Date: 2013-01-24 12:21:18 +0100
From: @drstmane
Nope, Oct2012-SP3++ is Oct2012 branch after Oct2012-SP3 release --- I don't think, though, there have been any relevant changes on that branch after the release.
## Comment 18418
Date: 2013-01-24 12:33:34 +0100
From: Ashish Kumar Singh <<ashishk>>
So what shall be our next step you propose Neil and Stefan?
## Comment 18419
Date: 2013-01-24 13:09:31 +0100
From: @drstmane
Well, maybe you could do as Niels suggested: build the Oct2012-SP2 release from scratch with assertions enabled (configure --enable-assert ...), run your experiment, and report whether it triggers any assertions. Please then also report in more detail what your program actually does (and how?), its output (if any) and the server output / logs.
My logs suggest that you program (in my case now running for more than 19 hours --- is it supposed to end sometime?) does lots of concurrent transactions. If so, I assume you are aware of MonetDB optimistic concurrency control and the consequences for your client application, right?
## Comment 18420
Date: 2013-01-24 14:19:45 +0100
From: Ashish Kumar Singh <<ashishk>>
Yep that's correct , I am aware of consequences of optimistic concurrency control.
Only point is that it shall not end up in a db state where records are duplicated!
I will try one build with assertion enabled and update you .
Do you see by any chance any thirdparty libraries version can cause this issue?
## Comment 18421
Date: 2013-01-24 14:30:57 +0100
From: @drstmane
FYI:
I just built Oct2012-SP1(!) from scratch with assertions enabled, and run your program. I produces the same java exceptions and errors as with Oct2012-SP3++ (just considerably more; >200 MB in one hour), but the server is running flawlessly, and the data looks fine:
$ mclient -e /tmp/check.sql
select * from test limit 1;
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
| roe_id | roe_type | node_event_id | dc_servername | roe_start_date_withtz | usr_id | customgroup_id | queuename_id | exitstatus_id |
+========+==========+===============+===============+=======================+========+================+==============+===============+
| 1101 | 0 | 0 | s | s | 0 | 0 | 0 | 1 |
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
1 tuple
select count(*) from test;
+-------+
| L1 |
+=======+
| 30661 |
+-------+
1 tuple
select count(roe_id) from test;
+-------+
| L1 |
+=======+
| 30661 |
+-------+
1 tuple
select count(distinct roe_id) from test;
+-------+
| L1 |
+=======+
| 30661 |
+-------+
1 tuple
select roe_id ,count(*) from test group by roe_id having count(*) > 1;
+--------+----+
| roe_id | L1 |
+========+====+
+--------+----+
0 tuples
## Comment 18422
Date: 2013-01-24 14:33:15 +0100
From: @drstmane
I'm running under 64-bit Fedora 16 on an Intel Core i7-2600 CPU @ 3.40GHz (4 cores + hyperthreading = 8 HW threads)
## Comment 18423
Date: 2013-01-24 14:36:09 +0100
From: Ashish Kumar Singh <<ashishk>>
I am running under Cent OS 5.8 64 bit , 2 core 4 GB ram . Client is windows client with 2 core 4 GB of ram if it helps. We saw this issue in RHEL and SLES 11 also .
## Comment 18424
Date: 2013-01-24 14:45:57 +0100
From: @drstmane
So, how long is your programm supposed to run, and are those zillions of java
exceptions expected to appear on the console (i.e., not caught and handled by
your program)?
java.sql.SQLException: COMMIT: transaction is aborted because of concurency
conflicts, will ROLLBACK instead
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2535)
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(MonetStatement.java:544)
at
com.altair.test.UpdateFrequentlyThread.run(UpdateFrequentlyThread.java:24)
## Comment 18425
Date: 2013-01-24 14:50:41 +0100
From: Ashish Kumar Singh <<ashishk>>
Okay after 100000 records are inserted it shall stop inserting new data, it doesn't exits as of now by default my bad :(.
Those exceptions i am printing intentionally as my observation was during concurrency conflicts only records are getting duplicated in DB.
Now I am running one assertion enabled build against Oct SP3. Where to look for logs after assertion fails?
## Comment 18426
Date: 2013-01-24 14:55:10 +0100
From: @drstmane
An assertion stops the server. If you start mserver5 by hand, you'll see that on the console whether you started mserver5. If you use monetdbd, you'll need to check the merovingian log in you dbfarm.
## Comment 18427
Date: 2013-01-24 15:00:17 +0100
From: @drstmane
After an hour and a half with Oct2012-SP1 I get
$ mclient -e /tmp/check.sql
select * from test limit 1;
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
| roe_id | roe_type | node_event_id | dc_servername | roe_start_date_withtz | usr_id | customgroup_id | queuename_id | exitstatus_id |
+========+==========+===============+===============+=======================+========+================+==============+===============+
| 1101 | 0 | 0 | s | s | 0 | 0 | 0 | 1 |
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
1 tuple
select count(*) from test;
+-------+
| L1 |
+=======+
| 46381 |
+-------+
1 tuple
select count(roe_id) from test;
+-------+
| L1 |
+=======+
| 46381 |
+-------+
1 tuple
select count(distinct roe_id) from test;
+-------+
| L1 |
+=======+
| 46360 |
+-------+
1 tuple
select roe_id ,count(*) from test group by roe_id having count(*) > 1;
+--------+------+
| roe_id | L1 |
+========+======+
| 482580 | 2 |
| 482581 | 2 |
| 482582 | 2 |
| 482583 | 2 |
| 482584 | 2 |
| 482585 | 2 |
| 482586 | 2 |
| 482587 | 2 |
| 482588 | 2 |
| 482589 | 2 |
| 482590 | 2 |
| 482591 | 2 |
| 482592 | 2 |
| 482593 | 2 |
| 482594 | 2 |
| 482595 | 2 |
| 482596 | 2 |
| 482597 | 2 |
| 482598 | 2 |
| 482599 | 2 |
| 482600 | 2 |
+--------+------+
21 tuples
So my conclusion so far: reproducible with Oct2012-SP1, but not with Oct2012-SP3++; will now try the Oct2012-SP3 release ...
## Comment 18428
Date: 2013-01-24 17:16:29 +0100
From: Ashish Kumar Singh <<ashishk>>
On sp3 fresh compile i was able to reproduce it, if you are not able to reproduce it easily then running multiple instances on test program in paralllel helps! With two test client instances running this was more easily coming in my case!
Thanks guys for your help on debugging this issue with me!
## Comment 18429
Date: 2013-01-24 18:30:00 +0100
From: @drstmane
Oct2012-SP3 with single client works fine for me; after 3 h:
$ mclient -e /tmp/check.sql
select * from test limit 1;
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
| roe_id | roe_type | node_event_id | dc_servername | roe_start_date_withtz | usr_id | customgroup_id | queuename_id | exitstatus_id |
+========+==========+===============+===============+=======================+========+================+==============+===============+
| 1101 | 0 | 0 | s | s | 0 | 0 | 0 | 1 |
+--------+----------+---------------+---------------+-----------------------+--------+----------------+--------------+---------------+
1 tuple
select min(roe_id), max(roe_id), count(*), count(roe_id), count(distinct roe_id) from test;
+------+---------+-------+-------+-------+
| L1 | L2 | L3 | L4 | L5 |
+======+=========+=======+=======+=======+
| 1101 | 1163900 | 99699 | 99699 | 99699 |
+------+---------+-------+-------+-------+
1 tuple
select roe_id ,count(*) from test group by roe_id having count(*) > 1;
+--------+----+
| roe_id | L1 |
+========+====+
+--------+----+
0 tuples
No time to test multiple clients soon. sorry.
## Comment 18430
Date: 2013-01-24 18:50:17 +0100
From: @njnes
okay it triggered an assert again. I don't have a solution just jet, but one test you could do is to set MAX_SPARES (in sql/storage/store.c) to 1 (instead of 32).
## Comment 18431
Date: 2013-01-24 19:01:52 +0100
From: @njnes
unfortunately MAXSPARES=1 doesn't help. Closing in on the problem a bit..
## Comment 18432
Date: 2013-01-24 22:49:58 +0100
From: @njnes
found an issue. Probably a fix by tomorrow.
## Comment 18433
Date: 2013-01-25 09:05:45 +0100
From: Ashish Kumar Singh <<ashishk>>
Kudos! Great thanks Neil !! I will wait to hear from you . If you need any other thing from my side I will be happy to help.
## Comment 18434
Date: 2013-01-25 10:58:09 +0100
From: @njnes
Changeset [4abd55aed644](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4abd55aed644) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4abd55aed644](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4abd55aed644)
Changeset description:
fix for bug #3222
ie make sure appends get correctly handled
## Comment 18435
Date: 2013-01-25 11:02:52 +0100
From: @njnes
please test the fix, using one of the version SP3++, Feb2013 or default, all are only available via hg, ie sources
## Comment 18436
Date: 2013-01-25 11:16:50 +0100
From: Ashish Kumar Singh <<ashishk>>
Let me try Neil!
## Comment 18452
Date: 2013-01-30 08:36:13 +0100
From: @drstmane
Ashish,
any news on this one? Does it work for you, now?
Thanks!
## Comment 18458
Date: 2013-02-10 13:28:44 +0100
From: @drstmane
Ashish,
any news on this one?
Does it work for you, now, and we can close this one as fixed?
Thanks!
## Comment 18519
Date: 2013-02-19 13:23:51 +0100
From: @sjoerdmullender
Feb2013 has been released.
| Monet DB giving wrong value from a table when a value is queried after insertion/ Data Loss | https://api.github.com/repos/MonetDB/MonetDB/issues/3222/comments | 0 | 2020-11-30T12:16:45Z | 2024-06-27T11:58:46Z | https://github.com/MonetDB/MonetDB/issues/3222 | 753,429,806 | 3,222 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-14 23:07:26 +0100
From: Christian Braun <<hcb>>
To: clients devs <<bugs-clients>>
Version: 11.13.7 (Oct2012-SP2)
Last updated: 2013-02-19 13:18:01 +0100
## Comment 18329
Date: 2013-01-14 23:07:26 +0100
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
when executing a statement larger then 16381 bytes the server disconnects the client. the attached patch lowers the maximum package size to 8190. the same maximum size the mclient utility uses.
Reproducible: Always
## Comment 18330
Date: 2013-01-14 23:08:14 +0100
From: Christian Braun <<hcb>>
Created attachment 170
patch
> Attached file: [php_monet.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3221_php_monet.patch_170) (text/plain, 649 bytes)
> Description: patch
## Comment 18331
Date: 2013-01-14 23:08:43 +0100
From: Christian Braun <<hcb>>
Created attachment 171
execute large statements
> Attached file: [test.php](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3221_test.php_171) (application/php, 492 bytes)
> Description: execute large statements
## Comment 18332
Date: 2013-01-14 23:29:02 +0100
From: @sjoerdmullender
Changeset [e134946a0ccb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e134946a0ccb) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e134946a0ccb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e134946a0ccb)
Changeset description:
Fixed bug #3221 and added test.
Thanks both for the bug report, the fix, and the test to Christian Braun.
## Comment 18517
Date: 2013-02-19 13:18:01 +0100
From: @sjoerdmullender
Feb2013 has been released.
| can no execute large statements | https://api.github.com/repos/MonetDB/MonetDB/issues/3221/comments | 0 | 2020-11-30T12:16:43Z | 2024-06-27T11:58:45Z | https://github.com/MonetDB/MonetDB/issues/3221 | 753,429,772 | 3,221 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-14 09:59:52 +0100
From: @drstmane
To: GDK devs <<bugs-common>>
Version: 11.15.1 (Feb2013)
Last updated: 2013-01-18 21:32:30 +0100
## Comment 18328
Date: 2013-01-14 09:59:52 +0100
From: @drstmane
Selections "<0", ">0", "<>0" on float & double (in SQL) fail with Intel's icc on Linux, i.e., it seems that nextafter(0,..) & nextafterf(0,..) don't seem to work as expected with Intel's icc.
See example below.
This makes these tests fail (with icc on Linux:
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46622:7e26417c92b6&target=Int-Fedora-x86_64-propcheck-oid32&module=sql&test=benchmarks%2FATIS%2Fselect_group&which=out
http://monetdb.cwi.nl/testweb/web/showtestoutput.php?serial=46622:7e26417c92b6&target=Int-Fedora-x86_64-propcheck-oid32&module=sql&test=test%2FBugTracker-2009%2Fpush-select-div-down.SF-2593341&which=err
sql>create table x (y double, z float);
operation successful (1.992ms)
sql>insert into x values (0,0);
1 affected row (1.590ms)
sql>insert into x values (0.1,0.1);
1 affected row (1.321ms)
sql>insert into x values (-0.1,-0.1);
1 affected row (1.316ms)
sql>insert into x values (-0.2,-0.2);
1 affected row (1.252ms)
sql>insert into x values (0.2,0.2);
1 affected row (1.313ms)
sql>select * from x;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
5 tuples (3.911ms)
sql>select * from x where y = 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
+--------------------------+--------------------------+
1 tuple (3.262ms)
sql>select * from x where z = 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
+--------------------------+--------------------------+
1 tuple (3.112ms)
sql>select * from x where y < 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (5.380ms)
sql>select * from x where z < 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (4.969ms)
sql>select * from x where y > 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (5.347ms)
sql>select * from x where z > 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (5.018ms)
sql>select * from x where y <> 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
5 tuples (5.837ms)
sql>select * from x where z <> 0;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
5 tuples (5.248ms)
sql>select * from x where y > 0.1;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
1 tuple (4.915ms)
sql>select * from x where y < 0.1;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| -0.10000000000000001 | -0.10000000000000001 |
| -0.20000000000000001 | -0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (5.060ms)
sql>select * from x where y < -0.1;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| -0.20000000000000001 | -0.20000000000000001 |
+--------------------------+--------------------------+
1 tuple (5.839ms)
sql>select * from x where y > -0.1;
+--------------------------+--------------------------+
| y | z |
+==========================+==========================+
| 0 | 0 |
| 0.10000000000000001 | 0.10000000000000001 |
| 0.20000000000000001 | 0.20000000000000001 |
+--------------------------+--------------------------+
3 tuples (5.185ms)
## Comment 18333
Date: 2013-01-15 10:12:11 +0100
From: @sjoerdmullender
Changeset [33497e39fe3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=33497e39fe3f) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=33497e39fe3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=33497e39fe3f)
Changeset description:
Added test for bug #3220.
## Comment 18346
Date: 2013-01-17 22:48:45 +0100
From: @drstmane
Changeset [774b1d62cb42](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=774b1d62cb42) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=774b1d62cb42](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=774b1d62cb42)
Changeset description:
Make nextafter() & nextafterf() work correctly with Intel icc:
It appears we need to use "-mp" instead of "-mp1" for improved
floating-point precision to make nextafter() & nextafterf()
work correctly with Intel icc.
This fixes bug #3220.
## Comment 18347
Date: 2013-01-18 21:32:30 +0100
From: @drstmane
TestWeb confirms "fix". Closing.
| Selections "<0", ">0", "<>0" on float & double fail with Intel's icc on Linux | https://api.github.com/repos/MonetDB/MonetDB/issues/3220/comments | 0 | 2020-11-30T12:16:40Z | 2024-06-27T11:58:44Z | https://github.com/MonetDB/MonetDB/issues/3220 | 753,429,748 | 3,220 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-13 19:35:23 +0100
From: Christian Braun <<hcb>>
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
CC: hcb, @njnes
Last updated: 2013-01-13 20:40:53 +0100
## Comment 18323
Date: 2013-01-13 19:35:23 +0100
From: Christian Braun <<hcb>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier:
Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012-SP2)
Database: MonetDB v11.13.7 (Oct2012-SP2), 'mapi:monetdb://etna:50000/db'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select date_to_str(now(), '%Y%m');
+-------------------+
| current_timestamp |
+===================+
| 201301 |
+-------------------+
1 tuple (0.595ms)
sql>create schema wolf;
operation successful (0.711ms)
sql>set schema wolf;
auto commit mode: on
sql>select date_to_str(now(), '%Y%m');
SELECT: no such binary operator 'date_to_str(timestamptz,char)'
sql>select sys.date_to_str(now(), '%Y%m');
+-------------------+
| current_timestamp |
+===================+
| 201301 |
+-------------------+
1 tuple (0.714ms)
Reproducible: Always
## Comment 18324
Date: 2013-01-13 20:11:50 +0100
From: @njnes
try select sys.date_to_str(now(), "%Y%m');
## Comment 18325
Date: 2013-01-13 20:13:03 +0100
From: @njnes
marked as invalid because functions are resolved in the users default schema. Once changed to a different schema full qualified named should be used (ie including the schema names).
## Comment 18326
Date: 2013-01-13 20:30:05 +0100
From: Christian Braun <<hcb>>
Created attachment 169
example
> Attached file: [monetdb.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3219_monetdb.txt_169) (text/plain, 2860 bytes)
> Description: example
## Comment 18327
Date: 2013-01-13 20:40:53 +0100
From: Christian Braun <<hcb>>
Seems to differ by function type. Maybe not a bug. But a bit inconsistent.
| function not found after set schema | https://api.github.com/repos/MonetDB/MonetDB/issues/3219/comments | 0 | 2020-11-30T12:16:38Z | 2024-06-28T13:16:49Z | https://github.com/MonetDB/MonetDB/issues/3219 | 753,429,724 | 3,219 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-10 07:48:48 +0100
From: Patrick TJ McPhee <<ptjm>>
To: SQL devs <<bugs-sql>>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes
Last updated: 2013-06-09 20:25:52 +0200
## Comment 18322
Date: 2013-01-10 07:48:48 +0100
From: Patrick TJ McPhee <<ptjm>>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.4) Gecko/20091114 Firefox/3.5.4
Build Identifier:
When two tables are joined using a column, that column can't be qualified by the name of either of the table, and doesn't appear in the list of columns qualified by <table>.*.
Given x (a,b) and y (a,c), the query "select * from x join y using (a)" returns a,b,c as expected, but "select x.* from x join y using (a)" returns b only and "select y.* from x join y using (a)" returns c only.
As a work-around, this works: "select x.* from x join y on x.a = y.a;"
Reproducible: Always
### Steps to Reproduce:
1.create table x (a varchar(20) primary key, b varchar(20));
2.create table y (a varchar(20) primary key, c int);
3.insert into a values ('alpha', 'bravo'), ('charlie', 'delta'), ('echo', 'foxtrot');
4.insert into x values ('alpha', 'bravo'), ('charlie', 'delta'), ('echo', 'foxtrot');
5.select x.* from x join y using (a);
### Actual Results:
+---------+
| b |
+=========+
| bravo |
| delta |
| foxtrot |
+---------+
3 tuples (4.259ms)
### Expected Results:
+---------+---------+
| a | b |
+=========+=========+
| alpha | bravo |
| charlie | delta |
| echo | foxtrot |
+---------+---------+
3 tuples (4.608ms)
This was observed with 11.13.7 under Linux and reproduced with 11.13.3 under FreeBSD and 11.13.5 under NetBSD.
I concede that this does appear to be according to the SQL 92 standard, however it's inconsistent with other database systems which makes porting a problem. For instance, I've confirmed the expected behaviour with postgresql, sqlite, and vectorwise.
## Comment 18806
Date: 2013-06-09 20:25:52 +0200
From: @njnes
We follow the sql specs here.
| Join common column does not appear in * qualified by table name | https://api.github.com/repos/MonetDB/MonetDB/issues/3218/comments | 0 | 2020-11-30T12:16:36Z | 2024-06-28T13:16:49Z | https://github.com/MonetDB/MonetDB/issues/3218 | 753,429,695 | 3,218 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-07 05:17:50 +0100
From: Patrick TJ McPhee <<ptjm>>
To: GDK devs <<bugs-common>>
Version: 11.13.9 (Oct2012-SP3)
Last updated: 2013-03-08 08:44:34 +0100
## Comment 18320
Date: 2013-01-07 05:17:50 +0100
From: Patrick TJ McPhee <<ptjm>>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.4) Gecko/20091114 Firefox/3.5.4
Build Identifier:
On NetBSD, the defines HAVE_KVM_H and HAVE_SYS_SYSCTL_H are defined, which drops the code into the FreeBSD KVM code for returning RSS, but NetBSD's implementation is not compatible.
I'll attach a patch which allows it to compile. I've only tried this on NetBSD 6, amd64.
Reproducible: Always
### Steps to Reproduce:
1. run configure
2. run gmake
### Actual Results:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../common/options -I./../common/options -I../common/stream -I./../common/stream -I../common/utils -I./../common/utils -I/usr/pkg/include -DLIBGDK -O3 -fomit-frame-pointer -pipe -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c gdk_posix.c -fPIC -DPIC -o .libs/libbat_la-gdk_posix.o
gdk_posix.c: In function 'MT_getrss':
gdk_posix.c:326:10: error: 'struct kinfo_proc' has no member named 'ki_rssize'
### Expected Results:
No compilation error.
## Comment 18321
Date: 2013-01-07 05:19:28 +0100
From: Patrick TJ McPhee <<ptjm>>
Created attachment 168
Patch which allows gdk_posix.c to compile under NetBSD 6
> Attached file: [netbsd-gdk.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3217_netbsd-gdk.patch_168) (text/plain, 344 bytes)
> Description: Patch which allows gdk_posix.c to compile under NetBSD 6
## Comment 18335
Date: 2013-01-15 16:03:13 +0100
From: @sjoerdmullender
Changeset [9880ae072539](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9880ae072539) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9880ae072539](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9880ae072539)
Changeset description:
Make compilable on NetBSD.
This should fix bug #3217. Thanks to Patrick TJ McPhee.
## Comment 18441
Date: 2013-01-29 10:16:58 +0100
From: @sjoerdmullender
I'm assuming that this is now resolved. Please reopen if that is not the case.
The fix didn't make it to the Oct2012-SP3 release, but should be in the next release.
## Comment 18508
Date: 2013-02-19 13:17:56 +0100
From: @sjoerdmullender
Feb2013 has been released.
## Comment 18596
Date: 2013-03-08 06:33:43 +0100
From: Patrick TJ McPhee <<ptjm>>
Confirmed this worked with Feb2013 and Feb2013 sp1.
## Comment 18597
Date: 2013-03-08 08:44:34 +0100
From: @sjoerdmullender
Thanks for verifying.
| gdk_posix fails to compile under NetBSD | https://api.github.com/repos/MonetDB/MonetDB/issues/3217/comments | 0 | 2020-11-30T12:16:33Z | 2024-06-27T11:58:42Z | https://github.com/MonetDB/MonetDB/issues/3217 | 753,429,667 | 3,217 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-07 04:22:37 +0100
From: Patrick TJ McPhee <<ptjm>>
To: clients devs <<bugs-clients>>
Version: 11.13.7 (Oct2012-SP2)
Last updated: 2013-02-19 13:17:57 +0100
## Comment 18318
Date: 2013-01-07 04:22:37 +0100
From: Patrick TJ McPhee <<ptjm>>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.4) Gecko/20091114 Firefox/3.5.4
Build Identifier:
If you create a .monetdb file with a width setting, e.g.,
width=-1
mclient gives this error message:
.monetdb:1: unknown property: width
The setting actually works, but the error message appears on the screen. The same happens for format.
I have a patch that fixes it (and also adds a database parameter in case you'd care to do that :).
Reproducible: Always
### Steps to Reproduce:
1. add width=<value> to .monetdb
2. start mclient
### Actual Results:
.monetdb:1: unknown property: width
is displayed
### Expected Results:
For nothing to be displayed.
I've observed this on Linux, NetBSD, and FreeBSD, but it should be an issue on all platforms. This patch resolves the issue. It also adds a database parameter
--- mclient.c.orig 2012-12-12 07:00:35.000000000 -0500
+++ mclient.c 2013-01-06 21:54:46.000000000 -0500
@@ -2788,9 +2788,14 @@
}
} else if (strcmp(buf, "format") == 0) {
output = strdup(q);
+ q = NULL;
+ } else if (strcmp(buf, "database") == 0) {
+ dbname = strdup(q); /* leak */
+ q = NULL;
} else if (strcmp(buf, "width") == 0) {
pagewidth = atoi(q);
pagewidthset = pagewidth != 0;
+ q = NULL;
}
if (q != NULL)
mnstr_printf(stderr_stream,
## Comment 18319
Date: 2013-01-07 04:25:10 +0100
From: Patrick TJ McPhee <<ptjm>>
Created attachment 167
Patch to mclient which resolves the issue, and adds a database parameter
> Attached file: [mclient.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3216_mclient.patch_167) (text/plain, 567 bytes)
> Description: Patch to mclient which resolves the issue, and adds a database parameter
## Comment 18336
Date: 2013-01-15 16:14:23 +0100
From: @sjoerdmullender
This bug occurs to the Oct2012 branch only. It does not occur in the Feb2013 branch.
## Comment 18509
Date: 2013-02-19 13:17:57 +0100
From: @sjoerdmullender
Feb2013 has been released.
| "unknown property" error setting format and width in .monetdb file | https://api.github.com/repos/MonetDB/MonetDB/issues/3216/comments | 0 | 2020-11-30T12:16:31Z | 2024-06-27T11:58:41Z | https://github.com/MonetDB/MonetDB/issues/3216 | 753,429,629 | 3,216 |
[
"MonetDB",
"MonetDB"
] | Date: 2013-01-03 19:00:31 +0100
From: Glauber <<glauberal>>
To: SQL devs <<bugs-sql>>
Version: 11.13.9 (Oct2012-SP3)
Last updated: 2013-02-19 13:18:00 +0100
## Comment 18316
Date: 2013-01-03 19:00:31 +0100
From: Glauber <<glauberal>>
User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11
Build Identifier:
I need to get the same date period for the previous year based on the current year. Example: 01.01.2013 to 02.01.2013 - last year Period: 2012-01-01 to 2012-01-02, then used the same sql I use in Postgres.
select date from dim_tempo
where date between cast ('2013-01-01 'as timestamp) + INTERVAL' -1 'year
and cast ('2013-01-02 'as timestamp) + INTERVAL' -1 'year
+ -------------------- +
| Date |
+ ==================== +
| 2012-01-01 00:00:00 |
| 2012-01-02 00:00:00 |
+ -------------------- +
MonetDB - Result Wrong
select date from dim_tempo
where date between cast ('2013-01-01 'as date) + interval' -1 'year
and cast ('2013-01-02 'as date) + interval' -1 'year;
+ ------------ +
| Date |
+ ============ +
| 2012-01-02 |
| 2012-01-03 |
+ ------------ +
Reproducible: Always
### Steps to Reproduce:
DDL and inserts Postgres:
CREATE TABLE dim_tempo
(
id_tempo double precision,
data timestamp without time zone
);
insert into dim_tempo values (1,'2012-01-01'), (2,'2012-01-02'), (3,'2012-01-03'), (4,'2012-01-04'), (5,'2013-01-01'), (6,'2013-01-02'), (7,'2013-01-03'), (8,'2013-01-04');
DDL and inserts MonetDB:
CREATE TABLE dim_tempo
(
id_tempo integer,
data date
);
insert into dim_tempo values (1,'2012-01-01'), (2,'2012-01-02'), (3,'2012-01-03'), (4,'2012-01-04'), (5,'2013-01-01'), (6,'2013-01-02'), (7,'2013-01-03'), (8,'2013-01-04');
1. run this query on another DBMS example: postgres
select date from dim_tempo
where date between cast ('2013-01-01 'as timestamp) + INTERVAL' -1 'year
and cast ('2013-01-02 'as timestamp) + INTERVAL' -1 'year
2. run this query in Monetdb, I used to run mclient
select date from dim_tempo
where date between cast ('2013-01-01 'as date) + interval' -1 'year
and cast ('2013-01-02 'as date) + interval' -1 'year;
3.
### Actual Results:
+ ------------ +
| Date |
+ ============ +
| 2012-01-02 |
| 2012-01-03 |
+ ------------ +
### Expected Results:
+ ------------ +
| Date |
+ ============ +
| 2012-01-01 |
| 2012-01-02 |
+ ------------ +
I am Brazilian!
## Comment 18442
Date: 2013-01-29 10:22:37 +0100
From: @sjoerdmullender
Changeset [fdbfe3a3f1bd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fdbfe3a3f1bd) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fdbfe3a3f1bd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fdbfe3a3f1bd)
Changeset description:
Add test for bug #3215.
## Comment 18443
Date: 2013-01-29 10:37:31 +0100
From: @sjoerdmullender
Changeset [27f146dcaa6c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=27f146dcaa6c) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=27f146dcaa6c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=27f146dcaa6c)
Changeset description:
Add or subtract number of days in correct month.
We need to adjust the year when wrapping months since some years are
leap years.
This fixes bug #3215.
## Comment 18444
Date: 2013-01-29 10:40:31 +0100
From: @sjoerdmullender
Should appear in the next release.
## Comment 18516
Date: 2013-02-19 13:18:00 +0100
From: @sjoerdmullender
Feb2013 has been released.
| Calculation Date function using interval and year | https://api.github.com/repos/MonetDB/MonetDB/issues/3215/comments | 0 | 2020-11-30T12:16:28Z | 2024-06-27T11:58:40Z | https://github.com/MonetDB/MonetDB/issues/3215 | 753,429,601 | 3,215 |
[
"MonetDB",
"MonetDB"
] | Date: 2012-12-25 23:03:04 +0100
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.15.1 (Feb2013)
CC: @mlkersten
Last updated: 2012-12-26 09:06:15 +0100
## Comment 18303
Date: 2012-12-25 23:03:04 +0100
From: @drstmane
While appearing to work fine in single-threaded mode (Mtest.py -n1), changeset [98e4b2ac3e5c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98e4b2ac3e5c) appears to cause severe problems, including double-free's, crashes (segfaults), and timeouts with both sql & geom tests.
In my case, SQl testing summary turned from
real 11m1.704s
!ERROR: Testing FAILED SIGNIFICANTLY (14 out of 1286 tests failed)
42 out of 1286 tests could not be executed
2 out of 1286 tests caused an abort (assertion failure)
12 out of 1286 tests produced SIGNIFICANTLY different output
into
real 249m45.083s
!ERROR: Testing FAILED SIGNIFICANTLY (561 out of 1286 tests failed)
159 out of 1286 tests could not be executed
60 out of 1286 tests ran into timeout
1 out of 1286 tests caused an abort (assertion failure)
8 out of 1286 tests resulted in a crash
492 out of 1286 tests produced SIGNIFICANTLY different output
yielding among others
*** glibc detected *** mserver5: double free or corruption (out): 0x0000000003a6d3d0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3cf307da76]
/lib64/libc.so.6[0x3cf307ed5e]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libbat.so.8(+0x92775)[0x7f7820002775]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libbat.so.8(+0x8fcc4)[0x7f781ffffcc4]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libbat.so.8(HEAPextend+0x452)[0x7f7820000df2]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libmonetdb5.so.13(MATpackIncrement+0x369)[0x7f78207e0fb9]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libmonetdb5.so.13(runMALsequence+0xd7e)[0x7f782068e52e]
/ufs/manegold/_/Monet/HG/Feb2013/prefix/--disable-debug_--enable-assert_--enable-optimize/lib64/libmonetdb5.so.13(+0x547cd)[0x7f78206907cd]
/lib64/libpthread.so.0[0x3cf3c07d90]
/lib64/libc.so.6(clone+0x6d)[0x3cf30f119d]
See also nightly testing at
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=46407:98e4b2ac3e5c
## Comment 18304
Date: 2012-12-25 23:05:38 +0100
From: @drstmane
While seemingly looking innocent at first sight, I do wonder why the new code extends the vheap of the input BAT, rather than extending / creating the vheap of the newly created result BAT ...
## Comment 18305
Date: 2012-12-25 23:09:51 +0100
From: @drstmane
http://dev.monetdb.org/hg/MonetDB/rev/98e4b2ac3e5c
## Comment 18306
Date: 2012-12-26 08:38:19 +0100
From: @drstmane
Would this patch make any sense and be in line with the original intention?
diff -r [98e4b2ac3e5c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98e4b2ac3e5c) monetdb5/modules/mal/mat.c
--- a/monetdb5/modules/mal/mat.c Tue Dec 25 10:54:07 2012 +0100
+++ b/monetdb5/modules/mal/mat.c Wed Dec 26 08:29:53 2012 +0100
@@ -157,9 +157,9 @@
if (bn == NULL)
throw(MAL, "mat.pack", MAL_MALLOC_FAIL);
/* allocate enough space for the strings */
- if ( b->T->vheap ){
+ if ( b->T->vheap && bn->T->vheap ){
newsize = b->T->vheap->size * pieces;
- if (HEAPextend(b->T->vheap, newsize) < 0)
+ if (HEAPextend(bn->T->vheap, newsize) < 0)
throw(MAL, "mat.pack", MAL_MALLOC_FAIL);
}
BATsettrivprop(bn);
## Comment 18307
Date: 2012-12-26 08:41:44 +0100
From: @mlkersten
yes, commit to source.
During incremental pack we should also reserve space for the vheap.
## Comment 18308
Date: 2012-12-26 08:45:51 +0100
From: @drstmane
Changeset [fbbff91f89da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fbbff91f89da) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbbff91f89da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbbff91f89da)
Changeset description:
fixing changeset [98e4b2ac3e5c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98e4b2ac3e5c) & bug #3214: extend vheap of result, not vheap of input
## Comment 18309
Date: 2012-12-26 09:06:15 +0100
From: @drstmane
After changeset [fbbff91f89da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fbbff91f89da) testing works, again, as it did before changeset [98e4b2ac3e5c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98e4b2ac3e5c) .
| changeset 98e4b2ac3e5c causes double-free's, crashes and timeouts in multi-threaded mode | https://api.github.com/repos/MonetDB/MonetDB/issues/3214/comments | 0 | 2020-11-30T12:16:26Z | 2024-06-27T11:58:39Z | https://github.com/MonetDB/MonetDB/issues/3214 | 753,429,565 | 3,214 |
[
"MonetDB",
"MonetDB"
] | Date: 2012-12-25 14:05:12 +0100
From: @mlkersten
To: GDK devs <<bugs-common>>
Version: 11.17.9 (Jan2014)
Last updated: 2015-11-11 10:38:22 +0100
## Comment 18302
Date: 2012-12-25 14:05:12 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20100101 Firefox/17.0
Build Identifier:
The last few days I noticed a spurious crash in Q1 on sf10 with debugging compiled.
GDB attachment enabled me to get hold on it after a series of
runs.
A crash in strCMP due to invalid address coming from all the way
up from pqueue. No solution yet.
Switching to Thread 0x7fa423fff700 (LWP 20080)]
0x00007fa4c2d946d2 in strCmp (l=0x7fa33cfc8248 <Address 0x7fa33cfc8248 out of bounds>, r=0x7fa4c3233548 "\200") at /export/scratch1/mk/Feb2013//package/gdk/gdk_atoms.c:1037
1037 return GDK_STRCMP(l, r);
(gdb) where
0 0x00007fa4c2d946d2 in strCmp (l=0x7fa33cfc8248 <Address 0x7fa33cfc8248 out of bounds>, r=0x7fa4c3233548 "\200") at /export/scratch1/mk/Feb2013//package/gdk/gdk_atoms.c:1037
1 0x00007fa4c2e30ad9 in setcolprops (b=0x7fa3ec11ee40, col=0x7fa3ec11ef30, x=0x7fa33cfc8248) at /export/scratch1/mk/Feb2013//package/gdk/gdk_bat.c:1085
2 0x00007fa4c2e31bff in BUNins (b=0x7fa3ec11ee40, h=0x7fa3ec0f4320, t=0x7fa33cfc8248, force=0 '\000') at /export/scratch1/mk/Feb2013//package/gdk/gdk_bat.c:1225
3 0x00007fa4c37e25de in pqueue_enqueue_anymax (h=0x7fa3ec11ee40, idx=0x7fa3ec0f4320, el=0x7fa33cfc8248, tpe=12) at /export/scratch1/mk/Feb2013//package/monetdb5/modules/mal/pqueue.c:741
4 0x00007fa4c37e5cda in pqueue_utopn_anymax (H=0x7fa423ffe698, t=0x7fa3ec20e520, N=0x7fa423ffe6a0) at /export/scratch1/mk/Feb2013//package/monetdb5/modules/mal/pqueue.c:1020
5 0x00007fa4c37f32f1 in PQutopn2_anymax (ret=0x7fa4b01ac3f0, aid=0x7fa4b01ac170, bid=0x7fa4b01ac370, N=0x7fa4b01a8500) at /export/scratch1/mk/Feb2013//package/monetdb5/modules/mal/pqueue.c:1253
6 0x00007fa4c35cd837 in malCommandCall (stk=0x7fa4b01a6f60, pci=0x7fa4b01750c0) at /export/scratch1/mk/Feb2013//package/monetdb5/mal/mal_interpreter.c:150
7 0x00007fa4c35d002f in runMALsequence (cntxt=0xdaf8f8, mb=0x7fa4b15a7280, startpc=592, stoppc=593, stk=0x7fa4b01a6f60, env=0x0, pcicaller=0x0) at /export/scratch1/mk/Feb2013//package/monetdb5/mal/mal_interpreter.c:683
8 0x00007fa4c35d352c in DFLOWworker (t=0x7fa4c3abac98) at /export/scratch1/mk/Feb2013//package/monetdb5/mal/mal_dataflow.c:278
9 0x00000038f5607d90 in start_thread () from /lib64/libpthread.so.0
10 0x00000038f4af119d in clone () from /lib64/libc.so.6
(gdb) up
1 0x00007fa4c2e30ad9 in setcolprops (b=0x7fa3ec11ee40, col=0x7fa3ec11ef30, x=0x7fa33cfc8248) at /export/scratch1/mk/Feb2013//package/gdk/gdk_bat.c:1085
1085 atom_CMP(x, ATOMnilptr(col->type), col->type) == 0;
(gdb) up
1 0x00007fa4c2e30ad9 in setcolprops (b=0x7fa3ec11ee40, col=0x7fa3ec11ef30, x=0x7fa33cfc8248) at /export/scratch1/mk/Feb2013//package/gdk/gdk_bat.c:1085
1085 atom_CMP(x, ATOMnilptr(col->type), col->type) == 0;
(gdb)
2 0x00007fa4c2e31bff in BUNins (b=0x7fa3ec11ee40, h=0x7fa3ec0f4320, t=0x7fa33cfc8248, force=0 '\000') at /export/scratch1/mk/Feb2013//package/gdk/gdk_bat.c:1225
1225 setcolprops(b, b->T, t);
(gdb) l
1220 hsize = b->H->vheap->size;
1221 if (b->T->hash && b->T->vheap)
1222 tsize = b->T->vheap->size;
1223
1224 setcolprops(b, b->H, h);
1225 setcolprops(b, b->T, t);
1226
1227 if (!countonly) {
1228 bunfastins(b, h, t);
1229 } else {
(gdb) print *b->H
$4 = {id = 0x7fa4c323bf81 "h", width = 8, type = 6 '\006', shift = 3 '\003', varsized = 0, key = 1, dense = 1, nonil = 1, nil = 0, sorted = 1, revsorted = 1, align = 0, nokey = {0, 0}, nosorted = 0, norevsorted = 0,
nodense = 0, seq = 458, heap = {maxsize = 2048, free = 0, size = 2048, base = 0x7fa3ec148570 "P\205\024\354\243\177", filename = 0x7fa3ec1226d0 "74/7401.head", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM,
newstorage = STORE_MEM, dirty = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, props = 0x0}
(gdb) print *b->T
$5 = {id = 0x7fa4c323bf83 "t", width = 1, type = 12 '\f', shift = 0 '\000', varsized = 1, key = 0, dense = 0, nonil = 1, nil = 0, sorted = 1, revsorted = 1, align = 0, nokey = {0, 0}, nosorted = 0, norevsorted = 0,
nodense = 0, seq = 0, heap = {maxsize = 256, free = 0, size = 256,
base = 0x7fa3ec10ccb0 "\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333\333", <incomplete sequence \333>...,
filename = 0x7fa3ec0790f0 "74/7401.tail", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM, newstorage = STORE_MEM, dirty = 0 '\000', parentid = 0}, vheap = 0x7fa3ec0f49a0, hash = 0x0, props = 0x0}
(gdb) up
3 0x00007fa4c37e25de in pqueue_enqueue_anymax (h=0x7fa3ec11ee40, idx=0x7fa3ec0f4320, el=0x7fa33cfc8248, tpe=12) at /export/scratch1/mk/Feb2013//package/monetdb5/modules/mal/pqueue.c:741
741 BUNins(h, (ptr) idx, (ptr) el, FALSE);
(gdb) l
736 unsigned short ts;
737
738 hbase = BUNfirst(h);
739
740 posel = BATcount(h); /*last position */
741 BUNins(h, (ptr) idx, (ptr) el, FALSE);
742 ts = Tsize(h);
743 ins = hbase + posel;
744
745 while (posel > 0) {
(gdb) print posel
$6 = 0
(gdb) print (char *) el
$7 = 0x7fa33cfc8248 <Address 0x7fa33cfc8248 out of bounds>
(gdb) up
4 0x00007fa4c37e5cda in pqueue_utopn_anymax (H=0x7fa423ffe698, t=0x7fa3ec20e520, N=0x7fa423ffe6a0) at /export/scratch1/mk/Feb2013//package/monetdb5/modules/mal/pqueue.c:1020
1020 pqueue_enqueue_anymax(*H, idx, v, tpe);
(gdb) l
1015
1016 idx = (oid *) BUNhead(ti, BUNfirst(t));
1017 for (i = 0, j = 0; j < cnt && i < n; j++, idx++, q++) {
1018 v = BUNtail(ti, q);
1019 if ((p = BUNfnd(BATmirror(*H), v)) == BUN_NONE) {
1020 pqueue_enqueue_anymax(*H, idx, v, tpe);
1021 HASHdestroy(*H);
1022 BUNins(duplicates, idx, idx, FALSE);
1023 i++;
1024 } else {
(gdb) print q
$8 = 0
(gdb) print cnt
$9 = 2
$10 = {b = 0x7fa3ec20e520, hvid = 0, tvid = 0}
(gdb) print * ti.b
$11 = {batCacheid = 3584, H = 0x7fa3ec20e570, T = 0x7fa3ec20e610, P = 0x7fa3ec20e6b0, U = 0x7fa3ec20e6c8}
(gdb) print * ti.b->H
$12 = {id = 0x7fa4c323bf81 "h", width = 8, type = 6 '\006', shift = 3 '\003', varsized = 0, key = 0, dense = 0, nonil = 1, nil = 0, sorted = 0, revsorted = 0, align = 8859201, nokey = {0, 0}, nosorted = 4, norevsorted = 1,
nodense = 1, seq = 9223372036854775808, heap = {maxsize = 16, free = 16, size = 16, base = 0x7fa3ec0f4320 "\312\001", filename = 0x7fa3ec0f2a80 "74/7462.head", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM,
newstorage = STORE_MEM, dirty = 0 '\000', parentid = 3890}, vheap = 0x0, hash = 0x0, props = 0x0}
(gdb) print * ti.b-TH
No symbol "TH" in current context.
(gdb) print * ti.b->TH
There is no member named TH.
(gdb) print * ti.b->T
$13 = {id = 0x7fa4c323bf83 "t", width = 2, type = 12 '\f', shift = 1 '\001', varsized = 1, key = 0, dense = 0, nonil = 1, nil = 0, sorted = 0, revsorted = 0, align = 8859235, nokey = {0, 0}, nosorted = 0, norevsorted = 0,
nodense = 0, seq = 0, heap = {maxsize = 4, free = 4, size = 4, base = 0x7fa3ec20fb4c "H\002H\002\260", filename = 0x7fa3ec10fd70 "74/7462.tail", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM,
newstorage = STORE_MEM, dirty = 0 '\000', parentid = -3890}, vheap = 0xd80010, hash = 0x0, props = 0x0}
Reproducible: Sometimes
## Comment 21510
Date: 2015-11-11 10:38:22 +0100
From: @mlkersten
Not seen since submission. Considered closed.
| Spurious invalid string comparison | https://api.github.com/repos/MonetDB/MonetDB/issues/3213/comments | 0 | 2020-11-30T12:16:23Z | 2024-06-28T13:16:48Z | https://github.com/MonetDB/MonetDB/issues/3213 | 753,429,523 | 3,213 |
[
"MonetDB",
"MonetDB"
] | Date: 2012-12-21 22:59:40 +0100
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.15.1 (Feb2013)
Last updated: 2013-01-22 09:29:15 +0100
## Comment 18300
Date: 2012-12-21 22:59:40 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20100101 Firefox/17.0
Build Identifier:
Looking into the details of bug #3163, the concurrent user test, I was looking into this sequence using valgrind and the debugger, to understand why each call seems to be associated with an MAL optimizer stack call in the concurrent user stress test.
Tracing it shows that each query is added to the cache separately.
This is not the intended behavior.
The template is the same and there is just 1 plan needed.
See 3163 for database schema and queries.
CREATE TABLE "big_data" (
A INT,
B INT,
C INT,
D VARCHAR(100),
E VARCHAR(128),
F VARCHAR(8000),
G DATE,
H DATE,
I DATE
);
SELECT A, D from big_Data where B=820795733 AND E ='UlWsbzcHZi5lyJjJF9AYFRiZPZxjHqFZai6spMitOilLXw01ETUGx6J1HdFIUiHJxDMVx81aZbfme5bgyW4q5K7SiKDTvU9cV';
SELECT A, D from big_Data where B=2032992976 AND E ='lfZl2Z4m6M3JrXVxwnLC7ILfys3DKYwwVaTesVWSwYkCAxhgHiAc';
SELECT A, D from big_Data where B=1911160577 AND E ='wMGcxuHT7NvpOfjgPAVNWDu0r0lHVJkO0xQ18jPWMa5jAqyt7s35AElW6iwzUiwryVELYwkxgxA';
SELECT A, D from big_Data where B=2000084679 AND E ='MYOXO3fvKn0Tn0AWrB9AVNkZxfJTK2lUbgOXWbdxnUJstQM4R4y51srknkJfRCDOwYt9SM6dFLzVwBu7VfAsriPQzpMmzoogyJ5rgmaJVNC4oBb3XPe';
sql>select * from querycache();
+-----------------------------------------------------------------------------------------------------------------------------------------------------------+-------+
| query
| count |
+===========================================================================================================================================================+=======+
| select * from querycache();
| 1 |
| select a, d from big_data where b=1911160577 and e =\'wMGcxuHT7NvpOfjgPAVNWDu0r0lHVJkO0xQ18jPWMa5jAqyt7s35AElW6iwzUiwryVELYwkxgxA\'; | 1 |
| select a, d from big_data where b=2032992976 and e =\'lfZl2Z4m6M3JrXVxwnLC7ILfys3DKYwwVaTesVWSwYkCAxhgHiAc\'; | 1 |
| select a, d from big_data where b=820795733 and e =\'UlWsbzcHZi5lyJjJF9AYFRiZPZxjHqFZai6spMitOilLXw01ETUGx6J1HdFIUiHJxDMVx81aZbfme5bgyW4q5K7SiKDTvU9cV\'; | 1 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------+-------+
4 tuples (6.9s)
Reproducible: Always
### Steps to Reproduce:
Load the database of bug #3163 and executed a few of its queries.
A single client interaction suffices.
## Comment 18301
Date: 2012-12-21 23:06:57 +0100
From: @mlkersten
Changeset [206bbb53dad3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=206bbb53dad3) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=206bbb53dad3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=206bbb53dad3)
Changeset description:
Adding test for bug #3212
## Comment 18310
Date: 2012-12-27 22:14:04 +0100
From: @mlkersten
The bug seems resolved.
## Comment 18376
Date: 2013-01-22 09:29:15 +0100
From: @sjoerdmullender
Oct2012-SP3 has been released.
| Query cache does not work properly | https://api.github.com/repos/MonetDB/MonetDB/issues/3212/comments | 0 | 2020-11-30T12:16:20Z | 2024-06-27T11:58:37Z | https://github.com/MonetDB/MonetDB/issues/3212 | 753,429,490 | 3,212 |
[
"MonetDB",
"MonetDB"
] | Date: 2012-12-18 20:55:45 +0100
From: Percy Wegmann <<percy>>
To: SQL devs <<bugs-sql>>
Version: 11.13.5 (Oct2012-SP1)
CC: @njnes
Last updated: 2012-12-19 04:06:30 +0100
## Comment 18261
Date: 2012-12-18 20:55:45 +0100
From: Percy Wegmann <<percy>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11
Build Identifier:
This happens only when auto commit is off
Reproducible: Always
### Steps to Reproduce:
mclient -u monetdb -d click -a
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012-SP1)
Database: MonetDB v11.13.5.click1 (Oct2012-SP1), 'mapi:monetdb://percy-sandbox:50000/click'
Type \q to quit, \? for a list of available commands
auto commit mode: off
sql>CREATE TABLE autocommittest(id BIGINT);
operation successful (0.521ms)
sql>PREPARE SELECT * FROM autocommittest;
execute prepared statement using: EXEC 1(...)
+--------+--------+-------+--------+----------------+--------+
| type | digits | scale | schema | table | column |
+========+========+=======+========+================+========+
| bigint | 64 | 0 | | autocommittest | id |
+--------+--------+-------+--------+----------------+--------+
1 tuple (0.568ms)
sql>PREPARE SELECT * FROM autocommittest;
+----+
| id |
+====+
+----+
0 tuples (0.589ms)
sql>
### Actual Results:
The 2nd PREPARE returns the results of running the query rather than preparing it again
### Expected Results:
The 2nd PREPARE should return a handle to a new prepared statement, just as it does when auto-commit is on
## Comment 18263
Date: 2012-12-18 21:23:53 +0100
From: @njnes
We fixed something very similar recently, ie could you test oct2012-sp2?
## Comment 18274
Date: 2012-12-19 04:06:30 +0100
From: Percy Wegmann <<percy>>
Thanks Niels, this appears to be fixed on SP2.
percy@percy-sandbox:~$ mclient -u monetdb -d click -a
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012-SP2)
Database: MonetDB v11.13.7 (Oct2012-SP2), 'mapi:monetdb://percy-sandbox:50000/click'
Type \q to quit, \? for a list of available commands
auto commit mode: off
sql>CREATE TABLE autocommittest(id BIGINT);
operation successful (0.644ms)
sql>PREPARE SELECT * FROM autocommittest;
execute prepared statement using: EXEC 1(...)
+--------+--------+-------+--------+----------------+--------+
| type | digits | scale | schema | table | column |
+========+========+=======+========+================+========+
| bigint | 64 | 0 | | autocommittest | id |
+--------+--------+-------+--------+----------------+--------+
1 tuple (0.726ms)
sql>PREPARE SELECT * FROM autocommittest;
execute prepared statement using: EXEC 2(...)
+--------+--------+-------+--------+----------------+--------+
| type | digits | scale | schema | table | column |
+========+========+=======+========+================+========+
| bigint | 64 | 0 | | autocommittest | id |
+--------+--------+-------+--------+----------------+--------+
1 tuple (0.683ms)
sql>
| When auto commit is off, preparing the same query twice automatically runs the query the 2nd time it is prepared | https://api.github.com/repos/MonetDB/MonetDB/issues/3211/comments | 0 | 2020-11-30T12:16:18Z | 2024-06-28T13:16:47Z | https://github.com/MonetDB/MonetDB/issues/3211 | 753,429,465 | 3,211 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.