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"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6912/comments | 0 | 2020-11-30T16:58:44Z | 2020-11-30T16:58:45Z | https://github.com/MonetDB/MonetDB/issues/6912 | 753,643,881 | 6,912 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-23 18:21:26 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27875
Date: 2020-06-23 18:21:26 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Do this
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" ("c0" DECIMAL(18,3) NOT NULL);
COPY 41 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0.388
0.371
0.939
0.790
0.493
0.148
0.841
0.034
0.189
0.087
0.048
0.227
0.759
0.446
0.622
0.579
0.453
0.819
0.768
0.027
0.839
0.506
0.560
0.362
0.453
0.728
0.078
0.364
0.559
0.829
0.061
0.854
0.920
0.440
0.627
0.838
0.113
0.501
0.283
0.722
0.819
SELECT ALL ((- (- (VAR_POP(ALL ((CAST(CAST(abs(709845242) AS INT) AS INT))%(abs(CAST((931144491) NOT IN (-587881807) AS INT))))))))^(- (+ (- (char_length(r'>])')))))), 0.5186927954967299, CAST("locate"(lower(r'[]'), rtrim(r'..ۄUH*6鉡q'), ((((-233289450)&(-476676450)))-(- (236876413)))) AS INT)
FROM t0 WHERE FALSE GROUP BY 1.2807753E7 HAVING MAX(ALL ((t0.c0)>=(NULL)));
### Actual Results:
'calc.bit' undefined
### Expected Results:
Somthing
## Comment 27887
Date: 2020-06-30 16:23:14 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [890beb553c41](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=890beb553c41) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=890beb553c41](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=890beb553c41)
Changeset description:
Fix for bug #6911, ie never call exp_convert on any expression without knowing if it will be compatible with the output type.
Removed the superfluous exp_convert calls and moved rel_check_type to rel_exp.h and renamed it to exp_check_type to make it more widely available.
| SQLancer query: 'calc.bit' undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6911/comments | 0 | 2020-11-30T16:58:40Z | 2024-06-27T13:09:22Z | https://github.com/MonetDB/MonetDB/issues/6911 | 753,643,845 | 6,911 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-23 18:06:30 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-10-19 11:06:20 +0200
## Comment 27874
Date: 2020-06-23 18:06:30 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Run the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0("c0" DOUBLE NOT NULL);
COPY 11 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0
0.9440456550171384
0.3985168253176739
0.9033732171086648
0.969477015070214
-4798112
0.6321209051017095
0.7740272412444077
0.7778437505533593
0.34293653568934335
0.1228907839970418
SELECT AVG(ALL ((((CAST(((+ (-266455613))/(sql_min(-384923592, -684635832))) AS INT))+(abs(((1380859174)*(1039801791))))))*(((((greatest(1447838997, -1100245247))/(((((849535137)||(-1532296761)))/(CAST(t0.c0 AS INT))))))*(- (+ (((-291947972)*(626914646))))))))), 0.77785585904529674916574322196538560092449188232421875 FROM t0 WHERE (0.06276420221300283) NOT BETWEEN ASYMMETRIC (t0.c0) AND (t0.c0)
GROUP BY 0.135845384683200176567652306403033435344696044921875, 0.86688447, 0.3299475775341662586725988148828037083148956298828125, + (+ (- (length(r'q')))), greatest(upper(upper(r'623865997')), trim(replace(r'vAd(Lup}Z', r'-1774953973', r'0.4235712099498189'), substr(r'', -1963236744)));
### Actual Results:
Something
### Expected Results:
MAL undefined error.
## Comment 27876
Date: 2020-06-29 20:12:03 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [20f3bf441d1a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=20f3bf441d1a) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=20f3bf441d1a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=20f3bf441d1a)
Changeset description:
Major change. According to the SQL standard addition and subtraction between intervals and other number types is not allowed. The same applies for casting. This fixes bug #6910
| SQLancer query: 'bat.append' undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6910/comments | 0 | 2020-11-30T16:58:37Z | 2024-06-27T13:09:21Z | https://github.com/MonetDB/MonetDB/issues/6910 | 753,643,803 | 6,910 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-23 16:36:55 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27873
Date: 2020-06-23 16:36:55 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Run the statments bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" ("c0" BOOLEAN,"c1" DOUBLE PRECISION NOT NULL);
COPY 4 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
false 0.2059926383949241
NULL 1.89755202e+09
NULL 0.8514002985569765
NULL 0.8565135463082767
SELECT ALL t0.c0 FROM t0 WHERE (((0.654013919354451) BETWEEN SYMMETRIC (t0.c1) AND ("length"(upper(''))))OR(t0.c0));
### Actual Results:
empty
### Expected Results:
3 null values.
| SQLancer query with wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/6909/comments | 0 | 2020-11-30T16:58:33Z | 2024-06-27T13:09:20Z | https://github.com/MonetDB/MonetDB/issues/6909 | 753,643,756 | 6,909 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-17 16:59:03 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:15 +0200
## Comment 27865
Date: 2020-06-17 16:59:03 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Run the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0(c0 BOOLEAN,c1 CHAR(140));
COMMENT ON TABLE "sys"."t0" IS 'Kn䛺䛺r';
COPY 9 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
false "0.6481236457757975-2109927659"
NULL "-21099276590.48742518585365991"
false NULL
false NULL
false "heQhWJB<WMpPTuH⛿KZn6Gy|I[7nY*"
true "10626644390.31732346086015495"
true "붺Bu-夵jc"
true "-7416460080.4072199619164287325034012"
NULL "0.019193566362750714"
create view v0(c0) as (select distinct 0.4 from t0 where ((t0.c0)and((((lower(t0.c1))||(((((-69891801)/(1210439951)))+(cast(0.5895729273161221 as int)))))) between symmetric (cast(0.3 as string)) and (greatest(t0.c1, ((t0.c1)||(-2045486895)))))));
SELECT ALL v0.c0 FROM v0 CROSS JOIN t0 WHERE NOT (((((NOT (t0.c0))AND(t0.c0)))OR(((((((CAST(+ (((-498346404)*(1808267325))) AS BOOLEAN))OR(((((((((((((upper(t0.c1))<(t0.c1)))OR(t0.c0)))OR(t0.c0)))AND((v0.c0)
BETWEEN ASYMMETRIC (0.41195698232255074) AND (v0.c0))))OR(t0.c0)))OR(t0.c0)))))OR(NOT ((0.8823237) NOT IN (0.5788206, -351441275)))))AND(((0.149425566998711)<(v0.c0)))))));
| SQLancer inputs not the same size | https://api.github.com/repos/MonetDB/MonetDB/issues/6908/comments | 0 | 2020-11-30T16:58:30Z | 2024-06-27T13:09:19Z | https://github.com/MonetDB/MonetDB/issues/6908 | 753,643,724 | 6,908 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-17 16:39:50 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27864
Date: 2020-06-17 16:39:50 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Run the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0 (c0 BOOLEAN, c1 CHAR(140));
create view v0(c0) as (select distinct 0.4 from t0 where ((t0.c0)and((((lower(t0.c1))||(((((-69891801)/(1210439951)))+(cast(0.5895729273161221 as int))))))
between symmetric (cast(0.5 as string)) and (greatest(t0.c1, ((t0.c1)||(-2045486895)))))));
create view v1(c0, c1) as (select all 0.1, ((((cast(0.2 as int))/(+ (((((-212060493)*(816153822)))|(((2000022046)+(1143103273))))))))%(cast(cast(0.76693934 as int) as int))) from v0
group by 0.3, cast(- (cast(2.000022046E9 as int)) as boolean), sql_max(cast(cast(v0.c0 as string(336)) as int), length('1')), ((cast(0.19825737 as int))%(-1509376269)), v0.c0
having count(all (0.7) is not null) order by v0.c0 asc nulls first) with check option;
select all sum(all cast(t0.c0 as int)) as agg0 from v1 join t0 on cast(cast(v1.c1 as int) as boolean) where (v1.c1) not in (v1.c1, 0.36970723) is null;
| SQLancer algebra.select undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6907/comments | 0 | 2020-11-30T16:58:26Z | 2024-06-27T13:09:18Z | https://github.com/MonetDB/MonetDB/issues/6907 | 753,643,676 | 6,907 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-17 11:12:56 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27863
Date: 2020-06-17 11:12:56 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Build Identifier:
Run the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0("c0" DOUBLE PRECISION, "c1" VARCHAR(496));
create view v0(c0, c1) as (select all t0.c0, r'epfNW⟚榢tptPbC{5{ZW}6,R' from t0) with check option;
select sum(all + (cast(t0.c0 as int))) from v0 full outer join t0 on ((cast((cast(v0.c1 as boolean)) not in (true, ((t0.c0)=(t0.c0)), cast(1745166981 as boolean)) as string))ilike(v0.c0));
### Actual Results:
Crash
### Expected Results:
An output.
| SQLancer crash on complex join | https://api.github.com/repos/MonetDB/MonetDB/issues/6906/comments | 0 | 2020-11-30T16:58:23Z | 2024-06-27T13:09:17Z | https://github.com/MonetDB/MonetDB/issues/6906 | 753,643,635 | 6,906 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-16 18:33:01 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:15 +0200
## Comment 27861
Date: 2020-06-16 18:33:01 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the queries bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" ("c0" INTEGER,"c1" DOUBLE);
COPY 15 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
-1498252621 -1498252621
0 NULL
-539579569 -539579569
-108613919 NULL
0 0
8 NULL
1783007739 NULL
498706403 NULL
0 0.6103170716911988
1493854316 0.6198781779645515
-1608947797 1
1 0.8356779050811012
-101868623 0.16442926747225173
1493854316 -1498252621
1 0.9401903184230552
SELECT t0.c0 FROM t0 WHERE ((0.9952398693354088) IN (t0.c1, t0.c1)) IS NULL;
### Actual Results:
0
-539579569
0
8
1783007739
### Expected Results:
0
-108613919
8
1783007739
498706403
## Comment 27862
Date: 2020-06-17 11:03:54 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8b7b7e2b98e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8b7b7e2b98e8) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=8b7b7e2b98e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=8b7b7e2b98e8)
Changeset description:
Bug #6905 was fixed by recent changes
| SQLancer TLP query with wrong results 3 | https://api.github.com/repos/MonetDB/MonetDB/issues/6905/comments | 0 | 2020-11-30T16:58:19Z | 2024-06-27T13:09:16Z | https://github.com/MonetDB/MonetDB/issues/6905 | 753,643,598 | 6,905 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-16 18:29:36 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:15 +0200
## Comment 27860
Date: 2020-06-16 18:29:36 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the queries bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" ("c0" DOUBLE, "c1" VARCHAR(496));
COPY 20 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0.1438664733406536 NULL
0.1765302987566959 NULL
NULL "0.6278315174254069"
0.9937940991911638 "470810.02006337716"
0.925750874406328 " \\Z᳣s}LfFQk呗8Mßßl07VXpgoVDy\015'X\n}呗x逖n\015>⎑s%cQyIQ"
NULL "0.17744327397271142"
NULL "y"
NULL "緦좺VDOKB "
1511423462 "470810.02006337716"
0.5249207035059663 "470810.02006337716"
1 "470810.02006337716"
0.3762066043983153 "470810.02006337716"
-939120682 "c2lT^9BY0smjöA罀A&ß14_[*r"
0.522051822144801 "0.008675985"
0.5347718465897517 "c2lt^9by0smjöa罀a&ß14_[*r"
NULL "true"
NULL "-844489501"
NULL "0.44968215744290607"
NULL ".v"
NULL "-174251119"
SELECT ALL 0.1002352, AVG(ALL t0.c0) FROM t0 GROUP BY CAST(t0.c0 AS STRING(799)), 0.4665444117594173, ((sql_min(+ ("locate"('', 'F', 150648381)), ((((-1039870396)||(390810869)))*(length(r'u')))))>>(CAST(0.588018201374832 AS INT)));
### Actual Results:
aggr.subavg undefined
### Expected Results:
An output
| SQLancer aggr.subavg undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6904/comments | 0 | 2020-11-30T16:58:16Z | 2024-06-27T13:09:15Z | https://github.com/MonetDB/MonetDB/issues/6904 | 753,643,555 | 6,904 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-16 18:28:14 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27859
Date: 2020-06-16 18:28:14 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the queries bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" ("c0" DOUBLE, "c1" VARCHAR(496));
COPY 20 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0.1438664733406536 NULL
0.1765302987566959 NULL
NULL "0.6278315174254069"
0.9937940991911638 "470810.02006337716"
0.925750874406328 " \\Z᳣s}LfFQk呗8Mßßl07VXpgoVDy\015'X\n}呗x逖n\015>⎑s%cQyIQ"
NULL "0.17744327397271142"
NULL "y"
NULL "緦좺VDOKB "
1511423462 "470810.02006337716"
0.5249207035059663 "470810.02006337716"
1 "470810.02006337716"
0.3762066043983153 "470810.02006337716"
-939120682 "c2lT^9BY0smjöA罀A&ß14_[*r"
0.522051822144801 "0.008675985"
0.5347718465897517 "c2lt^9by0smjöa罀a&ß14_[*r"
NULL "true"
NULL "-844489501"
NULL "0.44968215744290607"
NULL ".v"
NULL "-174251119"
SELECT ALL CAST(VAR_SAMP(ALL abs(CAST(t0.c1 AS INT))) AS INT) FROM t0 GROUP BY CAST(t0.c1 AS INT), t0.c1;
### Actual Results:
calc.abs undefined
### Expected Results:
An output
| SQLancer calc.abs undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6903/comments | 0 | 2020-11-30T16:58:12Z | 2024-06-27T13:09:14Z | https://github.com/MonetDB/MonetDB/issues/6903 | 753,643,499 | 6,903 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-16 11:20:50 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:13 +0200
## Comment 27858
Date: 2020-06-16 11:20:50 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Runs the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "t0" ("c0" DOUBLE PRECISION NOT NULL,"c1" VARCHAR(64));
create view v0(c0, c1) as (select all t0.c0, r'epfNW⟚榢tptPbC{5{ZW}6,R' from t0) with check option;
SELECT v0.c0 FROM v0 WHERE (v0.c1) NOT BETWEEN SYMMETRIC (replace(CAST(CAST(v0.c0 AS INT) AS STRING), v0.c1, replace(CAST(0.1 AS STRING), v0.c1, v0.c1))) AND (v0.c1);
### Actual Results:
batcalc.between undefined error
### Expected Results:
empty result set.
| SQLancer query: batcalc.between undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/6902/comments | 0 | 2020-11-30T16:58:09Z | 2024-06-27T13:09:13Z | https://github.com/MonetDB/MonetDB/issues/6902 | 753,643,460 | 6,902 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-15 16:07:10 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27850
Date: 2020-06-15 16:07:10 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Runs the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "t0" ("c0" DOUBLE PRECISION NOT NULL,"c1" VARCHAR(64));
INSERT INTO "t0" VALUES (0.10155454782177964, 'FALSE'), (594212101, NULL), (0.5981662672233894, NULL);
SELECT t0.c0 FROM t0 WHERE CAST((0.3101399424332040855034620108199305832386016845703125) NOT IN (0.6446234112932121007588648353703320026397705078125) AS BOOLEAN);
### Actual Results:
Empty.
### Expected Results:
3 rows.
| SQLancer TLP query with wrong results 2 | https://api.github.com/repos/MonetDB/MonetDB/issues/6901/comments | 0 | 2020-11-30T16:58:06Z | 2024-06-27T13:09:12Z | https://github.com/MonetDB/MonetDB/issues/6901 | 753,643,408 | 6,901 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-15 15:25:02 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27848
Date: 2020-06-15 15:25:02 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the query bellow.
Reproducible: Always
### Steps to Reproduce:
select scale_down(-631218936, cast(0.41370374 as int));
### Actual Results:
SIGFPE signal.
### Expected Results:
Output something.
| SQLancer generated SIGFPE | https://api.github.com/repos/MonetDB/MonetDB/issues/6900/comments | 0 | 2020-11-30T16:58:03Z | 2024-06-27T13:09:11Z | https://github.com/MonetDB/MonetDB/issues/6900 | 753,643,370 | 6,900 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-15 13:47:57 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27846
Date: 2020-06-15 13:47:57 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements bellow.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "sys"."t0" (
"c0" DECIMAL(18,3),
"c1" DOUBLE
);
COPY 25 RECORDS INTO "sys"."t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0.861 0.6056174268361689
NULL 0.5542760880735715
0.566 0.5542760880735715
0.923 0.052316013908556114
0.162 0.5542760880735715
0.329 0.44073078327593473
0.662 0.5255985140328766
0.001 NULL
0.736 NULL
0.604 0.5394080603985286
0.988 NULL
0.232 0.23262100818671297
0.041 -7.386201860458207e+20
0.776 NULL
0.805 NULL
0.189 NULL
0.493 NULL
0.164 0.23262100818671297
0.316 0.6870041098637464
NULL 1.19449193e+09
NULL 0.5798864736610635
0.219 37
0.924 0.8488059445245933
0.413 0.6870041098637464
0.234 0
SELECT count(*) FROM t0 WHERE (NOT (CAST((t0.c1) IS NULL AS BOOLEAN))) IS NULL;
### Actual Results:
18
| SQLancer TLP query with wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/6899/comments | 0 | 2020-11-30T16:58:00Z | 2024-06-27T13:09:10Z | https://github.com/MonetDB/MonetDB/issues/6899 | 753,643,341 | 6,899 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-13 15:13:13 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27844
Date: 2020-06-13 15:13:13 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0 (c0 int, c1 int);
insert into t0 values (1, 1);
CREATE TABLE v0 (c0 int, c1 int);
insert into v0 values (1, 1);
select 1 from v0 join t0 on (((substr('1', 1, v0.c0)) || (1) in (1, t0.c0)) like 'a');
### Actual Results:
Crash at exp_bin
### Expected Results:
An empty result set.
| SQLancer crash on join query | https://api.github.com/repos/MonetDB/MonetDB/issues/6898/comments | 0 | 2020-11-30T16:57:57Z | 2024-06-27T13:09:09Z | https://github.com/MonetDB/MonetDB/issues/6898 | 753,643,310 | 6,898 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-13 14:37:56 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27843
Date: 2020-06-13 14:37:56 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "t0"("c0" DECIMAL(18,3), "c1" BIGINT);
COPY 12 RECORDS INTO "t0" FROM stdin USING DELIMITERS E'\t',E'\n','"';
0.244 NULL
0.578 NULL
0.119 NULL
0.773 495026350
0.329 2108706088
0.483 1298757529
0.880 39
0.084 1
0.332 859611948
0.607 NULL
0.835 0
0.455 -1239303309
SELECT MIN(DISTINCT t0.c1) FROM t0 WHERE 1 >= t0.c0 GROUP BY true;
### Actual Results:
GDK reported error: BATgroupminmax: BATgroupmin: b and g must be aligned
### Expected Results:
-1239303309
| SQLancer distinct aggregate with error on group by constant | https://api.github.com/repos/MonetDB/MonetDB/issues/6897/comments | 0 | 2020-11-30T16:57:54Z | 2024-06-27T13:09:08Z | https://github.com/MonetDB/MonetDB/issues/6897 | 753,643,258 | 6,897 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-13 14:23:15 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27842
Date: 2020-06-13 14:23:15 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t0 (a int, b int);
insert into t0 values (1,1);
select 1 from t0 where (3 in (1, 2)) is null;
### Actual Results:
TypeException:user.s42_0[22]:'algebra.select' undefined in: algebra.select(X_30:bat[:oid], X_32:bit, X_32:bit, true:bit, true:bit, false:bit);
### Expected Results:
Empty result set.
| SQLancer algebra.select' undefined 2 | https://api.github.com/repos/MonetDB/MonetDB/issues/6896/comments | 0 | 2020-11-30T16:57:50Z | 2024-06-27T13:09:07Z | https://github.com/MonetDB/MonetDB/issues/6896 | 753,643,207 | 6,896 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-12 16:52:26 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27836
Date: 2020-06-12 16:52:26 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the following statements
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE tbl_ProductSales (ColID int, Product_Category varchar(64), Product_Name varchar(64), TotalSales int);
INSERT INTO tbl_ProductSales VALUES (1,'Game','Mobo Game',200),(2,'Game','PKO Game',400),(3,'Fashion','Shirt',500),(4,'Fashion','Shorts',100);
CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
SELECT another_t.col1 FROM tbl_productsales CROSS JOIN another_t WHERE ((tbl_productsales.product_category) NOT IN (tbl_productsales.product_category, tbl_productsales.product_category)) IS NULL;
### Actual Results:
'algebra.select' undefined error
### Expected Results:
An empty result set.
| SQLancer causing 'algebra.select' undefined error | https://api.github.com/repos/MonetDB/MonetDB/issues/6895/comments | 0 | 2020-11-30T16:57:48Z | 2024-06-27T13:09:06Z | https://github.com/MonetDB/MonetDB/issues/6895 | 753,643,171 | 6,895 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-12 16:15:52 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:13 +0200
## Comment 27835
Date: 2020-06-12 16:15:52 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the query below.
Reproducible: Always
### Steps to Reproduce:
1. select rtrim('0.9407860360743894', '');
### Actual Results:
Assertion failure
### Expected Results:
0.9407860360743894
| SQLancer crash on rtrim function | https://api.github.com/repos/MonetDB/MonetDB/issues/6894/comments | 0 | 2020-11-30T16:57:44Z | 2024-06-27T13:09:05Z | https://github.com/MonetDB/MonetDB/issues/6894 | 753,643,125 | 6,894 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 17:38:42 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:13 +0200
## Comment 27830
Date: 2020-06-11 17:38:42 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE tbl_ProductSales (ColID int, Product_Category varchar(64), Product_Name varchar(64), TotalSales int);
INSERT INTO tbl_ProductSales VALUES (1,'Game','Mobo Game',200),(2,'Game','PKO Game',400),(3,'Fashion','Shirt',500),(4,'Fashion','Shorts',100);
CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
CREATE TABLE integers(i INTEGER);
INSERT INTO integers VALUES (1), (2), (3), (NULL);
create view v0(c0) as (select distinct - (tbl_productsales.totalsales) from tbl_productsales, another_t);
create view v1(c0) as (select distinct not (not ((((v0.c0)=(1560867215))) = false)) from integers, another_t, tbl_productsales, v0);
create view v2(c0, c1) as (select v1.c0, -3.025584E8 from v0, tbl_productsales, v1, another_t);
create view v3(c0, c1, c2) as (select all 0.9104878744438205107059047804796136915683746337890625, -705263737, 0.7147939 from v2 where (cast(v2.c0 as varchar(32))) is null order by v2.c1 desc, v2.c0 desc);
SELECT v3.c0 FROM v3, v0, tbl_productsales FULL OUTER JOIN v2 ON v2.c0 RIGHT OUTER JOIN integers ON (tbl_productsales.TotalSales) BETWEEN (NULL) AND (v2.c1) JOIN another_t ON v2.c0;
### Actual Results:
GDK reported error: joinparamcheck: BATrangejoin: right inputs not aligned.
### Expected Results:
An empty result set.
| SQLancer inner join reporting GDK error | https://api.github.com/repos/MonetDB/MonetDB/issues/6893/comments | 0 | 2020-11-30T16:57:41Z | 2024-06-27T13:09:04Z | https://github.com/MonetDB/MonetDB/issues/6893 | 753,643,085 | 6,893 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 17:10:55 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27828
Date: 2020-06-11 17:10:55 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the queries below
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE tbl_ProductSales (ColID int, Product_Category varchar(64), Product_Name varchar(64), TotalSales int);
INSERT INTO tbl_ProductSales VALUES (1,'Game','Mobo Game',200),(2,'Game','PKO Game',400),(3,'Fashion','Shirt',500),(4,'Fashion','Shorts',100);
CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
CREATE TABLE integers(i INTEGER);
INSERT INTO integers VALUES (1), (2), (3), (NULL);
SELECT another_T.col2 FROM tbl_productsales, integers LEFT OUTER JOIN another_T ON another_T.col1 > 1 WHERE another_T.col2 > 1 GROUP BY another_T.col2 HAVING COUNT((another_T.col2) IN (another_T.col2)) > 0;
### Actual Results:
Crash on MAL code generation
### Expected Results:
3 rows with values 2, 22 and 222.
## Comment 27829
Date: 2020-06-11 17:27:27 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e43797768bd2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e43797768bd2) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e43797768bd2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e43797768bd2)
Changeset description:
Extend SQL parser to allow predicates as function arguments, also fixed bug #6892 by setting expression names at anyequal rewriter
| SQLancer crash on query with HAVING | https://api.github.com/repos/MonetDB/MonetDB/issues/6892/comments | 0 | 2020-11-30T16:57:38Z | 2024-06-27T13:09:03Z | https://github.com/MonetDB/MonetDB/issues/6892 | 753,643,054 | 6,892 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 15:41:24 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-11-24 11:37:23 +0100
## Comment 27827
Date: 2020-06-11 15:41:24 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
Export of data to a file with extension .lz4 is currently not possible on Windows release. It returns an error.
Simularly files compressed with lz4 and extension .lz4 cannot be read as a decompressed csv/tsv file.
Add support for lz4 (de)compression on Windows by including liblz4.dll at installation (like done for libbz2.dll, zlib1.dll).
Sources and/or Binaries (lz4_win_v1_9_2.zip) kan be found at https://github.com/lz4/lz4/releases/tag/v1.9.2
Reproducible: Always
### Steps to Reproduce:
COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
-- succeeds
COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.lz4';
-- returns error
CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
-- succeeds
CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.lz4');
-- returns error
### Actual Results:
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
271 affected rows
sql>-- succeeds
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.lz4';
could not open file 'D:\MonetDB\Exports\tables.tsv.lz4': No such file or directory
sql>-- returns error
sql>
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
sql>-- succeeds
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.lz4');
GDK reported error: store_hot_snapshot: Failed to open D:\MonetDB\Backups\demodb.tar..tmp..lz4 for writing
sql>-- returns error
sql>
### Expected Results:
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
271 affected rows
sql>-- succeeds
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.lz4';
271 affected rows
sql>
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
sql>-- succeeds
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.lz4');
sql>-- succeeds
## Comment 28163
Date: 2020-10-14 18:07:36 +0200
From: Martin van Dinther <<martin.van.dinther>>
This has been successfully implemented in MonetDB v11.39.5 (Oct2020).
Related hg change: [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=fad7c1e666c8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=fad7c1e666c8)
| Add support of lz4 (de)compression on MS Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/6891/comments | 0 | 2020-11-30T16:57:34Z | 2024-06-27T13:09:02Z | https://github.com/MonetDB/MonetDB/issues/6891 | 753,643,022 | 6,891 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 15:25:07 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-11-24 11:37:23 +0100
## Comment 27826
Date: 2020-06-11 15:25:07 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
Export of data to a file with extension .xz is currently not possible on Windows release. It returns an error.
Simularly files compressed with xz and extension .xz cannot be read as a decompressed csv/tsv file.
Add support for xz/lzma (de)compression on Windows by including liblzma.dll at installation (like done for libbz2.dll, zlib1.dll).
Sources and/or Binaries (xz-5.2.5-windows.zip) kan be found at https://tukaani.org/xz/
Reproducible: Always
### Steps to Reproduce:
COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
-- succeeds
COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.xz';
-- returns error
CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
-- succeeds
CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.xz');
-- returns error
### Actual Results:
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
271 affected rows
sql>-- succeeds
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.xz';
could not open file 'D:\MonetDB\Exports\tables.tsv.xz': No such file or directory
sql>-- returns error
sql>
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
sql>-- succeeds
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.xz');
GDK reported error: store_hot_snapshot: Failed to open D:\MonetDB\Backups\demodb.tar..tmp..xz for writing
sql>-- returns error
### Expected Results:
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.gz';
271 affected rows
sql>COPY SELECT * FROM sys.tables ORDER BY name INTO R'D:\MonetDB\Exports\tables.tsv.xz';
271 affected rows
sql>
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.gz');
sql>-- succeeds
sql>CALL sys.hot_snapshot(R'D:\MonetDB\Backups\demodb.tar.xz');
sql>-- succeeds
## Comment 28162
Date: 2020-10-14 18:03:07 +0200
From: Martin van Dinther <<martin.van.dinther>>
This has been successfully implemented in MonetDB v11.39.5 (Oct2020).
Related hg change: [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=f0ea738f684a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=f0ea738f684a)
| Add support of xz/lzma (de)compression on MS Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/6890/comments | 0 | 2020-11-30T16:57:31Z | 2024-06-27T13:09:01Z | https://github.com/MonetDB/MonetDB/issues/6890 | 753,642,992 | 6,890 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 14:07:20 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27825
Date: 2020-06-11 14:07:20 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE tbl_ProductSales (ColID int, Product_Category varchar(64), Product_Name varchar(64), TotalSales int);
INSERT INTO tbl_ProductSales VALUES (1,'Game','Mobo Game',200),(2,'Game','PKO Game',400),(3,'Fashion','Shirt',500),(4,'Fashion','Shorts',100);
CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
CREATE TABLE integers(i INTEGER);
INSERT INTO integers VALUES (1), (2), (3), (NULL);
select all integers.i from another_t inner join integers on ((another_t.col3)<=(cast((another_t.col4) between symmetric (cast(0.29924480503501805 as int)) and (another_t.col3) as int)))
where true union all select all integers.i from another_t join integers on ((another_t.col3)<=(cast((another_t.col4) between symmetric (cast(0.29924480503501805 as int)) and (another_t.col3) as int)))
where not (true) union all select all integers.i from another_t join integers on ((another_t.col3)<=(cast((another_t.col4) between symmetric (cast(0.29924480503501805 as int)) and (another_t.col3) as int))) where (true) is null;
### Actual Results:
Crash on MAL code generation.
### Expected Results:
Empty result set.
| SQLancer crash on long query | https://api.github.com/repos/MonetDB/MonetDB/issues/6889/comments | 0 | 2020-11-30T16:57:28Z | 2024-06-27T13:09:00Z | https://github.com/MonetDB/MonetDB/issues/6889 | 753,642,967 | 6,889 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 12:14:28 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27823
Date: 2020-06-11 12:14:28 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE tbl_ProductSales (ColID int, Product_Category varchar(64), Product_Name varchar(64), TotalSales int);
INSERT INTO tbl_ProductSales VALUES (1,'Game','Mobo Game',200),(2,'Game','PKO Game',400),(3,'Fashion','Shirt',500),(4,'Fashion','Shorts',100);
CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
create view v0(c0) as (select distinct - (tbl_productsales.totalsales) from tbl_productsales, another_t);
select another_t.col1 from another_t, tbl_productsales cross join v0;
### Actual Results:
Crash in the MAL code generation
### Expected Results:
Query to successfully compile and give results.
## Comment 27824
Date: 2020-06-11 12:45:50 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [80b0f1dd338f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=80b0f1dd338f) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=80b0f1dd338f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=80b0f1dd338f)
Changeset description:
Fix for bug #6888, ie rel_remove_redundant_join optimizer cannot be applied to cross products
| SQLancer crash on cross join on view | https://api.github.com/repos/MonetDB/MonetDB/issues/6888/comments | 0 | 2020-11-30T16:57:25Z | 2024-06-27T13:08:59Z | https://github.com/MonetDB/MonetDB/issues/6888 | 753,642,922 | 6,888 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-11 09:43:34 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27820
Date: 2020-06-11 09:43:34 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the query below for a double free error
Reproducible: Always
### Steps to Reproduce:
1. SELECT "sys"."replace"(cast(cast(0.8009925043335998 as clob) as clob(169)),cast("sys"."replace"('!','','wtkg춑5,I}楘') as clob),"sys"."concat"("sys"."concat"('?dMHr펔2!FU4Rᔎ%',-1194732688),0.7566860950241294));
### Actual Results:
A double-free error.
### Expected Results:
Something besides a double-free error.
## Comment 27821
Date: 2020-06-11 10:28:54 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1dcaa2b1e5cb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1dcaa2b1e5cb) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1dcaa2b1e5cb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1dcaa2b1e5cb)
Changeset description:
Fix for bug #6887, handle NULL and empty strings properly at replace(string) function
| SQLancer crash on complex query | https://api.github.com/repos/MonetDB/MonetDB/issues/6887/comments | 0 | 2020-11-30T16:57:21Z | 2024-06-27T13:08:59Z | https://github.com/MonetDB/MonetDB/issues/6887 | 753,642,883 | 6,887 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-10 17:02:10 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27818
Date: 2020-06-10 17:02:10 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below:
Reproducible: Always
### Steps to Reproduce:
1. CREATE TABLE another_T (col1 INT, col2 INT, col3 INT, col4 INT, col5 INT, col6 INT, col7 INT, col8 INT);
2. INSERT INTO another_T VALUES (1,2,3,4,5,6,7,8), (11,22,33,44,55,66,77,88), (111,222,333,444,555,666,777,888), (1111,2222,3333,4444,5555,6666,7777,8888);
3. INSERT INTO another_t(col4) VALUES(-589206676), (-1557408577);
4. DELETE FROM another_t WHERE ((another_t.col8)<=(+ (another_t.col8)));
5. ALTER TABLE another_t ADD UNIQUE(col8, col1, col6, col3);
### Actual Results:
Can not create object error
### Expected Results:
The ALTER statement to succeed
| SQLancer alter table add unique gives strange error message | https://api.github.com/repos/MonetDB/MonetDB/issues/6886/comments | 0 | 2020-11-30T16:57:18Z | 2024-06-27T13:08:58Z | https://github.com/MonetDB/MonetDB/issues/6886 | 753,642,829 | 6,886 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-10 14:05:07 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27815
Date: 2020-06-10 14:05:07 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the query below for an assertion failure.
Reproducible: Always
### Steps to Reproduce:
1. insert into integers(i) values(((length(reverse('8 \rcr੧[bp1eMY쫺4j5s뮯!<Rn4*}')))>>(((- (- (528640982)))&(ascii('528640982'))))));
### Actual Results:
mserver5: ../../../../src/monetdb5/modules/atoms/str.c:2924: UTF8_assert: Assertion `0' failed.
### Expected Results:
I'm not sure, but the shift should be too large, so a runtime error should be thrown.
## Comment 27816
Date: 2020-06-10 14:57:04 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e4cb5e4c3341](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e4cb5e4c3341) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e4cb5e4c3341](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e4cb5e4c3341)
Changeset description:
Fix for bug #6885. Added support for UTF-8 strings at reverse(string) function
| SQLancer causes assertion error on UTF8_strlen | https://api.github.com/repos/MonetDB/MonetDB/issues/6885/comments | 0 | 2020-11-30T16:57:15Z | 2024-06-27T13:08:57Z | https://github.com/MonetDB/MonetDB/issues/6885 | 753,642,798 | 6,885 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-10 12:16:51 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:14 +0200
## Comment 27813
Date: 2020-06-10 12:16:51 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the queries below to get a strange error message.
Reproducible: Always
### Steps to Reproduce:
1. CREATE TABLE t0 (a1 INT, a2 int, a3 int);
2. UPDATE t0 SET a2 = (- (- (t0.a1))), a3 = (ascii(CAST(ascii('}悂Y8K*韖5<c>^n8_X1X|p(''bX') AS STRING(920)))) WHERE NOT (((0.27023923567918073) NOT IN (0.9149447665258329)) = FALSE);
### Actual Results:
!42000 error message
### Expected Results:
0 rows updated.
| SQLancer generates query with unclear error message | https://api.github.com/repos/MonetDB/MonetDB/issues/6884/comments | 0 | 2020-11-30T16:57:13Z | 2024-06-27T13:08:56Z | https://github.com/MonetDB/MonetDB/issues/6884 | 753,642,760 | 6,884 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-10 09:10:52 +0200
From: @PedroTadim
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:13 +0200
## Comment 27810
Date: 2020-06-10 09:10:52 +0200
From: @PedroTadim
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Run the statements below to reproduce the crash.
Reproducible: Always
### Steps to Reproduce:
1. CREATE TABLE integers(i INTEGER);
2. INSERT INTO integers VALUES (1), (2), (3), (NULL);
3. delete from integers where (((0.7161494983624688) in (integers.i)) = true) = false;
### Actual Results:
Crash on the MAL code generation.
### Expected Results:
3 deleted rows (rows with values 1,2,3)
## Comment 27812
Date: 2020-06-10 11:09:34 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [82d510745c09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=82d510745c09) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=82d510745c09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=82d510745c09)
Changeset description:
Approved output, since bug #6883 has been fixed
| SQLancer crash on delete query | https://api.github.com/repos/MonetDB/MonetDB/issues/6883/comments | 0 | 2020-11-30T16:57:10Z | 2024-06-27T13:08:55Z | https://github.com/MonetDB/MonetDB/issues/6883 | 753,642,726 | 6,883 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-09 17:56:49 +0200
From: @swingbit
To: GDK devs <<bugs-common>>
Version: 11.35.19 (Nov2019-SP3)
CC: @yzchang
Last updated: 2020-07-27 09:30:10 +0200
## Comment 27805
Date: 2020-06-09 17:56:49 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36
Build Identifier:
In a system with 24GiB of RAM, MonetDB is run in Docker with memlimit=16g.
What Docker does is setting cgroups limits.
Starting from Apr2019, MonetDB reads those limits and uses them as caps for the resources it is allowed to use.
I remember testing that. mserver5 would report exactly the memory as limited by docker (thus: by cgroup). That seems to no longer be happening:
This is from inside the docker container.
cgroups limits memory to 16GiB, but MonetDB sees 24GiB:
cat /sys/fs/cgroup/memory/memory.limit_in_bytes
17179869184
/opt/monetdb/bin/mserver5 --version
MonetDB 5 server 11.35.20 (64-bit, 128-bit integers)
This is an unreleased version
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2020 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 23.5GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.43 2019-02-23
openssl: OpenSSL 1.1.1d FIPS 10 Sep 2019
libxml2: 2.9.9
Compiled by: @634c8f6244bd (x86_64-pc-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wundef -Wformat=2 -Wformat-overflow=1 -Wno-format-truncation -Wno-format-nonliteral -Wno-cast-function-type -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wno-missing-field-initializers -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 -Wduplicated-cond -Wduplicated-branches -Wrestrict -Wnested-externs -Wno-char-subscripts -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
Reproducible: Always
## Comment 27806
Date: 2020-06-09 18:16:31 +0200
From: @sjoerdmullender
Are you sure mserver5 --version reported the limit before? I doubt it. The version information is printed very early on and then the server exits. It doesn't go through the code that initializes all these memory variables.
What does mserver5 say without the --version argument?
## Comment 27807
Date: 2020-06-09 18:31:44 +0200
From: @swingbit
Yes, at some point is was visible:
cat /sys/fs/cgroup/memory/memory.limit_in_bytes
2147483648
/opt/monetdb/bin/mserver5 --version
MonetDB 5 server 11.33.12 (64-bit, 128-bit integers)
This is an unreleased version
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2019 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 2.0GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.43 2019-02-23
openssl: OpenSSL 1.1.1c FIPS 28 May 2019
libxml2: 2.9.9
Compiled by: @a9e9f9e384d5 (x86_64-pc-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wundef -Wformat=2 -Wformat-overflow=1 -Wno-format-truncation -Wno-format-nonliteral -Wno-cast-function-type -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wno-missing-field-initializers -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 -Wduplicated-cond -Wduplicated-branches -Wrestrict -Wnested-externs -Wno-char-subscripts -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
Another clue that the limit is not actually set is that more and more often we see MonetDB that is OOM-killed as soon as it reached the max memory allowed, with still plenty of swap and disk space. If the limits were set correctly, it should be way more difficult to reach that moment.
## Comment 27808
Date: 2020-06-09 18:36:04 +0200
From: @swingbit
Also, starting mserver5 without --version (so, actually starting the default database, gives the same memory information)
## Comment 27831
Date: 2020-06-12 12:14:35 +0200
From: @swingbit
I compared again a Nov2019 system with a Apr2019 system.
On a Nov2019 (11.35.20) with 24G of system RAM:
cgroups limits it to 12G
[root@9f334da3261c /] cat /sys/fs/cgroup/memory/memory.limit_in_bytes
12884901888
20G are available
sql>select * from env() where name = 'gdk_mem_maxsize';
+-----------------+-------------+
| name | value |
+=================+=============+
| gdk_mem_maxsize | 20603770839 |
+-----------------+-------------+
1 tuple
On a Apr2019 (11.33.12) with 32G of system RAM:
cgroups limits it to 2G
[root@4b5f37cbd7c9 /] cat /sys/fs/cgroup/memory/memory.limit_in_bytes
2147483648
1.6G are available:
sql>select * from env() where name = 'gdk_mem_maxsize';
+-----------------+------------+
| name | value |
+=================+============+
| gdk_mem_maxsize | 1750199173 |
+-----------------+------------+
1 tuple
## Comment 27832
Date: 2020-06-12 12:18:53 +0200
From: @swingbit
I see this in the Nov2019 release notes:
Added "vmmaxsize" and "memmaxsize" mserver5 options to the daemon in order to set mserver5's maximum virtual and committed memory respectively.
Just a guess, perhaps when these re not explicitly set their default values replace anyway what found in cgroups settings?
## Comment 27833
Date: 2020-06-12 14:47:19 +0200
From: @yzchang
Those options were introduced as extra safeguard and convenience.
We try to find, e.g., CGroups limitations set on mserver5, but we don't always succeed, because the location of the CGroups information can sometimes be hard to determine.
Afaik, we take the minimum of CGroups limitations (if we can find them) and the values of "vmmaxsize" and "memmaxsize" (if set). The actual max sizes for vm and mem are printed in the mserver5 start-up msg, especially if they are less than the system's overall resources.
## Comment 27834
Date: 2020-06-12 15:38:16 +0200
From: @sjoerdmullender
What might help me find the issue is if you could run mserver5 under strace. I'm interested in the output of
strace -s 1024 mserver5 --version
starting with the opening of the file /proc/self/mountinfo until the end. (You can use the strace -o option to save the output to a file.)
## Comment 27837
Date: 2020-06-12 17:38:52 +0200
From: @swingbit
Created attachment 682
Output of strace
> Attached file: [strace.out](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6882_strace.out_682) (text/plain, 50603 bytes)
> Description: Output of strace
## Comment 27838
Date: 2020-06-12 17:40:53 +0200
From: @swingbit
Apparently it doesn't find them:
openat(AT_FDCWD, "/sys/fs/cgroup/memory/docker/2951843bb482c7502f1c9e1ab8b5de271f6eac75ef227d5949c175e4b6687612/memory.limit_in_bytes", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/fs/cgroup/memory/docker/2951843bb482c7502f1c9e1ab8b5de271f6eac75ef227d5949c175e4b6687612/memory.soft_limit_in_bytes", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/fs/cgroup/memory/docker/2951843bb482c7502f1c9e1ab8b5de271f6eac75ef227d5949c175e4b6687612/memory.memsw.limit_in_bytes", O_RDONLY) = -1 ENOENT (No such file or directory)
## Comment 27839
Date: 2020-06-12 17:43:08 +0200
From: @swingbit
What is strange is that the /docker structure should not be visible (it isn't) from inside the docker container, but only from the host.
The docker container only sees /sys/fs/cgroup/memory/memory.limit_in_bytes
## Comment 27840
Date: 2020-06-12 17:51:45 +0200
From: @swingbit
Created attachment 683
Trace output of 11.33.12 (works)
> Attached file: [strace.11.33.12.out](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6882_strace.11.33.12.out_683) (text/plain, 47671 bytes)
> Description: Trace output of 11.33.12 (works)
## Comment 27841
Date: 2020-06-12 17:52:19 +0200
From: @swingbit
11.33.12 doesn't look into the /docker structure
## Comment 27845
Date: 2020-06-15 11:00:55 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [5495166fbc3c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5495166fbc3c) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=5495166fbc3c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=5495166fbc3c)
Changeset description:
Try harder to find a cgroup v1 control file.
This should fix bug #6882.
## Comment 27847
Date: 2020-06-15 14:44:11 +0200
From: @swingbit
Back-ported to Nov2019 and tested, the fix works.
## Comment 27849
Date: 2020-06-15 15:57:18 +0200
From: @sjoerdmullender
Great. Thanks for testing.
| cgroups limits no longer respected? | https://api.github.com/repos/MonetDB/MonetDB/issues/6882/comments | 0 | 2020-11-30T16:57:07Z | 2024-06-27T13:08:54Z | https://github.com/MonetDB/MonetDB/issues/6882 | 753,642,680 | 6,882 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-09 11:25:50 +0200
From: Arshad <<arshad.super>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @njnes
Last updated: 2020-08-25 13:57:55 +0200
## Comment 27802
Date: 2020-06-09 11:25:50 +0200
From: Arshad <<arshad.super>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Build Identifier:
Drop Table with "Cascade" followed by update table results in "ParseException" followed by a crash under sql_trans_drop_all_dependencies().
GDB Back trace from the core.
(gdb) bt
0 0x00007f22c4a95271 in sql_trans_drop_all_dependencies (tr=0x6cd21b0, id=164953, type=COLUMN_DEPENDENCY) at store.c:4526
1 0x00007f22c4a962c3 in sys_drop_column (tr=0x6cd21b0, col=0xaa11970, drop_action=2) at store.c:4757
2 0x00007f22c4a96448 in sys_drop_columns (tr=0x6cd21b0, t=0xaa11800, drop_action=2) at store.c:4798
3 0x00007f22c4a967e3 in sys_drop_table (tr=0x6cd21b0, t=0xaa11800, drop_action=2) at store.c:4852
4 0x00007f22c4a9bd7f in sql_trans_drop_table (tr=0x6cd21b0, s=0x6e307c0, id=164999, drop_action=2) at store.c:5838
5 0x00007f22c49e626b in mvc_drop_table (m=0x7f22080099a0, s=0x6e307c0, t=0xaa11800, drop_action=1) at sql_mvc.c:1433
6 0x00007f22c494ecdd in drop_table (sql=0x7f22080099a0, sname=0x7f2208040ec0 "MRT_P6",
tname=0x7f2208041810 "Table1", drop_action=1, if_exists=0) at sql_cat.c:539
7 0x00007f22c495230e in SQLdrop_table (cntxt=0x7f22c5260020, mb=0x7f22080402c0, stk=0x7f22080418c0, pci=0x7f2208042550)
at sql_cat.c:1124
8 0x00007f22d6e4304d in runMALsequence (cntxt=0x7f22c5260020, mb=0x7f22080402c0, startpc=1, stoppc=0, stk=0x7f22080418c0,
env=0x0, pcicaller=0x0) at mal_interpreter.c:654
9 0x00007f22d6e41ace in runMAL (cntxt=0x7f22c5260020, mb=0x7f22080402c0, mbcaller=0x0, env=0x0) at mal_interpreter.c:335
10 0x00007f22c4929d7c in SQLrun (c=0x7f22c5260020, be=0x7f2208001bd0, m=0x7f22080099a0) at sql_execute.c:385
11 0x00007f22c492b133 in SQLengineIntern (c=0x7f22c5260020, be=0x7f2208001bd0) at sql_execute.c:752
12 0x00007f22c49281b6 in SQLengine (c=0x7f22c5260020) at sql_scenario.c:1365
13 0x00007f22d6e62acf in runPhase (c=0x7f22c5260020, phase=4) at mal_scenario.c:517
14 0x00007f22d6e62c13 in runScenarioBody (c=0x7f22c5260020, once=0) at mal_scenario.c:543
15 0x00007f22d6e62dfb in runScenario (c=0x7f22c5260020, once=0) at mal_scenario.c:575
16 0x00007f22d6e64847 in MSserveClient (c=0x7f22c5260020) at mal_session.c:504
17 0x00007f22d6e643b4 in MSscheduleClient (command=0x7f22080008d0 "", challenge=0x7f2215eb6c90 "ojrzAT6w", fin=0x7f22080028f0,
fout=0x7f2210002b50, protocol=PROTOCOL_9, blocksize=8190) at mal_session.c:382
18 0x00007f22d6f070cb in doChallenge (data=0x7f22100008d0) at mal_mapi.c:267
---Type <return> to continue, or q <return> to quit---
19 0x00007f22d6a08b97 in THRstarter (a=0x7f2210004c40) at gdk_utils.c:1558
20 0x00007f22d6a6fc0f in thread_starter (arg=0x7f2210004cd0) at gdk_system.c:657
21 0x00007f22d431fe25 in start_thread (arg=0x7f2215eb7700) at pthread_create.c:308
22 0x00007f22d404d34d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb)
logs
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: update sys.functions set system = true where name in ('master', 'stopmaster', 'masterbeat', 'masterclock', 'mastertick', 'replicate', 'replicabeat', 'replicaclock', 'replicatick') and schema_id = (select id from sys.schemas where name = 'sys');
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: UPDATE sys._tables
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: SET system = true
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: WHERE name = 'comments'
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: AND schema_id = (SELECT id FROM sys.schemas WHERE name = 'sys');
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: set schema "sys";
2020-06-08 10:59:00 MSG PROD_2_DB[136676]:
2020-06-08 10:59:00 ERR PROD_2_DB[136676]: main thread:!ERROR:ParseException:SQLparser:3F000!CREATE PROCEDURE: external name wlc.stopmaster not bound (sys.stopmaster)
2020-06-08 10:59:00 ERR PROD_2_DB[136676]: !ParseException:SQLparser:3F000!CREATE PROCEDURE: external name wlc.stopmaster not bound (sys.stopmaster)
2020-06-08 10:59:00 MSG PROD_2_DB[136676]: MonetDB/SQL module loaded
2020-06-09 00:29:49 MSG merovingian[287426]: proxying client 10.106.36.35:45764 for database 'PROD_2_DB' to mapi:monetdb:///monet_data01/DBFARM_TSV_PROD_2/PROD_2_DB/.mapi.sock?database=PROD_2_DB
2020-06-09 00:29:49 MSG merovingian[287426]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2020-06-09 00:29:54 MSG merovingian[287426]: database 'PROD_2_DB' (136676) has crashed (dumped core)
2020-06-09 00:30:34 MSG merovingian[287426]: database 'PROD_2_DB' has crashed after start on 2020-06-08 10:58:58, attempting restart, up min/avg/max: 1s/2d/3w, crash average: 1.00 1.00 0.60 (27-9=18)
2020-06-09 00:30:34 MSG merovingian[287426]: proxying client 10.106.36.35:45766 for database 'PROD_2_DB' to mapi:monetdb:///monet_data01/DBFARM_TSV_PROD_2/PROD_2_DB/.mapi.sock?database=PROD_2_DB
Reproducible: Always
### Steps to Reproduce:
1. drop table IF EXISTS "Table1" cascade;
2. CREATE TABLE "Table1" ( VG_DIM_KEY INTEGER NOT NULL PRIMARY KEY , S_743613_KEY INTEGER DEFAULT 30000 , S_743614_KEY INTEGER DEFAULT 30000 , S_743615_KEY INTEGER DEFAULT 30000 , S_743616 INTEGER DEFAULT 30000 , S_743616_KEY INTEGER DEFAULT 30000 , S_743618 INTEGER DEFAULT 30000 , S_743618_KEY INTEGER DEFAULT 30000 , S_743650 FLOAT(14, 1) DEFAULT 30000 , S_743650_KEY INTEGER DEFAULT 30000 , S_743651 INTEGER DEFAULT 30000 , S_743651_KEY INTEGER DEFAULT 30000 , S_743652 INTEGER DEFAULT 30000 , S_743652_KEY INTEGER DEFAULT 30000 , S_743653_KEY INTEGER DEFAULT 30000 , S_743654_KEY INTEGER DEFAULT 30000 , S_743655_KEY INTEGER DEFAULT 30000 , S_743656_KEY INTEGER DEFAULT 30000 , S_743657 FLOAT(11, 1) DEFAULT 30000 , S_743657_KEY INTEGER DEFAULT 30000 , S_743658 INTEGER DEFAULT 30000 , S_743658_KEY INTEGER DEFAULT 30000 , S_743660_KEY INTEGER DEFAULT 30000 , S_743680 INTEGER DEFAULT 30000 , S_743680_KEY INTEGER DEFAULT 30000 , S_743681_KEY INTEGER DEFAULT 30000 , S_743682_KEY INTEGER DEFAULT 30000 , S_743683 INTEGER DEFAULT 30000 , S_743683_KEY INTEGER DEFAULT 30000 , S_743684_KEY INTEGER DEFAULT 30000 , S_743685_KEY INTEGER DEFAULT 30000 , S_743686_KEY INTEGER DEFAULT 30000 , S_743687_KEY INTEGER DEFAULT 30000 , S_743688 INTEGER DEFAULT 30000 , S_743688_KEY INTEGER DEFAULT 30000 , S_743689 INTEGER DEFAULT 30000 , S_743689_KEY INTEGER DEFAULT 30000 , S_743690_KEY INTEGER DEFAULT 30000 , S_743691_KEY INTEGER DEFAULT 30000 , S_743692 INTEGER DEFAULT 30000 , S_743692_KEY INTEGER DEFAULT 30000 , S_743693 INTEGER DEFAULT 30000 , S_743693_KEY INTEGER DEFAULT 30000 , S_743694_KEY INTEGER DEFAULT 30000 );
### Actual Results:
core dump.
### Expected Results:
Actual Table drop and recreate
## Comment 27921
Date: 2020-07-20 17:29:56 +0200
From: @sjoerdmullender
Was this database by any chance upgraded from an earier version of MonetDB?
## Comment 27922
Date: 2020-07-20 17:54:35 +0200
From: @sjoerdmullender
To add to my comment, from the error message that I see in the beginning of the log that you quoted I can see that the upgrade of the database didn't work.
In fact, part of the update was not run because of the error mentioning sys.stopmaster. That may well be the reason why you get the error with your own commands.
## Comment 27944
Date: 2020-07-27 09:00:40 +0200
From: Arshad <<arshad.super>>
Hi Sjoerd,
>Was this database by any chance upgraded from an earier version of MonetDB?
After talking with our test team. It was indeed the case. Please go ahead and close this issue for now. Will re-open as we hit this in fresh load or a proper upgrade.
Thanks for pointing out the correct direction!!!
Arshad
| Crash (core dump) after main thread:!ERROR:ParseException:SQLparser:3F000!CREATE PROCEDURE: external name wlc.stopmaster not bound (sys.stopmaster) | https://api.github.com/repos/MonetDB/MonetDB/issues/6881/comments | 0 | 2020-11-30T16:57:02Z | 2024-06-28T13:07:50Z | https://github.com/MonetDB/MonetDB/issues/6881 | 753,642,623 | 6,881 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-09 11:18:20 +0200
From: xavier <<wysunxavier>>
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
CC: @PedroTadim
Last updated: 2020-07-27 09:30:13 +0200
## Comment 27800
Date: 2020-06-09 11:18:20 +0200
From: xavier <<wysunxavier>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36
Build Identifier:
Using 200 million pieces of data for query, the left fuzzy query takes longer than other query statements.
SQL 1：select * from t1 where id like '%584049';
SQL 2: select * from t1 where id like '%170711%';
For example, full fuzzy query(SQL 2) returns a result set of 5000+, which takes 386ms,.However, it takes 915ms for the left fuzzy query to return 59 results.
Reproducible: Always
### Steps to Reproduce:
1.select * from t1 where id like '%584049';
### Actual Results:
The concurrent execution of left fuzzy query performance is more obvious.
Is there any way to improve the performance of left fuzzy queries?
## Comment 27803
Date: 2020-06-09 11:46:42 +0200
From: @PedroTadim
Hello xavier,
We have been fixing the optimization of simple like expressions this past week. Expressions such as '%584049' will use a faster route on Jun2020-SP1 release.
Best regards,
Pedro
## Comment 27809
Date: 2020-06-10 03:32:41 +0200
From: xavier <<wysunxavier>>
Thanks.
Looking forward to the new version.
Best wishes，
Xavier.
| Left fuzzy queries are much slower than other fuzzy queries. | https://api.github.com/repos/MonetDB/MonetDB/issues/6880/comments | 0 | 2020-11-30T16:56:58Z | 2024-06-27T13:08:51Z | https://github.com/MonetDB/MonetDB/issues/6880 | 753,642,575 | 6,880 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-09 05:10:54 +0200
From: Trung Le <<tle211212>>
To: clients devs <<bugs-clients>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-06-11 04:10:16 +0200
## Comment 27796
Date: 2020-06-09 05:10:54 +0200
From: Trung Le <<tle211212>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36
Build Identifier:
When I try to connect to Monetdb with the hostname of BI_business-intelligence, I get the following exception.
java.sql.SQLNonTransientConnectionException: Invalid URL: no hostname given or unparsable in 'jdbc:monetdb://BI_business-intelligence:50000/ebiz_olap?language=sql'
at nl.cwi.monetdb.jdbc.MonetDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.fahasa.aoe.db.DatabaseOlap$1.doIt(DatabaseOlap.java:56)
at com.fahasa.aoe.db.DatabaseOlap$1.doIt(DatabaseOlap.java:46)
at com.fahasa.aoe.utils.OperationUtils.doWithRetry(OperationUtils.java:70)
at com.fahasa.aoe.db.DatabaseOlap.initConnection(DatabaseOlap.java:46)
at com.fahasa.aoe.Main.main(Main.java:90)
However if I use business-intelligence as hostname, the code works. (Both BI_business-intelligence and business-intelligence are the same machine)
The expected behavior is that the code should work fine with hostname of BI_business-intelligence
Reproducible: Always
## Comment 27799
Date: 2020-06-09 10:53:13 +0200
From: @PedroTadim
Hello Trung,
We use the java URI class to parse the URI string in the jdbc connection string. After looking at this JVM bug:
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6587184
and the hostname definition: https://en.wikipedia.org/wiki/HostnameRestrictions_on_valid_host_names
I found out underscores are not allowed in hostnames. I'm afraid there's nothing we can do on the JDBC driver side.
## Comment 27819
Date: 2020-06-11 04:10:16 +0200
From: Trung Le <<tle211212>>
Thanks for your detailed explanation. I agree this is not a MonetDB bug. I will try to find a workaround for my problem. (docker swarm uses host name convention: <docker stack name>_<server name>).
| MonetDB JDBC throws exception if hostname contains underscore | https://api.github.com/repos/MonetDB/MonetDB/issues/6879/comments | 0 | 2020-11-30T16:56:56Z | 2024-06-28T13:07:49Z | https://github.com/MonetDB/MonetDB/issues/6879 | 753,642,541 | 6,879 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-08 15:01:05 +0200
From: mkj280
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
CC: martin.van.dinther, @PedroTadim
Last updated: 2020-10-19 11:06:22 +0200
## Comment 27795
Date: 2020-06-08 15:01:05 +0200
From: mkj280
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Build Identifier:
I noticed that everytime I run a SELECT query with AND statement, it causes the following error:
failed
Connection to server lost! (mserver5 still alive?)
This error not only occurs from JDBC but also running it in mclient. Thie error DID NOT occur on the 11.35.19 version, but on the recent 11.37.7 version.
Reproducible: Always
### Steps to Reproduce:
1.CREATE TABLE temp_table(norm_min float, norm_max float, min float, max float);
2.INSERT INTO temp_table VALUES (0.0,0.17424371009,6.0,12.25);
3.INSERT INTO temp_table VALUES (0.17424371009,0.2865480811,12.5,18.5);
4.INSERT INTO temp_table VALUES (0.2865480811,0.7201958679,18.5,24.75);
5.INSERT INTO temp_table VALUES (0.7201958679,1.0,24.75,31.0);
6.CREATE TABLE temp_table(norm_min float, norm_max float, min float, max float);
7.INSERT INTO temp_value VALUES (rand()/2147483648.0);
8.INSERT INTO temp_value VALUES (rand()/2147483648.0);
9.INSERT INTO temp_value VALUES (rand()/2147483648.0);
10.INSERT INTO temp_value VALUES (rand()/2147483648.0);
11.INSERT INTO temp_value VALUES (rand()/2147483648.0);
12.INSERT INTO temp_value VALUES (rand()/2147483648.0);
13.INSERT INTO temp_value VALUES (rand()/2147483648.0);
14.INSERT INTO temp_value VALUES (rand()/2147483648.0);
15.INSERT INTO temp_value VALUES (rand()/2147483648.0);
16.INSERT INTO temp_value VALUES (rand()/2147483648.0);
17.select (rand()/2147483648.0)*(temp_table.max - temp_table.min)+temp_table.min from temp_value, temp_table where temp_value.value<=temp_table.norm_max and temp_value.value>temp_table.norm_min;
### Actual Results:
failed
Connection to server lost! (mserver5 still alive?)
### Expected Results:
It should run, and produce values that meet the parameter discussed in the select statement.
## Comment 27798
Date: 2020-06-09 09:41:22 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c723ea6fb21f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c723ea6fb21f) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c723ea6fb21f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c723ea6fb21f)
Changeset description:
Added test for bug #6878
## Comment 27801
Date: 2020-06-09 11:22:04 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c281b315a126](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c281b315a126) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c281b315a126](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c281b315a126)
Changeset description:
Add a missing candidate iterator reset.
This fixes bug #6878.
## Comment 28093
Date: 2020-09-17 01:34:58 +0200
From: Martin van Dinther <<martin.van.dinther>>
Changed Product and Component classification. It was not a problem of the JDBC client interface (or mclient program), but of the SQL processing on the server.
| SQL Connection Error when running SELECT queries containing AND command | https://api.github.com/repos/MonetDB/MonetDB/issues/6878/comments | 0 | 2020-11-30T16:56:53Z | 2024-06-27T13:08:49Z | https://github.com/MonetDB/MonetDB/issues/6878 | 753,642,509 | 6,878 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-04 11:36:30 +0200
From: @joerivanruth
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27792
Date: 2020-06-04 11:36:30 +0200
From: @joerivanruth
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Build Identifier:
The files are not properly terminated with an end marker.
Reproducible: Always
### Steps to Reproduce:
$ mclient -d foo -s "call sys.hot_snapshot(r'/tmp/demo1.tar.lz4')"
$ lz4 -d </tmp/demo1.tar.lz4 | wc -c
Error 68 : Unfinished stream
3961856
$ mclient -d foo
Welcome to mclient, the MonetDB/SQL interactive terminal (Jun2020)
Database: MonetDB v11.37.7 (Jun2020), 'mapi:monetdb://hank:50000/foo'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE foo(i INTEGER);
operation successful
sql>INSERT INTO foo SELECT * FROM sys.generate_series(0,1000);
1000 affected rows
sql>COPY SELECT * FROM foo INTO '/tmp/demo2.tar.lz4' ON CLIENT;
1000 affected rows
sql>
$ lz4 -d </tmp/demo2.tar.lz4 | wc -c
Error 68 : Unfinished stream
3890
### Actual Results:
Error 68 : Unfinished stream
### Expected Results:
No errors
| MonetDB produces malformed LZ4 files | https://api.github.com/repos/MonetDB/MonetDB/issues/6877/comments | 0 | 2020-11-30T16:56:49Z | 2024-06-27T13:08:48Z | https://github.com/MonetDB/MonetDB/issues/6877 | 753,642,471 | 6,877 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-04 11:34:21 +0200
From: @joerivanruth
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27791
Date: 2020-06-04 11:34:21 +0200
From: @joerivanruth
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Build Identifier:
The generated tar files have only one 512-byte block of zeroes at the end, should be two.
Reproducible: Always
### Steps to Reproduce:
Welcome to mclient, the MonetDB/SQL interactive terminal (Jun2020)
Database: MonetDB v11.37.7 (Jun2020), 'mapi:monetdb://hank:50000/foo'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>call sys.hot_snapshot('/tmp/demo.tar');
sql>
$ cd /tmp
$ tar xf demo.tar
tar: A lone zero block at 7752
### Expected Results:
No warning
| tar files created by sys.hot_snapshot() produce warnings on some implementations of tar | https://api.github.com/repos/MonetDB/MonetDB/issues/6876/comments | 0 | 2020-11-30T16:56:46Z | 2024-06-27T13:08:47Z | https://github.com/MonetDB/MonetDB/issues/6876 | 753,642,439 | 6,876 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-04 11:25:24 +0200
From: @joerivanruth
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Duplicates: #6873
Last updated: 2020-06-04 11:30:07 +0200
## Comment 27785
Date: 2020-06-04 11:25:24 +0200
From: @joerivanruth
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36
Build Identifier:
If the write-ahead log becomes so large that it consists of multiple files,
only the last file is included in the snapshot.
Reproducible: Always
### Steps to Reproduce:
The attached python script can be used to reproduce. Invoke it as follows:
./demo.py /tmp/demo 150M
This is what happens:
- the script starts an mserver and opens two concurrent connections.
- connection1 creates a table, adds some data, commits, observes the
data it added and adds some more, uncommitted data
- connection2 observes the committed data and repeatedly adds lots of additional
data which it commits
- because connection1 is still ongoing, the committed data ends up in
the write ahead log which becomes spread over multiple files because
it's so large. In my example, the log consists of the files log.4
and log.5.
- hot_snapshot creates a snapshot containing only log.5
- when starting the snapshot, log.4 is missing and log.5 is ignored so
we lose data
### Actual Results:
This is the output of the script on my system:
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Agent 1: DROP TABLE IF EXISTS foo
0.002s (0.002s total)
Agent 1: CREATE TABLE foo(i BIGINT)
0.002s (0.004s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 1)
0.003s (0.007s total)
Agent 1: COMMIT
0.011s (0.018s total)
Agent 1: SELECT COUNT(*) FROM foo
==> 1
0.003s (0.018s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 33)
0.002s (0.020s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 1
0.002s (0.020s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
2.033s (2.052s total)
Agent 2: COMMIT
1.428s (3.480s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
3.329s (6.809s total)
Agent 2: COMMIT
1.858s (8.667s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 100)
2.105s (10.772s total)
Agent 2: COMMIT
1.282s (12.053s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 300000101
0.001s (12.053s total)
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.4 2400001006
log.5 524288
Starting snapshot
Agent 2: CALL sys.hot_snapshot(r'/tmp/demo/snap.tar')
0.454s (12.507s total)
Killing server
Deleting database dir
Restoring snapshot
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.5 524288
Restarting server
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Counting restored rows
Agent 3: SELECT COUNT(*) FROM foo
MonetDB Error: SELECT: no such table 'foo'
### Expected Results:
After restoring the snapshot, table 'foo' should exist and have 300000101 rows.
## Comment 27788
Date: 2020-06-04 11:30:07 +0200
From: @joerivanruth
*** This bug has been marked as a duplicate of bug #6873 ***
| sys.hot_snapshot() creates incomplete snapshots if the write-ahead log is very large | https://api.github.com/repos/MonetDB/MonetDB/issues/6875/comments | 0 | 2020-11-30T16:56:42Z | 2024-06-28T13:07:49Z | https://github.com/MonetDB/MonetDB/issues/6875 | 753,642,396 | 6,875 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-04 11:18:25 +0200
From: @joerivanruth
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Duplicates: #6873
Last updated: 2020-06-04 11:29:54 +0200
## Comment 27784
Date: 2020-06-04 11:18:25 +0200
From: @joerivanruth
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Build Identifier:
If the write-ahead log becomes so large that it consists of multiple files,
only the last file is included in the snapshot.
Reproducible: Always
### Steps to Reproduce:
The attached python script can be used to reproduce. Invoke it as follows:
./demo.py /tmp/demo 150M
This is what happens:
- the script starts an mserver and opens two concurrent connections.
- connection1 creates a table, adds some data, commits, observes the
data it added and adds some more, uncommitted data
- connection2 observes the committed data and repeatedly adds lots of additional
data which it commits
- because connection1 is still ongoing, the committed data ends up in
the write ahead log which becomes spread over multiple files because
it's so large. In my example, the log consists of the files log.4
and log.5.
- hot_snapshot creates a snapshot containing only log.5
- when starting the snapshot, log.4 is missing and log.5 is ignored so
we lose data
### Actual Results:
This is the output of the script on my system:
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Agent 1: DROP TABLE IF EXISTS foo
0.002s (0.002s total)
Agent 1: CREATE TABLE foo(i BIGINT)
0.002s (0.004s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 1)
0.003s (0.007s total)
Agent 1: COMMIT
0.011s (0.018s total)
Agent 1: SELECT COUNT(*) FROM foo
==> 1
0.003s (0.018s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 33)
0.002s (0.020s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 1
0.002s (0.020s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
2.033s (2.052s total)
Agent 2: COMMIT
1.428s (3.480s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
3.329s (6.809s total)
Agent 2: COMMIT
1.858s (8.667s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 100)
2.105s (10.772s total)
Agent 2: COMMIT
1.282s (12.053s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 300000101
0.001s (12.053s total)
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.4 2400001006
log.5 524288
Starting snapshot
Agent 2: CALL sys.hot_snapshot(r'/tmp/demo/snap.tar')
0.454s (12.507s total)
Killing server
Deleting database dir
Restoring snapshot
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.5 524288
Restarting server
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Counting restored rows
Agent 3: SELECT COUNT(*) FROM foo
MonetDB Error: SELECT: no such table 'foo'
### Expected Results:
After restoring the snapshot, table 'foo' should exist and have 300000101 rows.
## Comment 27786
Date: 2020-06-04 11:29:54 +0200
From: @joerivanruth
*** This bug has been marked as a duplicate of bug #6873 ***
| sys.hot_snapshot() creates incomplete snapshots if the write-ahead log is very large | https://api.github.com/repos/MonetDB/MonetDB/issues/6874/comments | 0 | 2020-11-30T16:56:39Z | 2024-06-28T13:07:48Z | https://github.com/MonetDB/MonetDB/issues/6874 | 753,642,364 | 6,874 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-04 11:17:58 +0200
From: @joerivanruth
To: SQL devs <<bugs-sql>>
Version: 11.37.7 (Jun2020)
Last updated: 2020-07-27 09:30:11 +0200
## Comment 27783
Date: 2020-06-04 11:17:58 +0200
From: @joerivanruth
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Build Identifier:
If the write-ahead log becomes so large that it consists of multiple files,
only the last file is included in the snapshot.
Reproducible: Always
### Steps to Reproduce:
The attached python script can be used to reproduce. Invoke it as follows:
./demo.py /tmp/demo 150M
This is what happens:
- the script starts an mserver and opens two concurrent connections.
- connection1 creates a table, adds some data, commits, observes the
data it added and adds some more, uncommitted data
- connection2 observes the committed data and repeatedly adds lots of additional
data which it commits
- because connection1 is still ongoing, the committed data ends up in
the write ahead log which becomes spread over multiple files because
it's so large. In my example, the log consists of the files log.4
and log.5.
- hot_snapshot creates a snapshot containing only log.5
- when starting the snapshot, log.4 is missing and log.5 is ignored so
we lose data
### Actual Results:
This is the output of the script on my system:
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Agent 1: DROP TABLE IF EXISTS foo
0.002s (0.002s total)
Agent 1: CREATE TABLE foo(i BIGINT)
0.002s (0.004s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 1)
0.003s (0.007s total)
Agent 1: COMMIT
0.011s (0.018s total)
Agent 1: SELECT COUNT(*) FROM foo
==> 1
0.003s (0.018s total)
Agent 1: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 33)
0.002s (0.020s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 1
0.002s (0.020s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
2.033s (2.052s total)
Agent 2: COMMIT
1.428s (3.480s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 150000000)
3.329s (6.809s total)
Agent 2: COMMIT
1.858s (8.667s total)
Agent 2: INSERT INTO foo SELECT 42 FROM sys.generate_series(0, 100)
2.105s (10.772s total)
Agent 2: COMMIT
1.282s (12.053s total)
Agent 2: SELECT COUNT(*) FROM foo
==> 300000101
0.001s (12.053s total)
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.4 2400001006
log.5 524288
Starting snapshot
Agent 2: CALL sys.hot_snapshot(r'/tmp/demo/snap.tar')
0.454s (12.507s total)
Killing server
Deleting database dir
Restoring snapshot
Contents of /tmp/demo/foo/sql_logs/sql:
log [4] 10
log.5 524288
Restarting server
Starting ['mserver5', '--dbpath=/tmp/demo/foo', '--set', 'mapi_port=50000']
Counting restored rows
Agent 3: SELECT COUNT(*) FROM foo
MonetDB Error: SELECT: no such table 'foo'
### Expected Results:
After restoring the snapshot, table 'foo' should exist and have 300000101 rows.
## Comment 27787
Date: 2020-06-04 11:29:54 +0200
From: @joerivanruth
*** Bug #6874 has been marked as a duplicate of this bug. ***
## Comment 27789
Date: 2020-06-04 11:30:07 +0200
From: @joerivanruth
*** Bug #6875 has been marked as a duplicate of this bug. ***
## Comment 27790
Date: 2020-06-04 11:31:43 +0200
From: @joerivanruth
Created attachment 681
python script that demonstrates the issue
> Attached file: [demo.py](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6873_demo.py_681) (text/x-python, 9280 bytes)
> Description: python script that demonstrates the issue
| sys.hot_snapshot() creates incomplete snapshots if the write-ahead log is very large | https://api.github.com/repos/MonetDB/MonetDB/issues/6873/comments | 0 | 2020-11-30T16:56:36Z | 2024-06-27T13:08:44Z | https://github.com/MonetDB/MonetDB/issues/6873 | 753,642,315 | 6,873 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6872/comments | 0 | 2020-11-30T16:56:33Z | 2020-11-30T16:56:35Z | https://github.com/MonetDB/MonetDB/issues/6872 | 753,642,284 | 6,872 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-06-02 21:45:05 +0200
From: wei.yao
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: martin.van.dinther, @njnes
Last updated: 2020-09-09 14:07:43 +0200
## Comment 27736
Date: 2020-06-02 21:45:05 +0200
From: wei.yao
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Build Identifier:
Hello,
by comparing two databases with same physical resources, environment, data:
one newly load the data, is working
one got error message with complex query: could not allocate space.
They should have enough physical resources to perform complex query.
We noticed in the non-working database, in the system table sys.storage, some attributes (unique, sorted, revsorted) are flipped from true to null, or false to true. One noticeable change is the primary key unique attribute is changed from true to null, although when query count(*) in the table there're no duplicate primary key id.
Could this unique of primary key id result this 'could not allocate space' error when trying complex query?
Thanks,
Reproducible: Always
### Actual Results:
schema | table | column | type | count | typewidth | columnsize | sorted | revsorted | unique |
+========+===============+=================================+===========+==========+==========+==========+===========+============+=============+========+=======+==========+========+===========+========+==========+
| sys | annotation | annotation_id | int | 48094 | 4 | 192376 | true | false | null |
| sys | annotation | annotation_id_pkey | oid | 0 | 8 | 0 | true | true | null |
| sys | annotation | annotation_label_fkey | oid | 48094 | 8 | 384752 | null | null | null |
| sys | annotation | annotation_tile_fkey | oid | 48094 | 8 | 384752 | false | false | null |
## Comment 27737
Date: 2020-06-02 21:52:46 +0200
From: wei.yao
Here's a concise table, for better view:
schema | table | column | sorted | revsorted | unique |
+========+===============+=================================+===========+==========+==========+==========+===========+============+=============+========+=======+==========+========+===========+========+==========+
| sys | annotation | annotation_id | true | false | null |
| sys | annotation | annotation_id_pkey | true | true | null |
| sys | annotation | annotation_label_fkey | null | null | null |
| sys | annotation | annotation_tile_fkey | false | false | null |
## Comment 27781
Date: 2020-06-03 11:45:02 +0200
From: Martin van Dinther <<martin.van.dinther>>
Could you supply us with DDL statement(s) to recreate the table(s) and some data rows to check what the storage properties should be?
It could be that when the table was created in an older version (pre Nov2019) and that the properties were not correctly updated in the newer software version.
Therefore it is a good idea/procedure to make an SQL dump (using msqldump program) before upgrading the software. After upgrading the software to a major new version start with an empty database and next recreate the database using the SQL dump script.
See: https://www.monetdb.org/Documentation/UserGuide/DumpRestore
## Comment 27782
Date: 2020-06-03 11:58:38 +0200
From: Martin van Dinther <<martin.van.dinther>>
Are you using the same software version for the 2 databases? If not, it could be the reason why you see differences in sys.storage.
Also check if there is data in sys.statistics. Maybe it is outdated. If so remove it or rerun analyze 'schema name' command to update the statistics in both databases.
Next rerun the complex query to see if there is a difference.
If not, share the complex query (and needed table definitions).
| sys.storage unique attribute changes for primary key | https://api.github.com/repos/MonetDB/MonetDB/issues/6871/comments | 0 | 2020-11-30T16:56:30Z | 2024-06-27T13:08:43Z | https://github.com/MonetDB/MonetDB/issues/6871 | 753,642,243 | 6,871 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-30 07:50:15 +0200
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @PedroTadim
Last updated: 2020-10-19 11:06:19 +0200
## Comment 27734
Date: 2020-05-30 07:50:15 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:76.0) Gecko/20100101 Firefox/76.0
Build Identifier:
The mgbench example illustrated missing bulk operators for:
mtime.{year, month,hours, dayofweek,...}
str.{substring, locate, replace}
They should be added to avoid 100s M of function calls.
Reproducible: Always
## Comment 28076
Date: 2020-09-14 11:44:03 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [923a2addb76f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=923a2addb76f) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=923a2addb76f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=923a2addb76f)
Changeset description:
Implemented remaining missing bulk implementations for string functions. This closes bug #6870.
| Missing bulk operators | https://api.github.com/repos/MonetDB/MonetDB/issues/6870/comments | 0 | 2020-11-30T16:56:27Z | 2024-06-27T13:08:42Z | https://github.com/MonetDB/MonetDB/issues/6870 | 753,642,206 | 6,870 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6869/comments | 0 | 2020-11-30T16:56:25Z | 2020-11-30T16:56:26Z | https://github.com/MonetDB/MonetDB/issues/6869 | 753,642,167 | 6,869 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6868/comments | 0 | 2020-11-30T16:56:22Z | 2020-11-30T16:56:24Z | https://github.com/MonetDB/MonetDB/issues/6868 | 753,642,129 | 6,868 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6867/comments | 0 | 2020-11-30T16:56:19Z | 2020-11-30T16:56:21Z | https://github.com/MonetDB/MonetDB/issues/6867 | 753,642,099 | 6,867 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6866/comments | 0 | 2020-11-30T16:56:16Z | 2020-11-30T16:56:18Z | https://github.com/MonetDB/MonetDB/issues/6866 | 753,642,062 | 6,866 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-20 21:24:48 +0200
From: Ariel <<aabadi>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
Duplicates: #6864
Last updated: 2020-05-20 22:11:12 +0200
## Comment 27723
Date: 2020-05-20 21:24:48 +0200
From: Ariel <<aabadi>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Build Identifier:
We started with ILIKE '%guate%' it found 7 records, then we changed to ILIKE '%guate%com% it found 1 record (which is ok)... finally we changed to ILIKE '%guate%mo%com%' and now it didn't find anything :'(
Please see the attached examples...
A) sql>SELECT DISTINCT nts_area_name
FROM sb_rmsv.nts_nt_sum_report
WHERE nts_area_name ILIKE '%guate%';
+---------------------------+
| nts_area_name |
+===========================+
| Guatemala |
| Guatemala-Mobile |
| Guatemala-Mobile Comcel |
| Guatemala-Mobile Movistar |
| Guatemala-Mobile PCS |
| Guatemala-Telgua |
| Guatemala-Telefonica |
+---------------------------+
B) sql>SELECT DISTINCT nts_area_name
FROM sb_rmsv.nts_nt_sum_report
WHERE nts_area_name ILIKE '%guate%com%;
+-------------------------+
| nts_area_name |
+=========================+
| Guatemala-Mobile Comcel |
+-------------------------+
C) sql>SELECT DISTINCT nts_area_name
FROM sb_rmsv.nts_nt_sum_report
WHERE nts_area_name ILIKE '%guate%mo%com%';
+---------------+
| nts_area_name |
+===============+
+---------------+
0 tuples
Another user has reported that the problem is based on the dash "-"
Reproducible: Always
### Steps to Reproduce:
1.There is a value on a table such "Guatemala-Mobile Comcel"
2.SELECT WHERE field ILIKE '%guate%mo%com%'. does NOT work
3.
### Actual Results:
Create a table with one string field
Insert the value "Guatemala-Mobile Comcel"
run the query with the where clause.
### Expected Results:
the value should appear, but it doesnt.
it must show the inserted string.
## Comment 27724
Date: 2020-05-20 22:11:12 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #6864 ***
| ILIKE Operator. Bad function | https://api.github.com/repos/MonetDB/MonetDB/issues/6865/comments | 0 | 2020-11-30T16:56:13Z | 2024-06-28T13:07:47Z | https://github.com/MonetDB/MonetDB/issues/6865 | 753,642,019 | 6,865 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-20 10:13:42 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: aabadi
Last updated: 2020-06-03 16:58:53 +0200
## Comment 27720
Date: 2020-05-20 10:13:42 +0200
From: @sjoerdmullender
In certain cases, (I)LIKE doesn't match strings that should match.
With these strings and using ILIKE:
Guatemala
Guatemala-Mobile
Guatemala-Mobile Comcel
Guatemala-Mobile Movistar
Guatemala-Mobile PCS
Guatemala-Telgua
Guatemala-Telefonica
the pattern '%guate%mo%com%' should match one value, but it matches none.
The pattern '%guate%com%' does match the one value it should.
## Comment 27721
Date: 2020-05-20 10:14:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [6ee8bd513f65](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6ee8bd513f65) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=6ee8bd513f65](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=6ee8bd513f65)
Changeset description:
Fix for bug #6864.
## Comment 27722
Date: 2020-05-20 11:36:44 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [619c4a6d52ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=619c4a6d52ba) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=619c4a6d52ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=619c4a6d52ba)
Changeset description:
Added test and output for bug #6864
## Comment 27725
Date: 2020-05-20 22:11:12 +0200
From: @sjoerdmullender
*** Bug #6865 has been marked as a duplicate of this bug. ***
| (I)LIKE with multiple % doen't find matches | https://api.github.com/repos/MonetDB/MonetDB/issues/6864/comments | 0 | 2020-11-30T16:56:09Z | 2024-06-27T13:08:38Z | https://github.com/MonetDB/MonetDB/issues/6864 | 753,641,977 | 6,864 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-12 17:13:06 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @yzchang
Last updated: 2020-06-09 12:07:56 +0200
## Comment 27704
Date: 2020-05-12 17:13:06 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Build Identifier:
In the following:
- I trigger the creation of a hash on a column.
- I verify that the thash file is written on disk
- I drop the table
- I verify that all the column files are deleted, except the thash file
sql>create table t(s string);
operation successful
sql>copy into t from '100kuuids.txt' on client;
100000 affected rows
-- no thash file yet
sql>select schema,table,column,location,count,hashes,phash from sys.storage('sys','t');
+--------+-------+--------+----------+--------+--------+-------+
| schema | table | column | location | count | hashes | phash |
+========+=======+========+==========+========+========+=======+
| sys | t | s | 06/600 | 100000 | 0 | false |
+--------+-------+--------+----------+--------+--------+-------+
1 tuple
-rw-------. 1 roberto roberto 448K May 12 17:01 06/600.tail
-rw-------. 1 roberto roberto 3.8M May 12 17:02 06/600.theap
-- this select triggers the creation of a hash on column t.s
sql>select * from t where s='e40ee8bd-9a6b-4c4e-b8a2-c103aa1a0aa3';
+--------------------------------------+
| s |
+======================================+
| e40ee8bd-9a6b-4c4e-b8a2-c103aa1a0aa3 |
+--------------------------------------+
1 tuple
sql>select schema,table,column,location,count,hashes,phash from sys.storage('sys','t');
+--------+-------+--------+----------+--------+--------+-------+
| schema | table | column | location | count | hashes | phash |
+========+=======+========+==========+========+========+=======+
| sys | t | s | 06/600 | 100000 | 983088 | false |
+--------+-------+--------+----------+--------+--------+-------+
1 tuple
-rw-------. 1 roberto roberto 448K May 12 17:01 06/600.tail
-rw-------. 1 roberto roberto 1.0M May 12 17:03 06/600.thash
-rw-------. 1 roberto roberto 3.8M May 12 17:02 06/600.theap
sql>drop table t;
operation successful
-rw-------. 1 roberto roberto 1.0M May 12 17:03 06/600.thash
The leftover thash file is deleted only on a server restart.
The issue is that these files can be rather large and this becomes not workable very quickly in a scenario where the server needs to stay up for a long time and data are regularly replaced (tables dropped/created).
Reproducible: Always
## Comment 27705
Date: 2020-05-12 17:16:46 +0200
From: @yzchang
Hai Roberto,
Just very quickly:
- do you still have the hash file after letting mserver5 "rest" for some time?
- do you still have the hash file after restarting mserver5?
=> i.e. mserver5 doesn't clean up the hash file in any of its later clean up actions.
## Comment 27706
Date: 2020-05-12 17:28:04 +0200
From: @swingbit
Hi Jennie,
The thash file stays there indefinitely if not restarting.
It is removed at the next mserver5 restart.
## Comment 27707
Date: 2020-05-12 17:40:39 +0200
From: @yzchang
thanks. at least we got it right by restart. but it should have been removed by drop table. i'm going to test this in the RC Jun2020.
## Comment 27708
Date: 2020-05-12 19:00:27 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c174d01fcc3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c174d01fcc3f) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c174d01fcc3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c174d01fcc3f)
Changeset description:
Destroy index files when a BAT is destroyed.
This should fix bug #6863.
## Comment 27709
Date: 2020-05-12 19:58:10 +0200
From: @swingbit
I've back-ported the fix to Nov2019 and tried.
Unfortunately I don't see any difference. The thash file stays won't be removed.
## Comment 27710
Date: 2020-05-12 20:20:52 +0200
From: @sjoerdmullender
You should only need the change in gdk_storage.c, not the one in gdk_hash.c.
I did see some different behavior when I was testing, but I couldn't put my finger on it. What I did, did fix it in at least one test I did.
## Comment 27711
Date: 2020-05-12 20:25:12 +0200
From: @swingbit
Yes! That was it.
I reverted the change in gdk_hash.c nd now it works as expected.
Thanks
## Comment 27804
Date: 2020-06-09 12:07:56 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3d1bffd73ea2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3d1bffd73ea2) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=3d1bffd73ea2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=3d1bffd73ea2)
Changeset description:
Destroy index files when a BAT is destroyed.
This should fix bug #6863.
| thash files not released upon drop table | https://api.github.com/repos/MonetDB/MonetDB/issues/6863/comments | 0 | 2020-11-30T16:56:05Z | 2024-06-27T13:08:37Z | https://github.com/MonetDB/MonetDB/issues/6863 | 753,641,929 | 6,863 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-11 10:45:03 +0200
From: Arshad <<arshad.super>>
To: GDK devs <<bugs-common>>
Version: 11.35.19 (Nov2019-SP3)
CC: @mlkersten, @njnes, renalkoclok
Last updated: 2020-07-27 09:09:13 +0200
## Comment 27701
Date: 2020-05-11 10:45:03 +0200
From: Arshad <<arshad.super>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36
Build Identifier:
Hi,
While executing our test-case where max_clients is set to 2048. mserver5 segfaults while executing update_table(). Our reproducer is very lengthy forking more than thousands of threads where there is great number of table create/update. We are trying to narrow down the reproducer and strip it to bare minimal so we can share it later or provide more info on this.
I have not seen this under Bug history either. Does this call to mind anything which we are missing. ? What scenario update_table() will fault which executing lib_sql.so ?
merovingian.log
===============
<snip>
2020-05-09 05:38:27 ERR control[432623]: !monetdbd: an internal error has occurred 'could not receive initial byte: Connection reset by peer'
2020-05-09 05:38:27 ERR control[432623]: !monetdbd: an internal error has occurred 'could not receive initial byte: Connection reset by peer'
2020-05-09 05:38:27 MSG merovingian[432623]: database 'TSV_PROD_2_DB' has crashed after start on 2020-05-08 10:49:50, attempting restart, up min/avg/max: 1s/2h/17h, crash average: 1.00 0.30 0.13 (12-8=4)'
<snip>
(gdb) bt
0 0x00007f4cf8f09b9b in update_table () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
1 0x00007f4cf8ef20c2 in rollforward_changeset_updates () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
2 0x00007f4cf8f02f6d in rollforward_update_schema () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
3 0x00007f4cf8ef20c2 in rollforward_changeset_updates () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
4 0x00007f4cf8ef244a in rollforward_trans () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
5 0x00007f4cf8ef7ca9 in sql_trans_commit () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
6 0x00007f4cf8e948e3 in mvc_commit () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
7 0x00007f4cf8e12d81 in SQLreader () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/monetdb5/lib_sql.so
8 0x00007f4d0ada7720 in runScenario () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libmonetdb5.so.28
9 0x00007f4d0ada7d6c in MSserveClient () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libmonetdb5.so.28
10 0x00007f4d0ada8336 in MSscheduleClient () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libmonetdb5.so.28
11 0x00007f4d0ae1559d in doChallenge () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libmonetdb5.so.28
12 0x00007f4d0aa2ce37 in THRstarter () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libbat.so.19
13 0x00007f4d0aa5ad89 in thread_starter () from /monet_binaries/MonetDB-11.35.19_DEBUG/lib/libbat.so.19
14 0x00007f4d084d2e25 in start_thread (arg=0x7f475940f700) at pthread_create.c:308
15 0x00007f4d0820034d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb)
dmesg
======
This is not from the present run. We do not have any fault registered yet. But we do see this on our previous run.
Fri May 8 10:43:42 2020] mserver5[5693]: segfault at 50 ip 00007f4cf8f09b9b sp 00007f475940c960 error 4 in lib_sql.so[7f4cf8ddf000+19e000]
$ mserver5 --version
MonetDB 5 server 11.35.19 (Nov2019-SP3) (64-bit)
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2020 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 1007.3GiB available memory, 128 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30
openssl: OpenSSL 1.0.2k-fips 26 Jan 2017
libxml2: 2.9.1
Compiled by: monet@localhost (x86_64-pc-linux-gnu)
Compilation: gcc -std=gnu99 -g -O2 -g3
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
$ /monet_binaries/MonetDB-11.35.19_DEBUG/bin/monetdbd --version
MonetDB Database Server v11.35.19 (Nov2019-SP3)
Reproducible: Always
### Steps to Reproduce:
1. Run Reproducer (Will upload or provide info)
### Actual Results:
mserver5 crashes.
### Expected Results:
Reproducer should work (create/update) table should work as designed.
## Comment 27702
Date: 2020-05-11 11:34:44 +0200
From: Arshad <<arshad.super>>
Log from /var/log/message at time of crash
===========================================
May 9 05:37:37 lnx1538 kernel: mserver5[5693]: segfault at 50 ip 00007f4cf8f09b9b sp 00007f475940c960 error 4 in lib_sql.so[7f4cf8ddf000+19e000]
May 9 05:37:37 lnx1538 abrt-hook-ccpp: Process 432632 (mserver5) of user 9998 killed by SIGSEGV - dumping core
## Comment 27735
Date: 2020-06-02 16:14:11 +0200
From: Arshad <<arshad.super>>
Update 2:
=========
We compiled with no optimization and assert switch on to catch any assertion early if any. The crash was a abort due to trans_init: Assertion `0' failed. I am not sure if this is the same cause. https://www.monetdb.org/pipermail/users-list/2018-June/010260.html. Below are the details. We see this fairly consistently any help on this one.
Our core generated is is almost 3.5 GB. I do not know if uploading is feasible. here.
Let us know if you require more input from us.
$ ls -alih core.287457
46932408 -rw------- 1 monetadmin monetadmin 3.4G Jun 2 06:27 core.287457
mserver5 --version
MonetDB 5 server 11.35.19 (Nov2019-SP3) (64-bit)
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2020 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 1007.3GiB available memory, 128 available cpu cores
Libraries:
libpcre: 8.32 2012-11-30
openssl: OpenSSL 1.0.2k-fips 26 Jan 2017
libxml2: 2.9.1
Compiled by: monetadmin@lnx1490.ch3.prod.i.com (x86_64-pc-linux-gnu)
Compilation: gcc -std=gnu99 -g -g3
Linking : /bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
Log
===
<snip>
2020-06-02 05:34:46 ERR TSV_PROD_2_DB[287457]: client4:!ERROR:MALException:mal.interpreter:prematurely stopped client
2020-06-02 05:35:52 ERR TSV_PROD_2_DB[287457]: client3:!ERROR:SQLException:sql.resultset:45000!Result set construction failed
2020-06-02 06:27:52 ERR TSV_PROD_2_DB[287457]: mserver5: store.c:3281: trans_init: Assertion `0' failed.
<snip>
2020-06-02 06:27:59 MSG merovingian[287426]: starting a proxy failed: could not receive initial byte: Connection reset by peer
2020-06-02 06:27:59 ERR merovingian[287426]: client error: could not receive initial byte: Connection reset by peer
2020-06-02 06:27:59 ERR merovingian[287426]: client error: could not receive initial byte: Connection reset by peer
2020-06-02 06:27:59 MSG merovingian[287426]: database 'TSV_PROD_2_DB' (287457) has crashed (dumped core)
2020-06-02 06:27:59 MSG merovingian[287426]: database 'TSV_PROD_2_DB' has crashed after start on 2020-06-01 02:00:13, attempting restart, up mi n/avg/max: 1s/2d/3w, crash average: 1.00 0.40 0.17 (14-9=5)
76845 2020-06-02 06:28:00 MSG merovingian[287426]: proxying client 10.106.68.48:47636 for database 'TSV_PROD_2_DB' to mapi:monetdb:///monet_data01/DB FARM_TSV_PROD_2/TSV_PROD_2_DB/.mapi.sock?database=TSV_PROD_2_DB
76846 2020-06-02 06:28:00 MSG TSV_PROD_2_DB[346819]: arguments: /monet_binaries/MonetDB-11.35.19_ARSHAD/bin/mserver5 --dbpath=/monet_data01/DBFARM_TS V_PROD_2/TSV_PROD_2_DB --set merovingian_uri=mapi:monetdb://lnx1538.ch3.qa.i.com:50900/TSV_PROD_2_DB --set mapi_open=false --set mapi_ipv6=fals e --set mapi_port=0 --set mapi_usock=/monet_data01/DBFARM_TSV_PROD_2/TSV_PROD_2_DB/.mapi.sock --set monet_vault_key=/monet_data01/DBFARM_TSV_PR OD_2/TSV_PROD_2_DB/.vaultkey --set gdk_nr_threads=128 --set max_clients=2048 --set sql_optimizer=sequential_pipe --set embedded_py=2
2020-06-02 06:28:00 ERR control[287426]: !monetdbd: an internal error has occurred 'cannot connect: Connection refused'
<snip-end>
Here is the back-trace.
(gdb) bt
0 0x00007f3ad12bd1f7 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
1 0x00007f3ad12be8e8 in __GI_abort () at abort.c:90
2 0x00007f3ad12b6266 in __assert_fail_base (
fmt=0x7f3ad1408e68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7f3ac1e45ba8 "0",
file=file@entry=0x7f3ac1e45914 "store.c", line=line@entry=3281,
function=function@entry=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init")
at assert.c:92
3 0x00007f3ad12b6312 in __GI___assert_fail (assertion=0x7f3ac1e45ba8 "0",
file=0x7f3ac1e45914 "store.c", line=3281,
function=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init") at assert.c:101
4 0x00007f3ac1dc3fa5 in trans_init (tr=0x7f39c00018d0, stk=0, otr=0x5d6be30)
at store.c:3281
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
6 0x00007f3ac1d154a1 in mvc_trans (m=0x7f39802d7940) at sql_mvc.c:357
7 0x00007f3ac1c58ec0 in SQLtrans (m=0x7f39802d7940) at sql_scenario.c:674
8 0x00007f3ac1c59e79 in SQLparser (c=0x7f3ac25b1cc8) at sql_scenario.c:1076
9 0x00007f3ad4195acf in runPhase (c=0x7f3ac25b1cc8, phase=1) at mal_scenario.c:517
10 0x00007f3ad4195b80 in runScenarioBody (c=0x7f3ac25b1cc8, once=0)
at mal_scenario.c:537
11 0x00007f3ad4195dfb in runScenario (c=0x7f3ac25b1cc8, once=0) at mal_scenario.c:575
12 0x00007f3ad4197847 in MSserveClient (c=0x7f3ac25b1cc8) at mal_session.c:504
13 0x00007f3ad41973b4 in MSscheduleClient (
command=0x7f3980130fd0 '\333' <repeats 199 times>, <incomplete sequence \333>...,
challenge=0x7f39bddedc90 "mckG7kNhAh", fin=0x7f3980142a70, fout=0x7f3ab8042330,
protocol=PROTOCOL_9, blocksize=8190) at mal_session.c:382
14 0x00007f3ad423a0cb in doChallenge (data=0x7f3ab8001f90) at mal_mapi.c:267
15 0x00007f3ad3d3bb97 in THRstarter (a=0x7f3ab8077440) at gdk_utils.c:1558
16 0x00007f3ad3da2c0f in thread_starter (arg=0x7f3ab80016f0) at gdk_system.c:657
17 0x00007f3ad1652e25 in start_thread (arg=0x7f39bddee700) at pthread_create.c:308
18 0x00007f3ad138034d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb) frame 5
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
6923 store.c: No such file or directory.
(gdb) bt
0 0x00007f3ad12bd1f7 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
1 0x00007f3ad12be8e8 in __GI_abort () at abort.c:90
2 0x00007f3ad12b6266 in __assert_fail_base (
fmt=0x7f3ad1408e68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7f3ac1e45ba8 "0",
file=file@entry=0x7f3ac1e45914 "store.c", line=line@entry=3281,
function=function@entry=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init")
at assert.c:92
3 0x00007f3ad12b6312 in __GI___assert_fail (assertion=0x7f3ac1e45ba8 "0",
file=0x7f3ac1e45914 "store.c", line=3281,
function=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init") at assert.c:101
4 0x00007f3ac1dc3fa5 in trans_init (tr=0x7f39c00018d0, stk=0, otr=0x5d6be30)
at store.c:3281
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
6 0x00007f3ac1d154a1 in mvc_trans (m=0x7f39802d7940) at sql_mvc.c:357
7 0x00007f3ac1c58ec0 in SQLtrans (m=0x7f39802d7940) at sql_scenario.c:674
8 0x00007f3ac1c59e79 in SQLparser (c=0x7f3ac25b1cc8) at sql_scenario.c:1076
9 0x00007f3ad4195acf in runPhase (c=0x7f3ac25b1cc8, phase=1) at mal_scenario.c:517
10 0x00007f3ad4195b80 in runScenarioBody (c=0x7f3ac25b1cc8, once=0)
at mal_scenario.c:537
11 0x00007f3ad4195dfb in runScenario (c=0x7f3ac25b1cc8, once=0) at mal_scenario.c:575
12 0x00007f3ad4197847 in MSserveClient (c=0x7f3ac25b1cc8) at mal_session.c:504
13 0x00007f3ad41973b4 in MSscheduleClient (
command=0x7f3980130fd0 '\333' <repeats 199 times>, <incomplete sequence \333>...,
challenge=0x7f39bddedc90 "mckG7kNhAh", fin=0x7f3980142a70, fout=0x7f3ab8042330,
protocol=PROTOCOL_9, blocksize=8190) at mal_session.c:382
14 0x00007f3ad423a0cb in doChallenge (data=0x7f3ab8001f90) at mal_mapi.c:267
15 0x00007f3ad3d3bb97 in THRstarter (a=0x7f3ab8077440) at gdk_utils.c:1558
16 0x00007f3ad3da2c0f in thread_starter (arg=0x7f3ab80016f0) at gdk_system.c:657
17 0x00007f3ad1652e25 in start_thread (arg=0x7f39bddee700) at pthread_create.c:308
18 0x00007f3ad138034d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb) frame 5
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
6923 in store.c
(gdb) info locals
tr = 0x7f39c00018d0
snr = 191
(gdb) ptype tr
type = struct sql_trans {
char *name;
int stime;
int wstime;
int rtime;
int wtime;
int schema_number;
int schema_updates;
int active;
int status;
list *dropped;
list *moved_tables;
changeset schemas;
sql_allocator *sa;
struct sql_trans *parent;
backend_stack stk;
} *
(gdb) p *tr
$1 = {name = 0x0, stime = 1889, wstime = 1893, rtime = 0, wtime = 0,
schema_number = 192, schema_updates = 0, active = 0, status = 0, dropped = 0x0,
moved_tables = 0x0, schemas = {sa = 0x7f39c0001970,
destroy = 0x7f3ac1db0bad <schema_destroy>, set = 0x7f39c014e5d0, dset = 0x0,
nelm = 0x0}, sa = 0x7f39c0001970, parent = 0x5d6be30, stk = 0}
(gdb) ptype snr
type = int
(gdb)
(gdb) bt full
0 0x00007f3ad12bd1f7 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 287457
selftid = 346754
1 0x00007f3ad12be8e8 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffd5d8a6f5a,
sa_sigaction = 0x7ffd5d8a6f5a}, sa_mask = {__val = {139890595487600,
139890337798420, 3281, 139885975361280, 139890594118595, 4,
139885975361216, 2149427392, 139884939385536, 139885975361392, 0, 0, 0,
21474836480, 139890649300992, 139890595499624}},
sa_flags = -1041998936,
sa_restorer = 0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606>}
sigs = {__val = {32, 0 <repeats 15 times>}}
2 0x00007f3ad12b6266 in __assert_fail_base (
fmt=0x7f3ad1408e68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7f3ac1e45ba8 "0",
file=file@entry=0x7f3ac1e45914 "store.c", line=line@entry=3281,
function=function@entry=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init")
at assert.c:92
str = 0x7f3980145080 " P\024\200\071\177"
total = 4096
3 0x00007f3ad12b6312 in __GI___assert_fail (assertion=0x7f3ac1e45ba8 "0",
file=0x7f3ac1e45914 "store.c", line=3281,
function=0x7f3ac1e46c1d <__PRETTY_FUNCTION__.12606> "trans_init") at assert.c:101
No locals.
4 0x00007f3ac1dc3fa5 in trans_init (tr=0x7f39c00018d0, stk=0, otr=0x5d6be30)
at store.c:3281
pt = 0x96f2bf0
t = 0x7f39c1d75a00
k = 0x96f3540
l = 0x7f39c1d76350
ps = 0x60c7220
s = 0x7f39c01569c0
istmp = 0
m = 0x97badc0
n = 0x7f39c1de6100
__PRETTY_FUNCTION__ = "trans_init"
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
tr = 0x7f39c00018d0
snr = 191
6 0x00007f3ac1d154a1 in mvc_trans (m=0x7f39802d7940) at sql_mvc.c:357
---Type <return> to continue, or q <return> to quit---
schema_changed = 0
err = 0
__PRETTY_FUNCTION__ = "mvc_trans"
7 0x00007f3ac1c58ec0 in SQLtrans (m=0x7f39802d7940) at sql_scenario.c:674
s = 0x48
__func__ = "SQLtrans"
__PRETTY_FUNCTION__ = "SQLtrans"
8 0x00007f3ac1c59e79 in SQLparser (c=0x7f3ac25b1cc8) at sql_scenario.c:1076
in = 0x7f3980142a70
out = 0x7f3ab8042330
msg = 0x0
be = 0x7f3980143900
m = 0x7f39802d7940
oldvtop = 1
oldstop = 1
pstatus = 0
err = 0
opt = 0
q = 0x7f39801439f0 '\333' <repeats 72 times>, "A"
__func__ = "SQLparser"
__PRETTY_FUNCTION__ = "SQLparser"
9 0x00007f3ad4195acf in runPhase (c=0x7f3ac25b1cc8, phase=1) at mal_scenario.c:517
msg = 0x0
10 0x00007f3ad4195b80 in runScenarioBody (c=0x7f3ac25b1cc8, once=0)
at mal_scenario.c:537
msg = 0x0
__PRETTY_FUNCTION__ = "runScenarioBody"
11 0x00007f3ad4195dfb in runScenario (c=0x7f3ac25b1cc8, once=0) at mal_scenario.c:575
msg = 0x0
12 0x00007f3ad4197847 in MSserveClient (c=0x7f3ac25b1cc8) at mal_session.c:504
mb = 0x7f3980142d40
msg = 0x0
__PRETTY_FUNCTION__ = "MSserveClient"
13 0x00007f3ad41973b4 in MSscheduleClient (
command=0x7f3980130fd0 '\333' <repeats 199 times>, <incomplete sequence \333>...,
challenge=0x7f39bddedc90 "mckG7kNhAh", fin=0x7f3980142a70, fout=0x7f3ab8042330,
protocol=PROTOCOL_9, blocksize=8190) at mal_session.c:382
user = 0x7f3980130fd4 '\333' <repeats 199 times>, <incomplete sequence \333>...
algo = 0x7f3980130fe7 '\333' <repeats 199 times>, <incomplete sequence \333>...
passwd = 0x7f3980130ff1 '\333' <repeats 199 times>, <incomplete sequence \333>...
---Type <return> to continue, or q <return> to quit---
lang = 0x7f398013101a '\333' <repeats 199 times>, <incomplete sequence \333>...
database = 0x7f398013101e '\333' <repeats 199 times>, <incomplete sequence \333>...
s = 0x0
dbname = 0x49d43e0 "TSV_PROD_2_DB"
msg = 0x0
filetrans = false
c = 0x7f3ac25b1cc8
__func__ = "MSscheduleClient"
14 0x00007f3ad423a0cb in doChallenge (data=0x7f3ab8001f90) at mal_mapi.c:267
buf = 0x7f3980130fd0 '\333' <repeats 199 times>, <incomplete sequence \333>...
__func__ = "doChallenge"
challenge = "mckG7kNhAh\000\275\275"
fdin = 0x7f3ab8001ef0
fdout = 0x7f3ab8042330
bs = 0x7f3980142a70
len = 93
protocol = PROTOCOL_9
buflen = 8190
15 0x00007f3ad3d3bb97 in THRstarter (a=0x7f3ab8077440) at gdk_utils.c:1558
t = 0x7f3ab8077440
func = 0x7f3ad4239912 <doChallenge>
arg = 0x7f3ab8001f90
__func__ = "THRstarter"
16 0x00007f3ad3da2c0f in thread_starter (arg=0x7f3ab80016f0) at gdk_system.c:657
p = 0x7f3ab80016f0
data = 0x7f3ab8077440
17 0x00007f3ad1652e25 in start_thread (arg=0x7f39bddee700) at pthread_create.c:308
__res = <optimized out>
pd = 0x7f39bddee700
now = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139885975365376,
6215938736664030108, 0, 139885975366080, 139885975365376, 37,
-6327547695679198308, -6325638198854079588}, mask_was_saved = 0}},
priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = <optimized out>
pagesize_m1 = <optimized out>
sp = <optimized out>
freesize = <optimized out>
18 0x00007f3ad138034d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb)
## Comment 27769
Date: 2020-06-03 09:13:32 +0200
From: @sjoerdmullender
The content of attachment 670 has been deleted for the following reason:
spam
## Comment 27793
Date: 2020-06-08 10:12:08 +0200
From: Arshad <<arshad.super>>
Hi Devs,
We are running into this very often. Would like to know if there is any update on this ? Is the information I have supplied sufficient ? Is there anything else you want me to update. Please do let me know.
Thanks
Arshad
## Comment 27794
Date: 2020-06-08 11:43:05 +0200
From: @mlkersten
This overwhelming information is hard to assess, but the first line may give a hint
2020-05-09 05:38:27 ERR control[432623]: !monetdbd: an internal error has occurred 'could not receive initial byte: Connection reset by peer'
This indicates there are problems in you network environment, because mserver lost the connection. Whether it is broken hardware, hidden network timeouts, broken pipe, hitting an OS limit on processes, open files, ... can not be determined.
Resolving this requires a holistic view on your application setup.
## Comment 27797
Date: 2020-06-09 06:37:59 +0200
From: Arshad <<arshad.super>>
Comment 2: contains the more latest core and information. This server was compiled with assert on to catch any abnormality early. I can confirm that the network is stable and the "connection reset" is the effect of earlier crash. The early (first) crash however could not capture the debugging symbols so we got the latest crash with debugging symbols. Which starts with Comment 2.
The setup is : Server running under Linux and clients (mclient) connecting to it. Clients however on certain parts of script can scale up-to 2048 count as I said earlier.
The core is so large that it is next to impossible to uploaded; most of the information is dissection of core. This is the most I could do.
The details of back-trace is given earlier.
This is where We hit assertion.
client3:!ERROR:SQLException:sql.resultset:45000!Result set construction failed
2020-06-02 06:27:52 ERR TSV_PROD_2_DB[287457]: mserver5: store.c:3281: trans_init: Assertion `0' failed.
...
...
..and as a result we abort.
2020-06-02 06:27:59 ERR merovingian[287426]: client error: could not receive initial byte: Connection reset by peer
2020-06-02 06:27:59 MSG merovingian[287426]: database 'TSV_PROD_2_DB' (287457) has crashed (dumped core)
Here is the relevant frame information of store.c
(gdb) frame 5
5 0x00007f3ac1dd417e in sql_trans_begin (s=0x7f3980140f30) at store.c:6923
6923 in store.c
(gdb) info locals
tr = 0x7f39c00018d0
snr = 191
(gdb) ptype tr
type = struct sql_trans {
char *name;
int stime;
int wstime;
int rtime;
int wtime;
int schema_number;
int schema_updates;
int active;
int status;
list *dropped;
list *moved_tables;
changeset schemas;
sql_allocator *sa;
struct sql_trans *parent;
backend_stack stk;
} *
(gdb) p *tr
$1 = {name = 0x0, stime = 1889, wstime = 1893, rtime = 0, wtime = 0,
schema_number = 192, schema_updates = 0, active = 0, status = 0, dropped = 0x0,
moved_tables = 0x0, schemas = {sa = 0x7f39c0001970,
destroy = 0x7f3ac1db0bad <schema_destroy>, set = 0x7f39c014e5d0, dset = 0x0,
nelm = 0x0}, sa = 0x7f39c0001970, parent = 0x5d6be30, stk = 0}
(gdb) ptype snr
type = int
(gdb)
## Comment 27822
Date: 2020-06-11 11:07:19 +0200
From: @njnes
the assert is throw because there is a difference in the lists of tables of a schema. Any hints on what the application is doing may help narrowing down the issue.
## Comment 27945
Date: 2020-07-27 09:09:13 +0200
From: Arshad <<arshad.super>>
Hi Niels,
>the assert is throw because there is a difference in the lists of tables of a schema. Any hints on what the application is doing may help narrowing down the issue.
The data load is happening through a automatic application workflow creator (control-M) - Currently the prep time itself is almost half a day. What I meant is that the Test-case is huge!. We are still trying narrow down and bring it into small chunk so that is easily shared.
That said, what i could say is that the setup is a Server running under Linux and clients (mclient) connecting to it (this is done via control-M). Clients however on certain parts of control-m script can scale up-to 2048 count. So concurrency is in play here.
Thanks
Arshad
| mserver5: crashes under update_table() when calling lib_sql.so ( max_clients = 2048) | https://api.github.com/repos/MonetDB/MonetDB/issues/6862/comments | 1 | 2020-11-30T16:56:01Z | 2024-06-27T13:08:36Z | https://github.com/MonetDB/MonetDB/issues/6862 | 753,641,878 | 6,862 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6861/comments | 0 | 2020-11-30T16:55:58Z | 2020-11-30T16:56:00Z | https://github.com/MonetDB/MonetDB/issues/6861 | 753,641,834 | 6,861 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6860/comments | 0 | 2020-11-30T16:55:56Z | 2020-11-30T16:55:57Z | https://github.com/MonetDB/MonetDB/issues/6860 | 753,641,800 | 6,860 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-01 22:03:56 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @kutsurak
Last updated: 2020-07-27 09:30:12 +0200
## Comment 27691
Date: 2020-05-01 22:03:56 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
select json.text(json '[1,2,3,4]', 'ax');
returns '1a2a3a4'
instead of '1ax2ax3ax4'.
It appears that only the first character of the separator string 'ax' is currently used.
It should include the whole separator string as the signature allows a string and not a character.
Reproducible: Always
### Steps to Reproduce:
select json.text(json '[1,2,3,4]', 'ax');
select json.text(json '[1,2,3,4]', 'test');
select func from sys.functions where name = 'text' and mod = 'json' and system;
### Actual Results:
sql>select json.text(json '[1,2,3,4]', 'ax');
+---------+
| L2 |
+=========+
| 1a2a3a4 |
+---------+
1 tuple
sql>select json.text(json '[1,2,3,4]', 'test');
+---------+
| L2 |
+=========+
| 1t2t3t4 |
+---------+
1 tuple
sql>
sql>select func from sys.functions where name = 'text' and mod = 'json' and system;
+-----------------------------------------------------------------------------+
| func |
+=============================================================================+
| create function json.text(js json, e string) |
: returns string external name json.text; :
| create function json.text(js json) |
: returns string external name json.text; :
+-----------------------------------------------------------------------------+
2 tuples
sql>
### Expected Results:
sql>select json.text(json '[1,2,3,4]', 'ax');
+------------+
| L2 |
+============+
| 1ax2ax3ax4 |
+------------+
1 tuple
sql>select json.text(json '[1,2,3,4]', 'test');
+------------------+
| L2 |
+==================+
| 1test2test3test4 |
+------------------+
1 tuple
sql>
sql>select func from sys.functions where name = 'text' and mod = 'json' and system;
+-----------------------------------------------------------------------------+
| func |
+=============================================================================+
| create function json.text(js json, e string) |
: returns string external name json.text; :
| create function json.text(js json) |
: returns string external name json.text; :
+-----------------------------------------------------------------------------+
2 tuples
sql>
## Comment 27852
Date: 2020-06-15 17:48:24 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [36ab2df63f09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=36ab2df63f09) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=36ab2df63f09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=36ab2df63f09)
Changeset description:
Added test bug #6859
## Comment 27870
Date: 2020-06-22 13:50:24 +0200
From: @kutsurak
The Documentation for json.text at https://www.monetdb.org/Documentation/SQLReference/DataTypes/JSONDataType refers to the separator as a character. I think that the expected result for
select json.text(json '[1,2,3,4]', 'ax');
should be an error. Thoughts?
## Comment 27891
Date: 2020-07-06 10:22:01 +0200
From: @kutsurak
Fixed as originally intended on changeset [76211429a963](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=76211429a963)
See: [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=76211429a963](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=76211429a963)
| only first character of the separator string in json.text(js json, sep string) is used | https://api.github.com/repos/MonetDB/MonetDB/issues/6859/comments | 0 | 2020-11-30T16:55:52Z | 2024-06-27T13:08:35Z | https://github.com/MonetDB/MonetDB/issues/6859 | 753,641,745 | 6,859 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-01 21:46:07 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @kutsurak
Last updated: 2020-07-27 09:30:15 +0200
## Comment 27690
Date: 2020-05-01 21:46:07 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
json.keyarray(json '{ "":0 }') should return: [""].
Instead it returns: Error: Could not allocate space
This is probably due to uninitialised/incorrect length when allocating memory as:
json.keyarray(json '{ "a":0 }') returns: ["a"].
Note json.isvalid(json '{ "":0 }')
and json.isobject(json '{ "":0 }')
both return true so '{ "":0 }' is a valid json object.
Reproducible: Always
### Steps to Reproduce:
select json.keyarray(json '{ "":0 }');
-- returns: Error: Could not allocate space
select json.isvalid(json '{ "":0 }');
select json.isobject(json '{ "":0 }');
-- returns: true
select json.keyarray(json '{ "":"" }');
select json.isvalid(json '{ "":"" }');
select json.isobject(json '{ "":"" }');
select json.keyarray(json '{ "a":0 }');
-- returns: ["a"]
### Actual Results:
sql>select json.keyarray(json '{ "":0 }');
Could not allocate space
sql>select json.isvalid(json '{ "":0 }');
+-------+
| L2 |
+=======+
| true |
+-------+
1 tuple
sql>select json.isobject(json '{ "":0 }');
+-------+
| L2 |
+=======+
| true |
+-------+
1 tuple
sql>
sql>select json.keyarray(json '{ "":"" }');
Could not allocate space
sql>select json.isvalid(json '{ "":"" }');
+-------+
| L2 |
+=======+
| true |
+-------+
1 tuple
sql>select json.isobject(json '{ "":"" }');
+-------+
| L2 |
+=======+
| true |
+-------+
1 tuple
sql>
sql>select json.keyarray(json '{ "a":0 }');
+-------+
| L2 |
+=======+
| ["a"] |
+-------+
1 tuple
sql>
### Expected Results:
sql>select json.keyarray(json '{ "":0 }');
+------+
| L2 |
+======+
| [""] |
+------+
1 tuple
sql>select json.keyarray(json '{ "":"" }');
+------+
| L2 |
+======+
| [""] |
+------+
1 tuple
See JSONkeyArray(json *ret, json *js) in
https://dev.monetdb.org/hg/MonetDB/file/Nov2019/monetdb5/modules/atoms/json.c
## Comment 27851
Date: 2020-06-15 17:42:22 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c932190780ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c932190780ff) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c932190780ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=c932190780ff)
Changeset description:
Added test for bug #6858
## Comment 27868
Date: 2020-06-22 13:42:44 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e5f5ab2d3769](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e5f5ab2d3769) made by Panagiotis Koutsourakis <kutsurak@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e5f5ab2d3769](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e5f5ab2d3769)
Changeset description:
Handle empty strings correctly in JSONkeyArray
This fixes Bug #6858
## Comment 27869
Date: 2020-06-22 13:42:48 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1ba2ed8873df](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1ba2ed8873df) made by Panagiotis Koutsourakis <kutsurak@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1ba2ed8873df](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1ba2ed8873df)
Changeset description:
Add test results for Bug #6858
| json.keyarray(json '{ "":0 }') fails with error: Could not allocate space | https://api.github.com/repos/MonetDB/MonetDB/issues/6858/comments | 0 | 2020-11-30T16:55:48Z | 2024-06-27T13:08:34Z | https://github.com/MonetDB/MonetDB/issues/6858 | 753,641,699 | 6,858 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-05-01 21:20:06 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-10-19 11:06:22 +0200
## Comment 27689
Date: 2020-05-01 21:20:06 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
In sys.functions there is an aggregate function json.output(js json) listed.
When calling json.output(js json) it always returns an Error with msg: "Not yet implemented". So its is not useful.
As it is unclear what this output() aggregate function should do, I think it is better to remove it from the system.
Reproducible: Always
### Steps to Reproduce:
select func from sys.functions where name = 'output' and mod = 'json' and system;
-- shows: create aggregate json.output(js json)\nreturns string external name json.output;
create table js6856(c int, jsval json);
insert into js6856 values (1, '["a", 4]'), (1, '["b", 3]'), (1, '["c", 2]'), (1, '["d", 1]');
select * from js6856;
select json.output(jsval) from js6856;
-- Not yet implemented
select c, json.output(jsval) from js6856 group by c;
-- TypeException:user.s14_1[16]:'json.suboutput' undefined in: X_28:bat[:str] := json.suboutput(X_23:bat[:json], X_24:bat[:oid], X_25:bat[:oid], true:bit);
drop table js6856;
### Actual Results:
sql>select func from sys.functions where name = 'output' and mod = 'json' and system;
+-----------------------------------------------------------------------------+
| func |
+=============================================================================+
| create aggregate json.output(js json) |
: returns string external name json.output; :
+-----------------------------------------------------------------------------+
1 tuple
sql>create table js6856(c int, jsval json);
operation successful
sql>insert into js6856 values (1, '["a", 4]'), (1, '["b", 3]'), (1, '["c", 2]'), (1, '["d", 1]');
4 affected rows
sql>select * from js6856;
+------+----------+
| c | jsval |
+======+==========+
| 1 | ["a", 4] |
| 1 | ["b", 3] |
| 1 | ["c", 2] |
| 1 | ["d", 1] |
+------+----------+
4 tuples
sql>select json.output(jsval) from js6856;
Not yet implemented
sql>select c, json.output(jsval) from js6856 group by c;
TypeException:user.s14_1[16]:'json.suboutput' undefined in: X_28:bat[:str] := json.suboutput(X_23:bat[:json], X_24:bat[:oid], X_25:bat[:oid], true:bit);
sql>drop table js6856;
operation successful
sql>
Remove definition for aggregate json.output from:
https://dev.monetdb.org/hg/MonetDB/file/Nov2019/sql/scripts/40_json.sql
https://dev.monetdb.org/hg/MonetDB/file/Nov2019/monetdb5/modules/atoms/json.mal
## Comment 27855
Date: 2020-06-16 09:52:47 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [05e39c517279](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=05e39c517279) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=05e39c517279](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=05e39c517279)
Changeset description:
Removed obsolete json.output(json) function. This fixes bug #6857
| remove not implemented aggregate function json.output(js json) | https://api.github.com/repos/MonetDB/MonetDB/issues/6857/comments | 0 | 2020-11-30T16:55:45Z | 2024-06-27T13:08:33Z | https://github.com/MonetDB/MonetDB/issues/6857 | 753,641,663 | 6,857 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6856/comments | 0 | 2020-11-30T16:55:42Z | 2020-11-30T16:55:44Z | https://github.com/MonetDB/MonetDB/issues/6856 | 753,641,634 | 6,856 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-29 18:55:14 +0200
From: bharath <<bharath.thamanna>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @njnes, @PedroTadim
Last updated: 2020-08-25 14:00:38 +0200
## Comment 27686
Date: 2020-04-29 18:55:14 +0200
From: bharath <<bharath.thamanna>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36
Build Identifier:
The monet db is running with the below version 11.35.19(NOV2019-SP3) WHERAS IT IS WORKING WITH oLDER VERSIONS
CREATE TABLE "NG_RUBRMAID_63782_INTRM8" AS SELECT SYSTEM,VENDOR,ITEM,COUNT(*) FROM "ITKEY" WHERE (SYSTEM,VENDOR,ITEM) IN
(SELECT DISTINCT IDA.S_38250, IDA.S_38249, IDA.S_38252 FROM "IT_DIM_RUBRMAID_63782" IDA) AND SYSTEM <> 88 GROUP BY SYSTEM,VENDOR,ITEM HAVING COUNT(*) > 1;
ITKEY has - 89247808 rows and IT_DIM_RUBRMAID_63782 - 2335481 rows
Error details –
GDK reported error: GDKextendf: could not extend file
OS: File too large
GDKextendf: could not extend file
OS: File too large
HEAPextend: failed to extend to 1205446005861584 for 05/21/52130.tail: h->storage == STORE_MEM && can_map && fd >= 0 && HEAPload_intern() != GDK_SUCCEED
Note – I tried with less number rows in ITKEY. Say 1000 rows in ITKEY table, then above SQL works fine but it is taking time and slight memory bloat also observed.
Reproducible: Always
### Steps to Reproduce:
1. Running the above mentioned query in db it shows GDK error
2.
3.
### Actual Results:
Erroing out for now with version
### Expected Results:
Table which data based out of that qUERY
## Comment 27693
Date: 2020-05-06 14:25:23 +0200
From: bharath <<bharath.thamanna>>
Its been week i dont received nay update for this could you please check and update at the earliest
## Comment 27694
Date: 2020-05-06 19:00:47 +0200
From: @PedroTadim
Hello bharath, I checked the explain of this query on both Apr2019 and Nov2019, and they were the same. Can you do the same and send it here, to debug further?
Best regards,
Pedro
## Comment 28011
Date: 2020-08-25 14:00:38 +0200
From: @njnes
please check the status on the Jun2020-SP1 version.
| During ETL load process ETL found NewGen flow is failing because of this below SQL and error details, | https://api.github.com/repos/MonetDB/MonetDB/issues/6855/comments | 0 | 2020-11-30T16:55:39Z | 2024-06-27T13:08:31Z | https://github.com/MonetDB/MonetDB/issues/6855 | 753,641,582 | 6,855 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6854/comments | 0 | 2020-11-30T16:55:37Z | 2020-11-30T16:55:38Z | https://github.com/MonetDB/MonetDB/issues/6854 | 753,641,556 | 6,854 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-21 17:58:00 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-06-15 09:28:21 +0200
## Comment 27677
Date: 2020-04-21 17:58:00 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Build Identifier:
* Issue 1
The online documentation (https://www.monetdb.org/Documentation/Manuals/SQLreference/Procedures) and the mclient help don't agree on the allowed syntax of a procedure body statement.
Docs:
procedure_statement:
transaction_statement
| update_statement
| schema
| grant
| revoke
| create_statement
| drop_statement
| alter_statement
| declare_statement
| set_statement
| control_statement
| select_statement_single_row
mclient help:
procedure_statement :
transaction_statement
| update_statement
| grant
| revoke
| declare
| set_statement
| control_statement
| select_single_row
* Issue 2
They both say that transaction statements are allowed, but that is not the case:
sql>CREATE or REPLACE PROCEDURE x()
more>BEGIN
more> start transaction;
more> commit;
more>END;
Statement 'START' is not a valid flow control statement
* Issue 3
create statements are allowed according to the docs (not according to the help).
sql>CREATE or REPLACE PROCEDURE x()
more>BEGIN
more> create table x1(i int);
more>END;
operation successful
sql>
sql>CALL x();
They appear to be allowed. However, there is no table x1 after calling the procedure. Does it create it only in tmp and remove it when leaving the procedure? If so, that is not obvious.
Reproducible: Always
## Comment 27679
Date: 2020-04-22 14:50:15 +0200
From: @PedroTadim
Hello Roberto, thanks for your feedback. We are in the process of updating the documentation on both website and mhelp.
For issue number 1:
I just updated the valid statements inside procedures, functions and triggers on the website. I also updated mhelp for the next feature release in June.
Grant, revoke, transaction management, create, drop and alter are not supported on them at the moment. We can however make them available for procedures later on.
For issue number 2:
I already said above.
For issue number 3:
Only declared tables can be created inside procedures, functions and triggers. However we allow to create them with the CREATE syntax, which is not a clean option. We should make this more clear in the documentation as you said. I was thinking about removing it, but it may break production scripts.
You may know that declared tables are only valid in the scope they are declared, so they are gone at the end of the function/procedure call.
## Comment 27680
Date: 2020-04-22 15:31:55 +0200
From: @swingbit
Hi Pedro,
Yes, it all makes sense, thanks
| procedure_statement syntax and semantics inconsistencies | https://api.github.com/repos/MonetDB/MonetDB/issues/6853/comments | 0 | 2020-11-30T16:55:34Z | 2024-06-27T13:08:30Z | https://github.com/MonetDB/MonetDB/issues/6853 | 753,641,523 | 6,853 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-20 12:13:19 +0200
From: @evangelos-dimitriadis
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @evangelos-dimitriadis, @njnes, @yzchang
Last updated: 2020-08-25 14:10:35 +0200
## Comment 27676
Date: 2020-04-20 12:13:19 +0200
From: @evangelos-dimitriadis
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Build Identifier:
While an update query runs on Master DB, Slave DB cannot replicate it. The slave used to replicate updates in version Nov-2019, but now it only works for inserts.
Reproducible: Always
### Steps to Reproduce:
1. Stop any running monetDB database.
2. Run the script in Additional Information.
### Actual Results:
Replication error in batch 4:4 :MALException:mal.interpreter:GDK reported error: BATreplace: id out of range
:update beta set alpha_id = (select alpha.id from alpha where alpha.id = beta.id);
### Expected Results:
The slave replicates both tables alpha and beta.
!/bin/bash
monetdbd create dbfarm_master
if [ ! -d "/dbfarm/master" ];
then
monetdbd start dbfarm_master
monetdb create master
monetdb release master
monetdb create slave
monetdb release slave
mclient -d master --statement "CALL wlc.beat(0);"
mclient -d master --statement "CALL wlc.master();"
mclient -d master --statement "CREATE TABLE IF NOT EXISTS alpha (id bigint PRIMARY KEY AUTO_INCREMENT, data bigint);"
mclient -d master --statement "CREATE TABLE IF NOT EXISTS beta (id bigint PRIMARY KEY AUTO_INCREMENT, alpha_id bigint REFERENCES alpha(id), data bigint);"
mclient -d master --statement "INSERT INTO sys.alpha (data) select * from generate_series(0,1000,cast (1 as bigint));"
mclient -d master --statement "INSERT INTO sys.beta (data) select * from generate_series(0,1000,cast (1 as bigint));"
THIS CREATES THE REPLICATION ERROR
mclient -d master --statement "UPDATE beta SET alpha_id = (SELECT alpha.id FROM alpha WHERE alpha.id = beta.id);"
sleep 5
mclient -d slave --statement "CALL wlr.master('master');"
sleep 5
mclient -d slave --statement "CALL wlr.replicate();"
else
echo "Existing database found."
fi
| Lazy Replication: Replica DB does not replicate updates any more | https://api.github.com/repos/MonetDB/MonetDB/issues/6852/comments | 0 | 2020-11-30T16:55:31Z | 2024-06-28T13:07:46Z | https://github.com/MonetDB/MonetDB/issues/6852 | 753,641,495 | 6,852 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-16 16:00:56 +0200
From: @aris-koning
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @kutsurak
Last updated: 2020-06-03 16:58:54 +0200
## Comment 27666
Date: 2020-04-16 16:00:56 +0200
From: @aris-koning
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Build Identifier:
on the current default branch (f3fa4abc4ee8) there is probably a smal bug in the parsing of integers in the json module. I think the logic for handling trailing zero's is doing something wrong in the implementation of JSONintegerParser.
Reproducible: Always
### Steps to Reproduce:
1.mclient -s "select cast('{\"foo\": 90}' as json);"
2.mclient -s "select cast('{\"foo\": 9}' as json);"
### Actual Results:
1. works
2. fails
### Expected Results:
should both succeed
## Comment 27667
Date: 2020-04-16 16:03:00 +0200
From: @aris-koning
the actual results are reversed:
1. fails
2. works
excuse me
## Comment 27674
Date: 2020-04-17 15:14:31 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [40378c804b2e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=40378c804b2e) made by Panagiotis Koutsourakis <kutsurak@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=40378c804b2e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=40378c804b2e)
Changeset description:
Add test for Bug #6851
## Comment 27675
Date: 2020-04-17 15:14:35 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [fbb484d7ec3a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fbb484d7ec3a) made by Panagiotis Koutsourakis <kutsurak@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbb484d7ec3a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=fbb484d7ec3a)
Changeset description:
Fix Bug #6851
| json parser doesn't parse integers correctly | https://api.github.com/repos/MonetDB/MonetDB/issues/6851/comments | 0 | 2020-11-30T16:55:28Z | 2024-06-27T13:08:28Z | https://github.com/MonetDB/MonetDB/issues/6851 | 753,641,466 | 6,851 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-16 07:43:35 +0200
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @yzchang
Last updated: 2020-06-03 16:58:53 +0200
## Comment 27663
Date: 2020-04-16 07:43:35 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
The purpose of the idle timestamp in the client record is to detect connections that haven't been used for a long time.
The property is not properly set.
Reproducible: Always
### Steps to Reproduce:
start two independent mclient sessions
one should see that the other one is idle using
select * from sys.sessions()
no additional test file included
## Comment 27664
Date: 2020-04-16 10:06:21 +0200
From: @yzchang
I tried the new sys.sessions() in Jun2020 yesterday, it actually did show me that the other other connection is idle since <timestamp>:
sql>select * from sessions();
+-----------+----------+----------------------------+----------------------------+--------------+----------------+--------------+-------------+-------------+
| sessionid | username | login | idle | optimizer | sessiontimeout | querytimeout | workerlimit | memorylimit |
+===========+==========+============================+============================+==============+================+==============+=============+=============+
| 0 | monetdb | 2020-04-15 21:30:21.000000 | 2020-04-15 21:30:23.000000 | default_pipe | 0 | 0 | 0 | 0 |
| 1 | monetdb | 2020-04-15 21:30:30.000000 | null | default_pipe | 0 | 0 | 0 | 0 |
+-----------+----------+----------------------------+----------------------------+--------------+----------------+--------------+-------------+-------------+
2 tuples
## Comment 27665
Date: 2020-04-16 10:10:57 +0200
From: @mlkersten
In the June branch indeed it was set in the sql.execute() code.
It should (also) be managed lower, because MAL sessions also exist.
| Idle timestamp not set | https://api.github.com/repos/MonetDB/MonetDB/issues/6850/comments | 0 | 2020-11-30T16:55:25Z | 2024-06-27T13:08:27Z | https://github.com/MonetDB/MonetDB/issues/6850 | 753,641,430 | 6,850 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-13 14:04:17 +0200
From: Nilam <<nilam09chaudhary>>
To: buildtools devs <<bugs-buildtools>>
Version: -- development
Last updated: 2020-04-13 14:04:17 +0200
## Comment 27658
Date: 2020-04-13 14:04:17 +0200
From: Nilam <<nilam09chaudhary>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Build Identifier:
I am running experiment with cracking. I am using holindex branch. But I found there are many environment variables being used. Can you provide me the values of those environment variables?
Reproducible: Always
| Need environment variables | https://api.github.com/repos/MonetDB/MonetDB/issues/6849/comments | 0 | 2020-11-30T16:55:23Z | 2024-06-28T13:07:45Z | https://github.com/MonetDB/MonetDB/issues/6849 | 753,641,401 | 6,849 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-06 12:47:52 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-06-15 09:28:44 +0200
## Comment 27651
Date: 2020-04-06 12:47:52 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Build Identifier:
This is a only minor ambiguity in th error message.
The following query is indeed wrong:
sql>select count(*) from (values (1),(2),(3)) as t(i) order by t.i;
SELECT: cannot use non GROUP BY column 't.i' in query results without an aggregate function
However the error message is the same as when t.i is used in the target list, which is not the case here. In this case t.i was not used "in query result" (if with "query result" the target list is implied).
Reproducible: Always
## Comment 27652
Date: 2020-04-06 16:53:44 +0200
From: @PedroTadim
Hello Roberto, on this case, the error message is helpful for the user to understand what is the problem. If he wants to use i column, it must be on an aggregate function. I also issued this query on other DBMS and I got the same error message.
So what should be the error message according to you? From my perspective it's not worth to change it.
## Comment 27653
Date: 2020-04-06 16:58:40 +0200
From: @swingbit
Yes, I agree that this is a correct error.
I think it may be a bit confusing because by "query results" I expect it is talking about the target list, which does not contain t.i.
I think it would be more precise if, in this case, the error said:
sql>select count(*) from (values (1),(2),(3)) as t(i) order by t.i;
SELECT: cannot use non GROUP BY column 't.i' in ORDER BY clause without an aggregate function
I understand it is a minor difference and might be not worth a change. I just thought it was a bit confusing.
## Comment 27654
Date: 2020-04-06 17:41:02 +0200
From: @swingbit
I guess the confusion from me comes from the fact that using t.i in the order by (besides being wrong in this case) would not make it part of the result.
Even without any aggregations, so in a correct query, a column appearing in the order by clause does not end up in the result, unless it is also in the target list.
## Comment 27655
Date: 2020-04-07 19:50:01 +0200
From: @PedroTadim
That's true, but this can happen:
SELECT MIN(col1) from t1 order by SUM(col2), col3;
Here an error is thrown because col3 is not being aggregated. The order by columns are not in the result, but they can change its cardinality, so that must be verified. Both output and ordering columns must have the same cardinality, otherwise the computation doesn't make sense.
| Ambiguous error message | https://api.github.com/repos/MonetDB/MonetDB/issues/6848/comments | 0 | 2020-11-30T16:55:20Z | 2024-06-28T13:07:45Z | https://github.com/MonetDB/MonetDB/issues/6848 | 753,641,367 | 6,848 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-06 02:24:45 +0200
From: Nenya Edjah <<nenya_edjah>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2020-06-03 16:58:52 +0200
## Comment 27647
Date: 2020-04-06 02:24:45 +0200
From: Nenya Edjah <<nenya_edjah>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36
Build Identifier:
In the impscheck() macro, there is an:
if (im[icnt] & mask)
check to determine if the corresponding segments of the data should be scanned.
In the else case, we essentially skip over those irrelevant cache lines with a while loop:
while (p < ci->ncand && o < e) {
p++;
o = canditer_next(ci);
}
For dense canditers, this is inefficient since the canditer_next(ci) operation basically just does some arithmetic operations. So, it doesn't make sense to waste CPU cycles by iterating through a while loop. Especially if the amount of data being skipped is large.
A simple optimization is to replace the snippet above with the following:
if (ci->tpe == cand_dense) {
BUN skip_sz = MIN(ci->ncand - p, e - o);
p += skip_sz;
o += skip_sz;
ci->next += skip_sz;
} else {
while (p < ci->ncand && o < e) {
p++;
o = canditer_next(ci);
}
}
I implemented this change and ran a test on a nearly sorted column with 100m elements. When using a single CPU, this reduces the average query latency from 140ms to 4ms.
Since this is simple change, I just wanted to let you guys know about it in case you wanted to get it implemented in a future version MonetDB.
Best,
Nenya
Reproducible: Always
## Comment 27648
Date: 2020-04-06 09:50:54 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b0e2acf99f2f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b0e2acf99f2f) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=b0e2acf99f2f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=b0e2acf99f2f)
Changeset description:
Speed up imprints check for dense candidate lists.
Thanks lots to Nenya Edjah for the report and the core of the change.
This fixes bug #6847.
## Comment 27649
Date: 2020-04-06 09:52:17 +0200
From: @sjoerdmullender
Thanks for the analysis and patch.
As you can see, I made some bigger changes, but in essence, it's your patch.
## Comment 27650
Date: 2020-04-06 12:27:47 +0200
From: Nenya Edjah <<nenya_edjah>>
:D
| A simple way of speeding up impscheck for dense canditers | https://api.github.com/repos/MonetDB/MonetDB/issues/6847/comments | 0 | 2020-11-30T16:55:16Z | 2024-06-27T13:08:24Z | https://github.com/MonetDB/MonetDB/issues/6847 | 753,641,321 | 6,847 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-04-01 03:21:06 +0200
From: Bilal <<bilal.ahmed>>
To: SQL devs <<bugs-sql>>
Version: 11.33.3 (Apr2019)
CC: @PedroTadim
Last updated: 2020-06-03 16:58:54 +0200
## Comment 27637
Date: 2020-04-01 03:21:06 +0200
From: Bilal <<bilal.ahmed>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36
Build Identifier:
I'm using MonetDB Server and MonetDB Client on windows shell. I created a Global temporary table in client connection 1 (name close_d). I tried to access this table under client connection 2 but it throws error of "no such table 'close_d' ". While I can see this table under sys.tables in client connection 2.
My assumption is that all connections shall be able to see and use Global Temporary tables of same name. Can you please elaborate the purpose and usage of Global Temporary table in MonetDB, as there is not much detail on documentation about it?
Reproducible: Always
### Steps to Reproduce:
1. Start MonetDB Server.
2. Start MonetDB client
3. Inside MonetDB client, execute following commands:
create global temporary table close_d (qaid int, value_ float) ON commit preserve rows;
4.insert into close_d values (11,1100);
5.insert into close_d values (13,1300);
6.select * from tmp.close_d;
It would all work fine. Now:
7. Open another MonetDB client session.
8. Inside MonetDB client, execute:
select * from tmp.close_d;
### Actual Results:
Following error is thrown:
SELECT: no such table 'close_d'
### Expected Results:
The table shall be accessible in client session 2 as well. If I execute following query in client session 2:
select * from sys.tables order by 1 desc limit 1;
Then it shows me the name of close_d as well like:
+------+-------------+------+-------------+------+-------+------+------+------+
| id | name | sche | query | type | syste | comm | acce | temp |
: : : ma_i : : : m : it_a : ss : orar :
: : : d : : : : ctio : : y :
: : : : : : : n : : :
+======+=============+======+=============+======+=======+======+======+======+
| 8231 | close_d | 2114 | null | 20 | false | 2 | 0 | 1 |
## Comment 27638
Date: 2020-04-01 11:26:36 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [37eb0372ed86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=37eb0372ed86) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=37eb0372ed86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=37eb0372ed86)
Changeset description:
Added test for bug #6846
## Comment 27639
Date: 2020-04-01 11:43:09 +0200
From: Bilal <<bilal.ahmed>>
(In reply to MonetDB Mercurial Repository from comment 1)
> Changeset [37eb0372ed86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=37eb0372ed86) made by Pedro Ferreira
> <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this
> bug.
>
> For complete details, see
> [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=37eb0372ed86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=37eb0372ed86)
>
> Changeset description:
>
> Added test for bug #6846
Hi Pedro,
I'm sorry but I did not understand this message completely. Does it mean that there is some new fix that is available for me to apply or it's yet work in progress on MonetDB end?
Thanks.
## Comment 27640
Date: 2020-04-01 11:48:34 +0200
From: @PedroTadim
Hello Bilal,
As a coincidence, some of us spotted this bug yesterday as well. We are working on a fix for it. For now, restarting the server fixes the issue, but we will make global temporary tables available for every session on the fly.
## Comment 27641
Date: 2020-04-01 11:52:39 +0200
From: Bilal <<bilal.ahmed>>
"For now, restarting the server fixes the issue"
Do you mean, that I have to download and reinstall MonetDB on my machine to validate this? Or simply restarting, will make this global table available to other connections? :|
## Comment 27642
Date: 2020-04-01 12:04:07 +0200
From: @PedroTadim
Simply restarting the server, not installing again :) However as a temporary table all its data will be lost. Sorry for the inconvenience.
## Comment 27643
Date: 2020-04-01 12:09:08 +0200
From: Bilal <<bilal.ahmed>>
:) Great Thanks!
Just to know, when can this fix possibly be expected?
Secondly, will you please explain that what is Global temporary table functionality in MonetDB and how it differs from Local temporary table? I didn't see much detail in documentation.
I've worked with Global temp tables a lot in SQL server but not sure what I shall expect in MonetDB.
Regards
## Comment 27644
Date: 2020-04-01 13:07:52 +0200
From: @PedroTadim
Our next planned release is a feature release next June. However if a paid customer asks for a bug fix release on Nov2019, we can backport this bugfix to it, and make it available earlier.
On any temporary table, data is never persisted across server restarts. Local temporary tables are visible to the current session only, while global are visible to every session, although their content it's not replicated (ie each session has its own data on the global temporary table). Global temporary tables' metadata persists across server restarts, while local ones do not.
## Comment 27645
Date: 2020-04-01 14:29:27 +0200
From: Bilal <<bilal.ahmed>>
Pedro,
Thanks a lot for explanation and assistance.
| Global temporary table not accessible in other connections / sessions | https://api.github.com/repos/MonetDB/MonetDB/issues/6846/comments | 0 | 2020-11-30T16:55:13Z | 2024-06-27T13:08:23Z | https://github.com/MonetDB/MonetDB/issues/6846 | 753,641,280 | 6,846 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-27 00:45:54 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-07-27 09:30:16 +0200
## Comment 27630
Date: 2020-03-27 00:45:54 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
The url extraction functions: sys.getanchor(), sys.getbasename(), sys.getcontext(), sys.getdomain(), sys.getextension(), sys.getfile(), sys.gethost(), sys.getport(), sys.getprotocol(), sys.getquery(), sys.getroboturl() and sys.getuser() do not accept null as argument value. Instead they return an error: Error: bad url
It would be better (more consistent) to return null in those cases, similar to string, numeric and temporal functions.
Reproducible: Always
### Steps to Reproduce:
create table turl (val url);
insert into turl values ('https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample');
insert into turl values (null);
select * from turl;
select val, sys.getanchor(val) from turl;
select val, sys.getbasename(val) from turl;
select val, sys.getcontext(val) from turl;
select val, sys.getdomain(val) from turl;
select val, sys.getextension(val) from turl;
select val, sys.getfile(val) from turl;
select val, sys.gethost(val) from turl;
select val, sys.getport(val) from turl;
select val, sys.getprotocol(val) from turl;
select val, sys.getquery(val) from turl;
select val, sys.getroboturl(val) from turl;
select val, sys.getuser(val) from turl;
drop table turl;
### Actual Results:
sql>create table turl (val url);
operation successful
sql>insert into turl values ('https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample');
1 affected row
sql>insert into turl values (null);
1 affected row
sql>select * from turl;
+----------------------------------------------------------------------+
| val |
+======================================================================+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample |
| null |
+----------------------------------------------------------------------+
2 tuples
sql>
sql>select val, sys.getanchor(val) from turl;
bad url
sql>select val, sys.getbasename(val) from turl;
bad url
sql>select val, sys.getcontext(val) from turl;
bad url
sql>select val, sys.getdomain(val) from turl;
bad url
sql>select val, sys.getextension(val) from turl;
bad url
sql>select val, sys.getfile(val) from turl;
bad url
sql>select val, sys.gethost(val) from turl;
bad url
sql>select val, sys.getport(val) from turl;
bad url
sql>select val, sys.getprotocol(val) from turl;
bad url
sql>select val, sys.getquery(val) from turl;
bad url
sql>select val, sys.getroboturl(val) from turl;
bad url
sql>select val, sys.getuser(val) from turl;
bad url
sql>
sql>drop table turl;
operation successful
### Expected Results:
sql>create table turl (val url);
operation successful
sql>insert into turl values ('https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample');
1 affected row
sql>insert into turl values (null);
1 affected row
sql>select * from turl;
+----------------------------------------------------------------------+
| val |
+======================================================================+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample |
| null |
+----------------------------------------------------------------------+
2 tuples
sql>
sql>select val, sys.getanchor(val) from turl;
+----------------------------------------------------------------------+---------+
| val | L1 |
+======================================================================+=========+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | example |
| null | null |
+----------------------------------------------------------------------+---------+
2 tuples
sql>select val, sys.getbasename(val) from turl;
+----------------------------------------------------------------------+------+
| val | L1 |
+======================================================================+======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | Abc |
| null | null |
+----------------------------------------------------------------------+------+
2 tuples
sql>select val, sys.getcontext(val) from turl;
+----------------------------------------------------------------------+---------------+
| val | L1 |
+======================================================================+===============+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | /Doc/Abc.html |
| null | null |
+----------------------------------------------------------------------+---------------+
2 tuples
sql>select val, sys.getdomain(val) from turl;
+----------------------------------------------------------------------+------+
| val | L1 |
+======================================================================+======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | org |
| null | null |
+----------------------------------------------------------------------+------+
2 tuples
sql>select val, sys.getextension(val) from turl;
+----------------------------------------------------------------------+------+
| val | L1 |
+======================================================================+======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | html |
| null | null |
+----------------------------------------------------------------------+------+
2 tuples
sql>select val, sys.getfile(val) from turl;
+----------------------------------------------------------------------+----------+
| val | L1 |
+======================================================================+==========+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | Abc.html |
| null | null |
+----------------------------------------------------------------------+----------+
2 tuples
sql>select val, sys.gethost(val) from turl;
+----------------------------------------------------------------------+-----------------+
| val | L1 |
+======================================================================+=================+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | www.monetdb.org |
| null | null |
+----------------------------------------------------------------------+-----------------+
2 tuples
sql>select val, sys.getport(val) from turl;
+----------------------------------------------------------------------+------+
| val | L1 |
+======================================================================+======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | 458 |
| null | null |
+----------------------------------------------------------------------+------+
2 tuples
sql>select val, sys.getprotocol(val) from turl;
+----------------------------------------------------------------------+-------+
| val | L1 |
+======================================================================+=======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | https |
| null | null |
+----------------------------------------------------------------------+-------+
2 tuples
sql>select val, sys.getquery(val) from turl;
+----------------------------------------------------------------------+------------------+
| val | L1 |
+======================================================================+==================+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | lang=nl&sort=asc |
| null | null |
+----------------------------------------------------------------------+------------------+
2 tuples
sql>select val, sys.getroboturl(val) from turl;
+----------------------------------------------------------------------+-------------------------------------------+
| val | L1 |
+======================================================================+===========================================+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | https://me@www.monetdb.org:458/robots.txt |
| null | null |
+----------------------------------------------------------------------+-------------------------------------------+
2 tuples
sql>select val, sys.getuser(val) from turl;
+----------------------------------------------------------------------+------+
| val | L1 |
+======================================================================+======+
| https://me@www.monetdb.org:458/Doc/Abc.html?lang=nl&sort=ascexample | me |
| null | null |
+----------------------------------------------------------------------+------+
2 tuples
sql>
sql>drop table turl;
operation successful
I left out function sys.getcontent() as it will be removed, see 6843.
## Comment 27857
Date: 2020-06-16 10:13:26 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4fbe5a6e053c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4fbe5a6e053c) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4fbe5a6e053c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4fbe5a6e053c)
Changeset description:
Handle NULL URLs. This fixes bug #6845.
| the url sys.get...(url) functions do not allow null as a parameter | https://api.github.com/repos/MonetDB/MonetDB/issues/6845/comments | 0 | 2020-11-30T16:55:09Z | 2024-06-27T13:08:22Z | https://github.com/MonetDB/MonetDB/issues/6845 | 753,641,215 | 6,845 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-27 00:13:31 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-07-27 09:30:15 +0200
## Comment 27629
Date: 2020-03-27 00:13:31 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
According to https://en.wikipedia.org/wiki/URLSyntax it should be possible to specify a user in a URL as part of the authority component.
When used I expected the sys.getUser(url) function to extract and return the user part. However it returns null.
It appears the implementation of URLgetUser() in monetdb5/modules/atoms/url.c is incorrect.
Reproducible: Always
### Steps to Reproduce:
select sys.getUser('https://me:pw@www.monetdb.org/Doc');
### Actual Results:
sql>select sys.getUser('https://me:pw@www.monetdb.org/Doc');
+------+
| L2 |
+======+
| null |
+------+
1 tuple
sql>
### Expected Results:
sql>select sys.getUser('https://me:pw@www.monetdb.org/Doc');
+----+
| L2 |
+====+
| me |
+----+
1 tuple
sql>
monetdb5/modules/atoms/url.c line 655
URLgetUser() should be implemented similar to URLgetHost() or URLgetPort(), so without (s = skip_path(p, NULL, NULL)) == NULL).
## Comment 27854
Date: 2020-06-15 18:59:01 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7a65c6210abc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7a65c6210abc) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=7a65c6210abc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=7a65c6210abc)
Changeset description:
Fix for bug #6844, ie parse correctly the user field from URLs
| sys.getUser('https://me:pw@www.monetdb.org/Doc') does not return the user: me | https://api.github.com/repos/MonetDB/MonetDB/issues/6844/comments | 0 | 2020-11-30T16:55:06Z | 2024-06-27T13:08:21Z | https://github.com/MonetDB/MonetDB/issues/6844 | 753,641,174 | 6,844 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-26 23:28:24 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-10-19 11:06:20 +0200
## Comment 27628
Date: 2020-03-26 23:28:24 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:
The function sys.getcontent(url) always returns error "Feature not supported".
It has not been implemented, see monetdb5/modules/atoms/url.c lines 393-400.
It is better to remove this function from the list of functions in sys.functions
(so also from sql/scripts/12_url.sql and monetdb5/modules/atoms/url.mal) as it is not usefull. I do not expect it will ever be implemented.
Reproducible: Always
### Steps to Reproduce:
select sys.getcontent(url 'https://www.monetdb.org/Home');
select * from sys.functions where name = 'getcontent' and mod = 'url' and schema_id = 2000 and system;
### Actual Results:
sql>select sys.getcontent(url 'https://www.monetdb.org/Home');
Feature not supported
sql>
sql>select * from sys.functions where name = 'getcontent' and mod = 'url' and schema_id = 2000 and system;
+------+------------+---------------------------------------------------+------+------+------+-------+-------+-------+------+-------+
| id | name | func | mod | lang | type | side_ | varre | varar | sche | syste |
: : : : : uage : : effec : s : g : ma_i : m :
: : : : : : : t : : : d : :
+======+============+===================================================+======+======+======+=======+=======+=======+======+=======+
| 5087 | getcontent | create function getcontent(theurl url) returns st | url | 1 | 1 | false | false | false | 2000 | true |
: : : ring : : : : : : : : :
: : : external name url."getContent"; : : : : : : : : :
+------+------------+---------------------------------------------------+------+------+------+-------+-------+-------+------+-------+
1 tuple
sql>
### Expected Results:
function sys.getcontent() removed from the system
I will adapt the documentation on
https://www.monetdb.org/Documentation/Manuals/SQLreference/URLtype
## Comment 27853
Date: 2020-06-15 18:10:33 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [f3537e77b80b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f3537e77b80b) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=f3537e77b80b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=f3537e77b80b)
Changeset description:
Removed obsolete sys.getContent(url) function. This fixes bug #6843
| function sys.getcontent(url) always returns "Feature not supported" | https://api.github.com/repos/MonetDB/MonetDB/issues/6843/comments | 0 | 2020-11-30T16:55:02Z | 2024-06-27T13:08:20Z | https://github.com/MonetDB/MonetDB/issues/6843 | 753,641,131 | 6,843 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6842/comments | 0 | 2020-11-30T16:54:59Z | 2020-11-30T16:55:01Z | https://github.com/MonetDB/MonetDB/issues/6842 | 753,641,096 | 6,842 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6841/comments | 0 | 2020-11-30T16:54:57Z | 2020-11-30T16:54:58Z | https://github.com/MonetDB/MonetDB/issues/6841 | 753,641,061 | 6,841 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6840/comments | 0 | 2020-11-30T16:54:54Z | 2020-11-30T16:54:56Z | https://github.com/MonetDB/MonetDB/issues/6840 | 753,641,037 | 6,840 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6839/comments | 0 | 2020-11-30T16:54:52Z | 2020-11-30T16:54:53Z | https://github.com/MonetDB/MonetDB/issues/6839 | 753,641,008 | 6,839 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6838/comments | 0 | 2020-11-30T16:54:49Z | 2020-11-30T16:54:51Z | https://github.com/MonetDB/MonetDB/issues/6838 | 753,640,977 | 6,838 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6837/comments | 0 | 2020-11-30T16:54:46Z | 2020-11-30T16:54:47Z | https://github.com/MonetDB/MonetDB/issues/6837 | 753,640,940 | 6,837 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6836/comments | 0 | 2020-11-30T16:54:43Z | 2020-11-30T16:54:45Z | https://github.com/MonetDB/MonetDB/issues/6836 | 753,640,907 | 6,836 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T16:49:47Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6835/comments | 0 | 2020-11-30T16:54:40Z | 2020-11-30T16:54:42Z | https://github.com/MonetDB/MonetDB/issues/6835 | 753,640,866 | 6,835 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-19 20:12:25 +0100
From: Arshad <<arshad.super>>
To: clients devs <<bugs-clients>>
Version: 11.35.19 (Nov2019-SP3)
CC: martin.van.dinther
Last updated: 2020-04-15 12:07:11 +0200
## Comment 27610
Date: 2020-03-19 20:12:25 +0100
From: Arshad <<arshad.super>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36
Build Identifier:
Hi,
Using "ODBC Data source administrator" I am creating "File DSN" which is failing. However, I could successfully add an "user dsn" and connect with same information. Therefore I am confident that the information is correct. I am also sure I am not mixing 32bit/63bit application here. I generated trace which points essentially to below errors. (Full trace attached below.)
<snip>
DIAG [28000] [MonetDB][ODBC Driver 11.35.19]Invalid authorization specification (0)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
<snip>
What I was expecting was to get a "pop-up" page where I could further enter key=value pair or to successfully connect. Could this be a bug under 11.35.19 ?
SYSTEM INFO
(Windows 10 Enterprise) Version : 10.0.18363 Build 18363
Monet ODBC Driver version = 11.35.19 (32bit)
Thanks
Arshad
Reproducible: Always
### Steps to Reproduce:
1. Open ODBC Data source administrator under windows.
2. Click on "FILE DSN" tab
3. Click "ADD"
4. Select "Monetdb ODBC Driver"
5. Give a name to FILE DSN to be created (eg TESTDSN")
6. Click "finish"
### Actual Results:
Windows pop-up with message "A connect cannot be made"
### Expected Results:
1. It should successfully create "FILE DSN" file
OR
2. Further pop-up should be thrown for getting more information for connection.
TRACE LOGS
==========
odbcad32 1050-5ee4 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x00A3C374
odbcad32 1050-5ee4 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x00A3C374 ( 0x02C7C460)
odbcad32 1050-5ee4 ENTER SQLSetEnvAttr
SQLHENV 0x02C7C460
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 380 <SQL_OV_ODBC3_80>
SQLINTEGER 0
odbcad32 1050-5ee4 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x02C7C460
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 380 <SQL_OV_ODBC3_80>
SQLINTEGER 0
odbcad32 1050-5ee4 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x02C7C460
SQLHANDLE * 0x00A3C38C
odbcad32 1050-5ee4 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x02C7C460
SQLHANDLE * 0x00A3C38C ( 0x0689B578)
odbcad32 1050-5ee4 ENTER SQLDriverConnectW
HDBC 0x0689B578
HWND 0x00120CC6
WCHAR * 0x7B932440 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x7B932440
SWORD -3
SWORD * 0x00000000
UWORD 1 <SQL_DRIVER_COMPLETE>
odbcad32 1050-5ee4 EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 0x0689B578
HWND 0x00120CC6
WCHAR * 0x7B932440 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x7B932440
SWORD -3
SWORD * 0x00000000
UWORD 1 <SQL_DRIVER_COMPLETE>
DIAG [28000] [MonetDB][ODBC Driver 11.35.19]Invalid authorization specification (0)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
odbcad32 1050-5ee4 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0689B578
odbcad32 1050-5ee4 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0689B578
odbcad32 1050-5ee4 ENTER SQLFreeHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x02C7C460
odbcad32 1050-5ee4 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x02C7C460
## Comment 27611
Date: 2020-03-20 05:42:01 +0100
From: Arshad <<arshad.super>>
Update 1:
=========
I also tried Hard-coding the dll path. Just to check the behavior. It is still the same.
Driver="C:\Program Files (x86)\MonetDB\MonetDB ODBC Driver\lib\libMonetODBC.dll"
[As I understand, the below information should be collected separately on a different window pop-up, However I also tried adding this while creating FILE DSN. This did not work either]
Database=Database
Host=server.com
UserName=monetdb123
Password=monetdb123
Port=5120
Am I missing anything ? Any inputs on this would be helpful. Thanks!
## Comment 27612
Date: 2020-03-20 08:08:08 +0100
From: Arshad <<arshad.super>>
Update 2
========
Since, this is my first time creating File DSN under windows. I went ahead and tried previous version just to check if there are differences in behavior. Tried with ODBC Version 11.31.13 and 11.33.11, the behavior is same as described earlier.
DEBUG TRACE FILE GENERATED WITH 11.31.13
========================================
odbcad32 3f64-394c ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x0051C96C
odbcad32 3f64-394c EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x0051C96C ( 0x0446C410)
odbcad32 3f64-394c ENTER SQLSetEnvAttr
SQLHENV 0x0446C410
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 380 <SQL_OV_ODBC3_80>
SQLINTEGER 0
odbcad32 3f64-394c EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x0446C410
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 380 <SQL_OV_ODBC3_80>
SQLINTEGER 0
odbcad32 3f64-394c ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0446C410
SQLHANDLE * 0x0051C984
odbcad32 3f64-394c EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0446C410
SQLHANDLE * 0x0051C984 ( 0x0674B170)
odbcad32 3f64-394c ENTER SQLDriverConnectW
HDBC 0x0674B170
HWND 0x00350C40
WCHAR * 0x7B932440 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x7B932440
SWORD -3
SWORD * 0x00000000
UWORD 1 <SQL_DRIVER_COMPLETE>
odbcad32 3f64-394c EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 0x0674B170
HWND 0x00350C40
WCHAR * 0x7B932440 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x7B932440
SWORD -3
SWORD * 0x00000000
UWORD 1 <SQL_DRIVER_COMPLETE>
DIAG [28000] [MonetDB][ODBC Driver 11.31.13]Invalid authorization specification (0)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
odbcad32 3f64-394c ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0674B170
odbcad32 3f64-394c EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0674B170
odbcad32 3f64-394c ENTER SQLFreeHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x0446C410
odbcad32 3f64-394c EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x0446C410
## Comment 27627
Date: 2020-03-26 17:55:23 +0100
From: Martin van Dinther <<martin.van.dinther>>
We can reproduce the problem with the File DSN on MS Windows.
Currently no connection-parameters dialog is pop-ing up, hence you miss essential connection parameters and the connection fails as reported.
I tried to specify the connection parameters via the "Advanced..."-button option and enter:
DRIVER={MonetDB ODBC Driver}
HOST=localhost
PORT=50000
DATABASE=demo
UID=monetdb
PWD=monetdb
but the ODBC Data Source Adminstrator program removes the PWD before storing the File DSN. As the PWD setting is required for a succesful connection, the File DSN will not be usable. So this also does not work.
As a workaround you can use a User DSN (or System DSN if you have admin privileges).
The implementation of a fix is not trivial as it requires windows specific code.
Can you explain why you (need to) use a File DSN instead of a User DSN?
And why you think the importance must be: high & major?
## Comment 27631
Date: 2020-03-27 04:35:43 +0100
From: Arshad <<arshad.super>>
Hi Martin,
Thanks for looking into this!
Your are Correct, User-DSN does work as I mentioned in my bug-report. But the nature of the project (without giving to much details) is that we need the flexibility of FILE DSN.
My Understanding at the time of reporting the bug was that it was not a sub-set of functionality which was failing. The "whole" FILE DSN connection failed to initiate, and this is like breaking the full feature. However, please feel free to choose the bug status of your choice for this bug.
Any further information you required please do let me know. I would be happy to provide.
Thanks Again!!
## Comment 27657
Date: 2020-04-12 01:22:16 +0200
From: Arshad <<arshad.super>>
Hi Martin,
I was trying to build MonetDB project under Windows to see if I could contribute towards this bug. I could build server,client binaries as well as obdcinstall.exe. However I could not trigger the NT/mksqlwxs.py and NT/mkodbcwxs.py to generate MonetDB5-SQL-Installer.wxs and MonetDB-ODBC-Installer.wxs.
I was under impression that this would be triggered by nmake on the top level. This however as I said is not happening as I could see server, client binaries but no *.wxs generated.
This is how I am executing the build.
nmake.exe /D /K /nologo /f ../NT/Makefile HAVE_TESTING=1 HAVE_ODBC=1 ENABLE_STRICT=1 DEBUG=0 HAVE_GDK=0 HAVE_MAPI=1 HAVE_PCRE=1
Could you please help me out on how to generate the installer wxs? I do have the necessary WixToolSet installed, but this would come once the *.wxs is generated.
D:\>where candle
C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe
D:\>where light
C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe
Thanks
Arshad
PS: The build document I am following is https://github.com/MonetDB/MonetDB/blob/master/buildtools/doc/windowsbuild.rst
## Comment 27660
Date: 2020-04-14 20:53:18 +0200
From: Martin van Dinther <<martin.van.dinther>>
The NT/Makefile has a rule:
makewxs:
$(PYTHON) $(NT)\mksqlwxs.py $(VERSION) "$(MAKE_INCLUDEFILE)" "$(prefix)" > "$(prefix)\MonetDB5-SQL-Installer.wxs"
$(PYTHON) $(NT)\mkodbcwxs.py $(VERSION) "$(MAKE_INCLUDEFILE)" "$(prefix)" > "$(prefix)\MonetDB-ODBC-Installer.wxs"
running in NT directory
> nmake makewxs
should create the needed .wxs files
## Comment 27661
Date: 2020-04-15 09:43:09 +0200
From: Arshad <<arshad.super>>
Thanks Martin.
I was calling the top level NT\Makefile nothing unfavorable caught my eye.
<snip>
cd "perl" && "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86\nmake.exe" /nologo DEBUG=1 "prefix=D:\monetwinbuild\MonetDB\OBJFL" "bits=32" all
if not exist "NT" mkdir "NT"
copy ".\..\..\clients\NT\Makefile.msc" "NT\Makefile"
1 file(s) copied.
<snip>
..and build continued from there.
Now that I try what you recommended. Looks like I am missing a file dependency "makedefs.txt". This is something which is generated? Where do we get "makedefs.txt" ? I am checking on my end also...
<snip>
nmake.exe /D /K /nologo /f ..\NT\Makefile makewxs
makewxs target does not exist
python .\..\NT\mksqlwxs.py 11.38.0 "" "D:\monetwinbuild\MonetDB\OBJFL" > "D:\monetwinbuild\MonetDB\OBJFL\MonetDB5-SQL-Installer.wxs"
Traceback (most recent call last):
File ".\..\NT\mksqlwxs.py", line 286, in <module>
main()
File ".\..\NT\mksqlwxs.py", line 38, in main
for line in open(sys.argv[2]):
FileNotFoundError: [Errno 2] No such file or directory: ''
NMAKE : warning U4010: 'makewxs' : build failed; /K specified, continuing ...
<snip>
## Comment 27662
Date: 2020-04-15 12:07:11 +0200
From: @sjoerdmullender
Please read the file buildtools/doc/windowsbuild.rst. It contains valuable information about building on Windows. It may not be completely up-to-date, but it does describe a variable MAKE_INCLUDEFILE which is used by the makefile rule to build the .wxs files.
| Fails to Create A "FILE DSN" (Monetdb ODBC) under Windows 10 Enterprise | https://api.github.com/repos/MonetDB/MonetDB/issues/6834/comments | 0 | 2020-11-30T16:54:36Z | 2024-06-28T13:07:44Z | https://github.com/MonetDB/MonetDB/issues/6834 | 753,640,816 | 6,834 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-18 08:23:00 +0100
From: miro.mannino
To: buildtools devs <<bugs-buildtools>>
Version: 11.35.19 (Nov2019-SP3)
CC: @PedroTadim
Last updated: 2020-06-15 09:29:50 +0200
## Comment 27606
Date: 2020-03-18 08:23:00 +0100
From: miro.mannino
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Build Identifier:
We would like to use the embedded python (i.e. monetdb set embedpy=true).
Our understanding is that the usual monetdb doesn't have this python extension.
For this reason we are trying to compile the latest monedb version from
https://www.monetdb.org/downloads/sources/Latest/
After that if we try to do monetdb set embedpy=true we receive this error:
set: no such property: embedpy
We suspect that maybe this latest version the Nov2019-SP3 doesn't have python?
On the other side we are not able to compile the source code from the link provided in:
https://www.monetdb.org/blog/embedded-pythonnumpy-monetdb
That code seems outdated and unable to compile, both for linux (ubuntu) or macos (catalina).
Does the latest Nov2019-SP3 have python or it is discontinued?
Thank you!
Reproducible: Always
## Comment 27607
Date: 2020-03-18 09:19:01 +0100
From: @PedroTadim
Hello Miro,
To be able to compile MonetDB from sources with embedded-python, it requires to have the python development packages, plus numpy and numpy development packages installed on the system. Are you sure you have these?
Meanwhile I updated the blogpost with a necessary 'make' step before 'make install'.
Is also important that we removed Python 2 support in the default branch of MonetDB, which will be affected on the next feature release. This means the 'embedpy' property is now obsolete and you should use 'embedpy3'. Make sure you have Python 3 development packages installed.
Best regards,
Pedro
| no such property: embedpy, or missing python during compilation? | https://api.github.com/repos/MonetDB/MonetDB/issues/6833/comments | 0 | 2020-11-30T16:54:33Z | 2024-06-28T13:07:43Z | https://github.com/MonetDB/MonetDB/issues/6833 | 753,640,789 | 6,833 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-15 09:54:51 +0100
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: dnv, @PedroTadim, @yzchang
Last updated: 2020-08-18 11:24:26 +0200
## Comment 27593
Date: 2020-03-15 09:54:51 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:73.0) Gecko/20100101 Firefox/73.0
Build Identifier:
- The prepared statement disappears when it is called wrongly without warning.
- There should be a method to explicitly drop a prepared statement
- the phrase "EXEC 7(...)" hints at arguments being expected, which is not true.
- Otherwise the calling method would be nice to be rendered as a SQL FUNCTION signature rather than the argument table
- it would be nice to give the prepared statement a name (= syntax sugar for procedure/function def. without arguments)
Reproducible: Always
### Steps to Reproduce:
sql>prepare select 1;
execute prepared statement using: EXEC 13(...)
+---------+--------+-------+--------+-------+--------+
| type | digits | scale | schema | table | column |
+=========+========+=======+========+=======+========+
| tinyint | 1 | 0 | | | |
+---------+--------+-------+--------+-------+--------+
sql>select * from prepared_statements();
+-----------+----------+-------------+-------------------+----------------------------+
| sessionid | username | statementid | statement | created |
+===========+==========+=============+===================+============================+
| 0 | monetdb | 13 | prepare select 1; | 2020-03-15 08:39:28.200392 |
+-----------+----------+-------------+-------------------+----------------------------+
1 tuple
sql>exec 13();
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
sql>exec 13;
syntax error, unexpected SCOLON, expecting '(' in: "exec 13;"
sql>select * from prepared_statements();
+-----------+----------+-------------+-----------+---------+
| sessionid | username | statementid | statement | created |
+===========+==========+=============+===========+=========+
+-----------+----------+-------------+-----------+---------+
0 tuples
sql>prepare select 1;
execute prepared statement using: EXEC 17(...)
sql>drop function 17();
syntax error, unexpected sqlINT in: "drop function 17"
sql>prepare myid as select 1;
syntax error, unexpected IDENT in: "prepare myid"
sql>prepare select 1;
execute prepared statement using: EXEC 21(...)
sql>exec 21(cast( 1 as tinyint));
EXEC called with wrong number of arguments: expected 0, got 1
## Comment 27608
Date: 2020-03-18 14:51:38 +0100
From: @PedroTadim
The answers for each bullet point:
- Deleting prepared statements after error is a feature, which I think it should be revised, because we now offer the possibility to deallocate them.
- Deallocate statements have been added in default (also on Jun2020 branch) with this purpose.
- A prepared statement is seen as function that is called later. A function without arguments in SQL is called with just (). The same for prepared statements. To add the arguments to the EXEC it requires a small change in mclient.
- We allow digits in identifiers, which means calling exec "11" could mean to execute the prepared statement named "11" or the query with the cache id 11. We could disallow a numerical digit as the first letter on the prepared statement to allow this.
## Comment 27936
Date: 2020-07-24 14:10:02 +0200
From: @yzchang
(In reply to Pedro Ferreira from comment 1)
> The answers for each bullet point:
>
> - Deleting prepared statements after error is a feature, which I think it
> should be revised, because we now offer the possibility to deallocate them.
I'd love to see this feature be revised. How about only delete (is it called "deallocate" actually?) a prepared statement when explicitly instructed?
> - Deallocate statements have been added in default (also on Jun2020 branch)
> with this purpose.
how does this work? do we have documentation in the monetdb.org website?
## Comment 27943
Date: 2020-07-26 11:56:15 +0200
From: @PedroTadim
I added the deallocate information on mhelp.
## Comment 27990
Date: 2020-08-18 11:24:26 +0200
From: Karl Seguin <<dnv>>
In addition to revisiting the auto-deallocate on error, I'd also like to see something like postgres' unnamed prepared statements which automatically deallocates after use.
Even better would be a prepare+execute+close in a single statement, but this would require monetdb to be able to infer the types better (e.g., allow exec 5('2010-01-10') instead of exec 5(date '2010-01-01')). I assume this would be possible since it can figure it out for non-prepared statements.
From a security perspective, drivers should be encouraged to prefer prepared statements, so improving their usability would be nice.
| Prepared statements admin | https://api.github.com/repos/MonetDB/MonetDB/issues/6832/comments | 0 | 2020-11-30T16:54:30Z | 2024-06-28T13:07:42Z | https://github.com/MonetDB/MonetDB/issues/6832 | 753,640,759 | 6,832 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-12 17:13:15 +0100
From: @evangelos-dimitriadis
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.35.19 (Nov2019-SP3)
CC: @evangelos-dimitriadis, @njnes
Last updated: 2020-08-25 14:10:09 +0200
## Comment 27586
Date: 2020-03-12 17:13:15 +0100
From: @evangelos-dimitriadis
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
Build Identifier:
While having a master and a slave configured for lazy replication the slave will not update the database with new columns from master.
Reproducible: Always
### Steps to Reproduce:
0. See script in Additional Information or:
1. Create master and slave db.
2. Create a table in master.
3. Replicate in slave.
4. Alter table adding a column in master.
5. Replicate in slave.
### Actual Results:
Slave does not create the extra column.
### Expected Results:
Both master and slave should have the extra column.
!/bin/bash
monetdbd create dbfarm_master
if [ ! -d "/dbfarm/master" ];
then
monetdbd start dbfarm_master
monetdb create master
monetdb release master
monetdb create slave
monetdb release slave
mclient -d master --statement "CALL wlc.beat(0);"
mclient -d master --statement "CALL wlc.master();"
mclient -d master --statement "CREATE TABLE IF NOT EXISTS alpha (id bigint PRIMARY KEY AUTO_INCREMENT, data bigint);"
mclient -d slave --statement "CALL wlr.master('master');"
sleep 3
mclient -d slave --statement "CALL wlr.replicate();"
mclient -d master --statement "ALTER TABLE sys.alpha ADD extra int;"
sleep 3
mclient -d slave --statement "CALL wlr.replicate();"
mclient -d master --statement "SELECT * FROM sys.alpha;"
mclient -d slave --statement "SELECT * FROM sys.alpha;"
else
echo "Existing database found."
fi
| Lazy Replication: Slave DB does not replicate the creation of new columns | https://api.github.com/repos/MonetDB/MonetDB/issues/6831/comments | 0 | 2020-11-30T16:54:26Z | 2024-06-28T13:07:41Z | https://github.com/MonetDB/MonetDB/issues/6831 | 753,640,713 | 6,831 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-03-12 14:15:33 +0100
From: bharath <<bharath.thamanna>>
To: GDK devs <<bugs-common>>
Version: 11.35.19 (Nov2019-SP3)
Last updated: 2020-03-12 15:46:09 +0100
## Comment 27584
Date: 2020-03-12 14:15:33 +0100
From: bharath <<bharath.thamanna>>
Created attachment 643
Merovingian
We are trying to upgrade from MonetDB-11.27.13_PY8 to MonetDB-11.35.19 .
We had created a new DBfirm with the new version MonetDB-11.35.19 .
And copied the old version DB directory to this dbfirm location , But while starting up this DB , we are not able to bring up the database . This issue is in reference to the bug_id 6740 .
I have attached the Merovingian log for the same .
> Attached file: [merovingian.log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6830_merovingian.log_643) (text/plain, 20256 bytes)
> Description: Merovingian
## Comment 27585
Date: 2020-03-12 15:46:09 +0100
From: @sjoerdmullender
This looks like your database is corrupt and was already corrupt before the upgrade. The new version has added a check for this kind of thing and refuses to start, but the condition was preexisting.
If you look in the merovingian.log file that you provided, you see a message about a missing file (look for BBPcheckbats). You might be able to start the database if you create that file (or all of them if there are multiple) and create them so that they are large enough. Of course, since the file is missing, you don't have the data that should be in there. You could make up data (e.g. zero bytes) to fill out the file. The required size can be found in the file BBP.dir which is either in the "bat" subdirectory or in "bat/BACKUP". The file is ASCII, so readable. The size is on the line that contains the name of the missing file in the fourth column (without the .tail extension). The size (in bytes) is the 22nd column (probably the second from the end, but that depends on the type of the column).
Another way to find the correct line is to realize that the basename of the file is the octal representation of a number. The decimal representation of that number is in the first column of the BBP.dir file.
| While upgrading the database from MonetDB-11.27.13_PY8 to MonetDB-11.35.19 we are not able to bring up the database | https://api.github.com/repos/MonetDB/MonetDB/issues/6830/comments | 0 | 2020-11-30T16:54:22Z | 2024-06-28T13:07:40Z | https://github.com/MonetDB/MonetDB/issues/6830 | 753,640,667 | 6,830 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-21 10:25:12 +0100
From: @bernardom29
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @PedroTadim
Last updated: 2020-02-24 09:32:58 +0100
## Comment 27576
Date: 2020-02-21 10:25:12 +0100
From: @bernardom29
The NTILE window function is returning incorrect results in some cases. In the example below, the function divides the result set in more buckets than specified in the function argument.
How to reproduce:
1 - Create table and add values
create table employees (dep varchar(10), name varchar(20), salary double, hire_date date);
insert into employees values
('mgmt', 'Smith',81,str_to_date('10-08-2019', '%d-%m-%Y')),
('dev', 'Jones',55,str_to_date('9-08-2019', '%d-%m-%Y')),
('sls', 'Williams',55,str_to_date('14-07-2019', '%d-%m-%Y')),
('sls', 'Taylor',62,str_to_date('13-08-2019', '%d-%m-%Y')),
('dev', 'Brown',62,str_to_date('6-06-2019', '%d-%m-%Y')),
('mgmt', 'Davies',84,str_to_date('4-06-2019', '%d-%m-%Y')),
('sls', 'Evans',87,str_to_date('1-09-2019', '%d-%m-%Y')),
('sls', 'Wilson',72,str_to_date('21-09-2019', '%d-%m-%Y')),
('sls', 'Thomas',72,str_to_date('12-06-2019', '%d-%m-%Y')),
('mgmt', 'Johnson',100,str_to_date('12-07-2019', '%d-%m-%Y'));
2 - Execute this query, which gives incorrect results
SELECT dep, name, salary, NTILE(4) OVER (ORDER BY hire_date) FROM employees;
It should divide the 10 rows into 4 buckets, but it returns a 5 for the last row, which is incorrect.
The function returns correct results in the case of 2 buckets, for example.
## Comment 27577
Date: 2020-02-21 11:19:22 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [670675a1ce57](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=670675a1ce57) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=670675a1ce57](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=670675a1ce57)
Changeset description:
Added test and fix for bug #6829. Changed ntile implementation for a more generic one
| NTILE window function returns incorrect results | https://api.github.com/repos/MonetDB/MonetDB/issues/6829/comments | 0 | 2020-11-30T16:54:19Z | 2024-06-27T13:08:11Z | https://github.com/MonetDB/MonetDB/issues/6829 | 753,640,633 | 6,829 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-20 16:25:46 +0100
From: @bernardom29
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @PedroTadim, @yzchang
Last updated: 2020-06-03 16:58:53 +0200
## Comment 27572
Date: 2020-02-20 16:25:46 +0100
From: @bernardom29
Monetdb server is crashing when executing a query with a window function which uses an extracted date (e.g. EXTRACT(MONTH FROM date)) as the order for the window. This doesn't happen if the window is also partitioned or if the window is ordered by the whole date.
How to reproduce:
1 - Create test table and add some values
create table employees (dep varchar(10), name varchar(20), salary double, hire_date date);
insert into employees values
('mgmt', 'Smith',81,str_to_date('10-08-2019', '%d-%m-%Y')),
('dev', 'Jones',55,str_to_date('9-08-2019', '%d-%m-%Y')),
('sls', 'Williams',55,str_to_date('14-07-2019', '%d-%m-%Y')),
('sls', 'Taylor',62,str_to_date('13-08-2019', '%d-%m-%Y')),
('dev', 'Brown',62,str_to_date('6-06-2019', '%d-%m-%Y')),
('mgmt', 'Davies',84,str_to_date('4-06-2019', '%d-%m-%Y')),
('sls', 'Evans',87,str_to_date('1-09-2019', '%d-%m-%Y')),
('sls', 'Wilson',72,str_to_date('21-09-2019', '%d-%m-%Y')),
('sls', 'Thomas',72,str_to_date('12-06-2019', '%d-%m-%Y')),
('mgmt', 'Johnson',100,str_to_date('12-07-2019', '%d-%m-%Y'));
2 - Execute this query, which crashes the server
SELECT dep, name, salary, SUM(salary) OVER (ORDER BY EXTRACT(MONTH FROM hire_date)) salary_sum FROM employees;
Note that these two queries don't crash the server:
SELECT dep, name, salary, SUM(salary) OVER (ORDER BY hire_date) salary_sum FROM employees;
SELECT dep, name, salary, SUM(salary) OVER (PARTITION BY dep ORDER BY EXTRACT(MONTH FROM hire_date)) salary_sum FROM employees;
## Comment 27573
Date: 2020-02-20 16:40:07 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [34fa1ae0cd2c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=34fa1ae0cd2c) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=34fa1ae0cd2c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=34fa1ae0cd2c)
Changeset description:
Added test and output for Bug #6828. It gives right output on Nov2019 branch, but crashes on linear-hashing
## Comment 27574
Date: 2020-02-20 16:50:36 +0100
From: @yzchang
Yeah, it crashes on default, not on Nov2019.
## Comment 27575
Date: 2020-02-20 17:18:55 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [71a80133d806](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=71a80133d806) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=71a80133d806](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=71a80133d806)
Changeset description:
Fix for bug #6828, ie make sure window function call parameters have labels
| Server crashes when executing a window query with ordering by EXTRACT date | https://api.github.com/repos/MonetDB/MonetDB/issues/6828/comments | 0 | 2020-11-30T16:54:16Z | 2024-06-27T13:08:10Z | https://github.com/MonetDB/MonetDB/issues/6828 | 753,640,590 | 6,828 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-20 15:48:36 +0100
From: @bernardom29
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-02-24 09:32:58 +0100
## Comment 27570
Date: 2020-02-20 15:48:36 +0100
From: @bernardom29
The CUME_DIST() window function is returning incorrect results, even returning values above 1 (the return values should always be within 0 and 1).
Overview of CUME_DIST function: https://www.sqlitetutorial.net/sqlite-window-functions/sqlite-cume_dist/
How to reproduce:
1 - Create test table and add some values
create table employees (dep varchar(10), name varchar(20), salary double);
insert into employees values
('mgmt', 'Smith',81),
('dev', 'Jones',55),
('sls', 'Williams',55),
('sls', 'Taylor',62),
('dev', 'Brown',62),
('mgmt', 'Davies',84),
('sls', 'Evans',87),
('sls', 'Wilson',72),
('sls', 'Thomas',72),
('mgmt', 'Johnson',100);
2 - Execute one of these queries, which give incorrect results:
SELECT dep, name, salary, CUME_DIST() OVER (partition by dep ORDER BY salary) cume_dist_val FROM employees;
SELECT dep, name, salary, CUME_DIST() OVER (PARTITION BY dep) cume_dist_val FROM employees;
The expected results would be values between 0 and 1, with each row's value being the number of rows with values lower or equal divided by the total number of rows in the window or partition.
The actual results go above 1 and are incorrect.
## Comment 27571
Date: 2020-02-20 16:11:11 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [176ea6bea667](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=176ea6bea667) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=176ea6bea667](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=176ea6bea667)
Changeset description:
Added test and fix for bug #6827, ie reset accumulator variable after each partition
| CUME_DIST window function returns incorrect results | https://api.github.com/repos/MonetDB/MonetDB/issues/6827/comments | 0 | 2020-11-30T16:54:13Z | 2024-06-27T13:08:09Z | https://github.com/MonetDB/MonetDB/issues/6827 | 753,640,553 | 6,827 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-18 15:58:20 +0100
From: @gijzelaerr
To: Merovingian devs <<bugs-merovingian>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Duplicates: #6821
Last updated: 2020-02-19 08:42:15 +0100
## Comment 27565
Date: 2020-02-18 15:58:20 +0100
From: @gijzelaerr
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36
Build Identifier:
hi! When I try to enable the embedpy3 on Ubuntu Bionic I get the error:
main thread:!ERROR:MALException:pyapi.eval:PY000!Failed to initialize embedded python
In the merovingian log. I installed the monetdb-python3 package. The same thing seems to work on Ubuntu Eoan (19.10).
Reproducible: Always
### Steps to Reproduce:
On an empty Ubuntu 18.04 system:
apt-get update
apt-get install -qy software-properties-common sudo wget
apt-get update -q
sh -c "echo 'deb http://dev.monetdb.org/downloads/deb/ bionic monetdb' > /etc/apt/sources.list.d/monetdb.list"
wget --output-document=- http://dev.monetdb.org/downloads/MonetDB-GPG-KEY | apt-key add -
apt-get update -q
apt-get install -qy monetdb5-sql monetdb-client monetdb-python3
export DBFARM=/var/lib/monetdb
mkdir -p -m 770 ${DBFARM}
chown -R monetdb.monetdb ${DBFARM}
sudo -u monetdb monetdbd create ${DBFARM}
sudo -u monetdb monetdbd start ${DBFARM}
sudo -u monetdb monetdb create demo
sudo -u monetdb monetdb set embedpy3=true demo
sudo -u monetdb monetdb release demo
sudo -u monetdb monetdb start demo
## Comment 27567
Date: 2020-02-19 08:42:15 +0100
From: @PedroTadim
*** This bug has been marked as a duplicate of bug #6821 ***
| main thread:!ERROR:MALException:pyapi.eval:PY000!Failed to initialize embedded python | https://api.github.com/repos/MonetDB/MonetDB/issues/6826/comments | 0 | 2020-11-30T16:54:09Z | 2024-06-28T09:31:33Z | https://github.com/MonetDB/MonetDB/issues/6826 | 753,640,508 | 6,826 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-18 13:50:10 +0100
From: @gijzelaerr
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: renalkoclok
Last updated: 2020-06-03 09:16:39 +0200
## Comment 27564
Date: 2020-02-18 13:50:10 +0100
From: @gijzelaerr
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36
Build Identifier:
Not sure where to report this. If I sort bugs on time like here:
https://www.monetdb.org/bugzilla/buglist.cgi?bug_status=__all__&content=to%20a%20directory%20not%20ending%20in&list_id=11617&query_format=specific&order=changeddate%2Cpriority%2Cbug_severity&query_based_on=
I get an error 'invalid local time'
Reproducible: Always
## Comment 27771
Date: 2020-06-03 09:16:39 +0200
From: @sjoerdmullender
The content of attachment 672 has been deleted for the following reason:
spam
| bugzilla: Invalid local time for date in time zone: Europe/Amsterdam | https://api.github.com/repos/MonetDB/MonetDB/issues/6825/comments | 0 | 2020-11-30T16:54:05Z | 2024-06-28T13:07:39Z | https://github.com/MonetDB/MonetDB/issues/6825 | 753,640,454 | 6,825 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-18 13:46:54 +0100
From: @gijzelaerr
To: buildtools devs <<bugs-buildtools>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-07-21 12:09:45 +0200
## Comment 27563
Date: 2020-02-18 13:46:54 +0100
From: @gijzelaerr
When i compile and install MonetDB 11.39.9 using:
./configure --enable-py3integration --disable-py2integration --prefix=/home/gijs/Opt/monetdb/
I get the error:
$ make install | grep libtool
/bin/bash ../../libtool --mode=install /usr/bin/install -c libstream.la '/home/gijs/Opt/monetdb/lib'
libtool: install: /usr/bin/install -c .libs/libstream.so.13.0.3 /home/gijs/Opt/monetdb/lib/libstream.so.13.0.3
libtool: install: (cd /home/gijs/Opt/monetdb/lib && { ln -s -f libstream.so.13.0.3 libstream.so.13 || { rm -f libstream.so.13 && ln -s libstream.so.13.0.3 libstream.so.13; }; })
libtool: install: (cd /home/gijs/Opt/monetdb/lib && { ln -s -f libstream.so.13.0.3 libstream.so || { rm -f libstream.so && ln -s libstream.so.13.0.3 libstream.so; }; })
libtool: install: /usr/bin/install -c .libs/libstream.lai /home/gijs/Opt/monetdb/lib/libstream.la
libtool: warning: remember to run 'libtool --finish /usr/local/lib'
/bin/bash ../../libtool --mode=install /usr/bin/install -c libmapi.la '/home/gijs/Opt/monetdb/lib'
libtool: install: /usr/bin/install -c .libs/libmapi.so.12.0.2 /home/gijs/Opt/monetdb/lib/libmapi.so.12.0.2
libtool: install: (cd /home/gijs/Opt/monetdb/lib && { ln -s -f libmapi.so.12.0.2 libmapi.so.12 || { rm -f libmapi.so.12 && ln -s libmapi.so.12.0.2 libmapi.so.12; }; })
libtool: install: (cd /home/gijs/Opt/monetdb/lib && { ln -s -f libmapi.so.12.0.2 libmapi.so || { rm -f libmapi.so && ln -s libmapi.so.12.0.2 libmapi.so; }; })
libtool: install: /usr/bin/install -c .libs/libmapi.lai /home/gijs/Opt/monetdb/lib/libmapi.la
libtool: finish: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/sbin" ldconfig -n /home/gijs/Opt/monetdb/lib
in a given directory, LIBDIR, you must either use libtool, and
/bin/bash ../../libtool --mode=install /usr/bin/install -c mclient msqldump stethoscope tachograph tomograph '/home/gijs/Opt/monetdb/bin'
libtool: warning: '../../common/stream/libstream.la' has not been installed in '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/mclient /home/gijs/Opt/monetdb/bin/mclient
libtool: warning: '../../common/stream/libstream.la' has not been installed in '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/msqldump /home/gijs/Opt/monetdb/bin/msqldump
libtool: warning: '../../common/stream/libstream.la' has not been installed in '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/stethoscope /home/gijs/Opt/monetdb/bin/stethoscope
libtool: warning: '../../common/stream/libstream.la' has not been installed in '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/tachograph /home/gijs/Opt/monetdb/bin/tachograph
libtool: warning: '../../common/stream/libstream.la' has not been installed in '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/tomograph /home/gijs/Opt/monetdb/bin/tomograph
/bin/bash ../../../libtool --mode=install /usr/bin/install -c libMonetODBCs.la '/home/gijs/Opt/monetdb/lib'
libtool: install: /usr/bin/install -c .libs/libMonetODBCs.so /home/gijs/Opt/monetdb/lib/libMonetODBCs.so
libtool: install: /usr/bin/install -c .libs/libMonetODBCs.lai /home/gijs/Opt/monetdb/lib/libMonetODBCs.la
libtool: warning: remember to run 'libtool --finish /usr/local/lib'
/bin/bash ../../../libtool --mode=install /usr/bin/install -c libMonetODBC.la '/home/gijs/Opt/monetdb/lib'
libtool: error: error: cannot install 'libMonetODBC.la' to a directory not ending in /usr/local/lib
make[8]: *** [Makefile:662: install-MonetODBCLTLIBRARIES] Error 1
The same just works fine with 11.35.3
## Comment 27566
Date: 2020-02-19 08:41:05 +0100
From: @PedroTadim
Hello Gijs, with some search on the Internet, I found this:
https://stackoverflow.com/questions/10279829/installing-glib-in-non-standard-prefix-fails
Do a 'make clean' after a re-run of configure.
Pedro
## Comment 27569
Date: 2020-02-19 09:20:51 +0100
From: @gijzelaerr
hm, interesting. Still, I would argue this is non-standard configure/make behaviour? I'm not reporting these issues to solve my own problems but attempting to improve the MonetDB install experience.
## Comment 27925
Date: 2020-07-21 11:33:42 +0200
From: @sjoerdmullender
I probably do this several times a day and never have this problem.
I have done this on all versions of MonetDB for a very long time.
So, this means it must be some difference in our environments, so please describe yours.
OS, version of libtool, all that kind of thing.
## Comment 27926
Date: 2020-07-21 11:49:13 +0200
From: @gijzelaerr
This is 5 months ago, I dont remember on what system I did this.
## Comment 27927
Date: 2020-07-21 11:52:43 +0200
From: @sjoerdmullender
May I conclude that you don't see this anymore then? Have you tried compiling the Jun2020 branch recently?
## Comment 27928
Date: 2020-07-21 11:59:26 +0200
From: @gijzelaerr
I'm currently working on the oscar branch only and have not seen this issue there.
## Comment 27929
Date: 2020-07-21 12:09:45 +0200
From: @sjoerdmullender
I know. The oscar branch doesn't use libtool, hence my mentioning the Jun2020 branch.
| libtool: error: error: cannot install 'libMonetODBC.la' to a directory not ending in /usr/local/lib | https://api.github.com/repos/MonetDB/MonetDB/issues/6824/comments | 0 | 2020-11-30T16:54:01Z | 2024-06-28T13:09:19Z | https://github.com/MonetDB/MonetDB/issues/6824 | 753,640,412 | 6,824 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-17 22:50:00 +0100
From: @drstmane
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2020-10-30 11:43:51 +0100
## Comment 27562
Date: 2020-02-17 22:50:00 +0100
From: @drstmane
"Note: The bam.seq_char function is currently only available in the bamloader branch, which will be merged into the next feature release of MonetDB."
on https://www.monetdb.org/Documentation/Extensions/LifeScience/functions
might be (long) outdated given
https://dev.monetdb.org/hg/MonetDB/shortlog/bamloader
## Comment 28242
Date: 2020-10-30 11:43:51 +0100
From: @drstmane
The page in question is now located at
https://www.monetdb.org/index.php/Documentation/ServerProgramming/ExtendingSQL/LifeScience/functions
| Outdated(?) note about BAMloader branch | https://api.github.com/repos/MonetDB/MonetDB/issues/6823/comments | 0 | 2020-11-30T16:53:58Z | 2024-06-28T13:09:19Z | https://github.com/MonetDB/MonetDB/issues/6823 | 753,640,371 | 6,823 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-17 22:03:35 +0100
From: @drstmane
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: @yzchang
Last updated: 2020-02-17 22:44:28 +0100
## Comment 27560
Date: 2020-02-17 22:03:35 +0100
From: @drstmane
The "MonetDb Solutions" link at the bottom of page
https://www.monetdb.org/Documentation/Extensions/LifeScience/install
points to "http://www.monetsbsolutions.com/"
instead of "http://www.monetdbsolutions.com/"
## Comment 27561
Date: 2020-02-17 22:44:28 +0100
From: @yzchang
Thanks, fixed
| Broken link to MonetDB Solutions | https://api.github.com/repos/MonetDB/MonetDB/issues/6822/comments | 0 | 2020-11-30T16:53:55Z | 2024-06-27T13:08:03Z | https://github.com/MonetDB/MonetDB/issues/6822 | 753,640,334 | 6,822 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-17 17:03:21 +0100
From: Arnold Kuzniar <<arnold.kuzniar>>
To: buildtools devs <<bugs-buildtools>>
Version: 11.35.9 (Nov2019-SP1)
CC: @gijzelaerr, @PedroTadim
Last updated: 2020-06-03 16:58:54 +0200
## Comment 27559
Date: 2020-02-17 17:03:21 +0100
From: Arnold Kuzniar <<arnold.kuzniar>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build Identifier:
I've tried the latest MonetDB (v11.35.9) with embedded Python 2/3 on Linux/Ubuntu but after starting the database crashes. Thanks for your help.
Reproducible: Always
### Steps to Reproduce:
$ sudo apt install monetdb5-sql monetdb-client monetdb-python2 monetdb-python3
$ apt list | grep monetdb
...
libmonetdb-client-odbc/bionic,now 11.35.9 amd64 [installed,auto-removable]
libmonetdb-client12/bionic,now 11.35.9 amd64 [installed,automatic]
libmonetdb-stream13/bionic,now 11.35.9 amd64 [installed,automatic]
libmonetdb19/bionic,now 11.35.9 amd64 [installed,automatic]
monetdb-client/bionic,now 11.35.9 amd64 [installed]
monetdb-python2/bionic,now 11.35.9 amd64 [installed]
monetdb-python3/bionic,now 11.35.9 amd64 [installed]
monetdb5-server/bionic,now 11.35.9 amd64 [installed,automatic]
monetdb5-sql/bionic,now 11.35.9 amd64 [installed]
...
$ monetdbd create mydbfarm
$ monetdbd start mydbfarm
$ monetdb create voc
$ monetdb release voc
$ monetdb set embedpy3=true voc or embedpy=true [embedpy3=false]
$ monetdb get all
name prop source value
voc name - voc
voc type default database
voc shared default yes
voc nthreads default 8
voc optpipe default default_pipe
voc readonly default no
voc embedr default no
voc embedpy default no
voc embedpy3 local yes
voc embedc default no
voc ipv6 default no
voc listenaddr default <unknown>
voc nclients default 64
voc dbextra default <unknown>
voc memmaxsize default <unknown>
voc vmmaxsize default <unknown>
$ monetdb start voc
### Actual Results:
starting database 'voc'... FAILED
start: starting 'voc' failed: database 'voc' appears to shut itself down after starting, check monetdbd's logfile (merovingian.log) for possible hints
2020-02-17 16:10:30 MSG merovingian[918]: starting database 'voc', up min/avg/max: 14s/14s/14s, crash average: 0.00 0.00 0.00 (1-1=0)
2020-02-17 16:10:31 MSG voc[3113]: arguments: /usr/bin/mserver5 --dbpath=/var/monetdb5/dbfarm/voc --set merovingian_uri=mapi:monetdb://silver:50000/voc --set mapi_open=false --set mapi_ipv6=false --set mapi_port=0 --set mapi_usock=/var/monetdb5/dbfarm/voc/.mapi.sock --set monet_vault_key=/var/monetdb5/dbfarm/voc/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set embedded_py=3
2020-02-17 16:10:31 MSG voc[3113]: MonetDB 5 server v11.35.9 (Nov2019-SP1)
2020-02-17 16:10:31 MSG voc[3113]: Serving database 'voc', using 8 threads
2020-02-17 16:10:31 MSG voc[3113]: Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
2020-02-17 16:10:31 MSG voc[3113]: Found 15.120 GiB available main-memory of which we use 12.323 GiB
2020-02-17 16:10:31 MSG voc[3113]: Copyright (c) 1993 - July 2008 CWI.
2020-02-17 16:10:31 MSG voc[3113]: Copyright (c) August 2008 - 2019 MonetDB B.V., all rights reserved
2020-02-17 16:10:31 MSG voc[3113]: Visit https://www.monetdb.org/ for further information
2020-02-17 16:10:31 MSG voc[3113]: Listening for UNIX domain connection requests on mapi:monetdb:///var/monetdb5/dbfarm/voc/.mapi.sock
2020-02-17 16:10:31 MSG voc[3113]: MonetDB/SQL module loaded
2020-02-17 16:10:31 ERR voc[3113]: main thread:!ERROR:MALException:pyapi.eval:PY000!Failed to initialize embedded python
2020-02-17 16:10:31 ERR voc[3113]: !MALException:pyapi.eval:PY000!Failed to initialize embedded python
2020-02-17 16:10:33 MSG merovingian[918]: database 'voc' (3113) has exited with exit status 0
2020-02-17 16:10:33 ERR control[918]: (local): failed to fork mserver: database 'voc' appears to shut itself down after starting, check monetdbd's logfile (/var/log/monetdb/merovingian.log) for possible hints
2020-02-17 16:13:16 MSG merovingian[918]: caught SIGTERM, starting shutdown sequence
2020-02-17 16:13:16 MSG control[918]: control channel closed
2020-02-17 16:13:16 MSG merovingian[918]: Merovingian 11.35.9 stopped
## Comment 27568
Date: 2020-02-19 08:42:15 +0100
From: @PedroTadim
*** Bug #6826 has been marked as a duplicate of this bug. ***
## Comment 27581
Date: 2020-03-02 10:03:07 +0100
From: @sjoerdmullender
Do you have python3-numpy installed?
It's a required package for embedded Python, so if it isn't installed it's a problem with the package dependencies.
In the mean time, you can install it and be on your way.
## Comment 27582
Date: 2020-03-02 17:54:19 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [b96cb465c3a9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b96cb465c3a9) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=b96cb465c3a9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=b96cb465c3a9)
Changeset description:
Add run-time dependencies for embedded languages.
This should fix bug #6821.
## Comment 27656
Date: 2020-04-08 11:41:02 +0200
From: @gijzelaerr
Sorry for the delay in response, but I can confirm that yes this resolves the issue!
thanks.
| Failed to start monetdb with embedded python | https://api.github.com/repos/MonetDB/MonetDB/issues/6821/comments | 0 | 2020-11-30T16:53:51Z | 2024-06-27T13:08:02Z | https://github.com/MonetDB/MonetDB/issues/6821 | 753,640,283 | 6,821 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-16 20:08:20 +0100
From: Arnold Kuzniar <<arnold.kuzniar>>
To: buildtools devs <<bugs-buildtools>>
Version: 11.35.3 (Nov2019)
Duplicates: #6794
Last updated: 2020-02-16 23:56:10 +0100
## Comment 27554
Date: 2020-02-16 20:08:20 +0100
From: Arnold Kuzniar <<arnold.kuzniar>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build Identifier:
Hi,
I wanted to use Python from within MonetDB but after starting the database crashes. I've tested separately with Python 2 and 3. Please find the commands including the logs below.
Thanks for your help.
Reproducible: Always
### Steps to Reproduce:
$ docker pull monetdb/monetdb
$ docker run --name monetdb -p 50000 -d monetdb/monetdb
$ docker exec -it monetdb bash
$ yum list installed monetdb*
Installed Packages
MonetDB.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB-SQL-server5.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB-SQL-server5-hugeint.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB-client.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB-release.noarch 1.3-1.monetdb @@commandline
MonetDB-stream.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB5-server.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB5-server-hugeint.x86_64 11.33.3-20190426.fc29 @monetdb
$ yum install MonetDB-python2.x86_64 MonetDB-python3.x86_64
$ yum list installed monetdb*
Installed Packages
MonetDB.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-SQL-server5.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-SQL-server5-hugeint.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-client.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-python2.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-python3.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB-release.noarch 1.3-1.monetdb @@commandline
MonetDB-stream.x86_64 11.33.3-20190426.fc29 @monetdb
MonetDB5-server.x86_64 11.35.3-20191125.fc29 @monetdb
MonetDB5-server-hugeint.x86_64 11.35.3-20191125.fc29 @monetdb
$ monetdb set embedpy3=true devdb or embedpy=true [embedpy3=false]
$ monetdb get all | grep embed
devdb embedr local yes
devdb embedpy default no
devdb embedpy3 local yes
devdb embedc default no
$ monetdb start devdb
### Actual Results:
starting database 'devdb'... FAILED
start: starting 'devdb' failed: database 'devdb' has crashed after starting, manual intervention needed, check monetdbd's logfile (/var/log/monetdb/merovingian.log) for details
$ cat /var/log/monetdb/merovingian.log
2020-02-16 18:23:54 MSG control[89]: (local): set property 'embedpy3' for database 'devdb' to 'true'
2020-02-16 18:24:03 MSG control[89]: (local): served status list
2020-02-16 18:24:03 MSG merovingian[89]: starting database 'devdb', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0)
2020-02-16 18:24:04 MSG devdb[186]: arguments: /usr/bin/mserver5 --dbpath=/var/monetdb5/dbfarm/devdb --set merovingian_uri=mapi:monetdb://c4308c8efcc1:50000/devdb --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/monetdb5/dbfarm/devdb/.mapi.sock --set monet_vault_key=/var/monetdb5/dbfarm/devdb/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set embedded_r=true --set embedded_py=3 --set monet_daemon=yes
2020-02-16 18:24:04 MSG devdb[186]: MonetDB 5 server v11.35.3 (Nov2019)
2020-02-16 18:24:04 MSG devdb[186]: Serving database 'devdb', using 8 threads
2020-02-16 18:24:04 MSG devdb[186]: Compiled for x86_64-redhat-linux-gnu/64bit with 128bit integers
2020-02-16 18:24:04 MSG devdb[186]: Found 15.120 GiB available main-memory of which we use 12.323 GiB
2020-02-16 18:24:04 MSG devdb[186]: Copyright (c) 1993 - July 2008 CWI.
2020-02-16 18:24:04 MSG devdb[186]: Copyright (c) August 2008 - 2019 MonetDB B.V., all rights reserved
2020-02-16 18:24:04 MSG devdb[186]: Visit https://www.monetdb.org/ for further information
2020-02-16 18:24:04 MSG devdb[186]: Listening for UNIX domain connection requests on mapi:monetdb:///var/monetdb5/dbfarm/devdb/.mapi.sock
2020-02-16 18:24:04 MSG devdb[186]: SQL catalog created, loading sql scripts once
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 09_like.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 10_math.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 12_url.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 13_date.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 14_inet.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 15_querylog.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 16_tracelog.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 17_temporal.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 18_index.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 20_vacuum.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 21_dependency_views.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 22_clients.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 23_skyserver.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 25_debug.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 26_sysmon.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 27_rejects.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 39_analytics.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 39_analytics_hge.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 40_json.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 40_json_hge.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 41_md5sum.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 45_uuid.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 46_profiler.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 51_sys_schema_extension.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 60_wlcr.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 61_wlcr.sql
2020-02-16 18:24:04 MSG devdb[186]: loading sql script: 72_fits.sql
2020-02-16 18:24:04 ERR devdb[186]: main thread:!ERROR:ParseException:SQLparser:3F000!CREATE PROCEDURE: external name fits.listdir not bound (sys.listdir)
2020-02-16 18:24:04 ERR devdb[186]: ParseException:SQLparser:3F000!CREATE PROCEDURE: external name fits.listdir not bound (sys.listdir)Fatal error during initialization:
2020-02-16 18:24:04 ERR devdb[186]: ParseException:SQLparser:3F000!CREATE PROCEDU
RE: external name fits.listdir not bound (sys.listdir)
2020-02-16 18:24:08 MSG merovingian[89]: database 'devdb' (186) has exited with exit status 1
2020-02-16 18:24:08 ERR control[89]: (local): failed to fork mserver: database 'devdb' has crashed after starting, manual intervention needed, check monetdbd's logfile (/var/log/monetdb/merovingian.log) for details
## Comment 27555
Date: 2020-02-16 22:42:03 +0100
From: @sjoerdmullender
This bug was fixed with the Nov2019-SP1 release (11.35.9). You should upgrade your system to at least Fedora 30 (since 29 has reached the end of its life) in order to upgrade to this release.
We do not generally support EOL systems.
If you really need to, you can try to build from source RPM.
*** This bug has been marked as a duplicate of bug #6794 ***
## Comment 27557
Date: 2020-02-16 23:56:10 +0100
From: Arnold Kuzniar <<arnold.kuzniar>>
Thanks, Sjoerd. Could you update the `monetdb/monetdb` Docker image to the latest release instead?
| Failed to start monetdb with embedded python | https://api.github.com/repos/MonetDB/MonetDB/issues/6820/comments | 0 | 2020-11-30T16:53:46Z | 2024-06-28T13:09:18Z | https://github.com/MonetDB/MonetDB/issues/6820 | 753,640,230 | 6,820 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-15 06:13:45 +0100
From: Alex Ossipov <<alexo15>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
Last updated: 2020-02-21 12:36:57 +0100
## Comment 27549
Date: 2020-02-15 06:13:45 +0100
From: Alex Ossipov <<alexo15>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36
Build Identifier:
When a new function is created it does not persist after db restart.It does not matter if autocommit is enabled or not.
Reproducible: Always
### Steps to Reproduce:
1.start mclient
2.create function. For example, from documentation:
CREATE FUNCTION python_times_two(i INTEGER) RETURNS INTEGER LANGUAGE PYTHON3 {
return i * 2
};
3.restart database:
monetdb stop -d test
monetdb start -d test
### Actual Results:
select python_times_two(i) from integers;
returns error:
SQL Error [42000]: SELECT: no such unary operator 'python_times_two(int)'
### Expected Results:
should return multiplied values.
## Comment 27550
Date: 2020-02-15 07:07:13 +0100
From: Alex Ossipov <<alexo15>>
Here are new details:
1. made a new database.
2. execute select * from sys.functions; successfully returns list of default functions
3. created a new function
sql>CREATE FUNCTION python_times_two(i INTEGER) RETURNS INTEGER LANGUAGE PYTHON3 {
more> return i * 2
more>};
operation successful
4.sql>select * from sys.functions where name ='python_times_two';
Could not allocate space
5.sql>select * from sys.functions;
GDK reported error: BATproject: does not match always
## Comment 27551
Date: 2020-02-15 12:16:15 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [57b40d3cc170](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=57b40d3cc170) made by Sjoerd Mullender <sjoerd@acm.org> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=57b40d3cc170](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=57b40d3cc170)
Changeset description:
Fix for bug #6819: add code for all external languages.
## Comment 27552
Date: 2020-02-15 12:18:11 +0100
From: @sjoerdmullender
I just created a fix for this problem.
A workaround might be to use language PYTHON instead of PYTHON3, even when actually using Python 3 as the embedded Python version (so still running mserver 5 with --set embedded_py=3).
## Comment 27558
Date: 2020-02-17 09:11:54 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [06ab95ace054](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=06ab95ace054) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=06ab95ace054](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=06ab95ace054)
Changeset description:
Added test for bug #6819
| functions do not persist | https://api.github.com/repos/MonetDB/MonetDB/issues/6819/comments | 0 | 2020-11-30T16:53:43Z | 2024-06-27T13:08:00Z | https://github.com/MonetDB/MonetDB/issues/6819 | 753,640,199 | 6,819 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-13 15:24:50 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-06-03 16:58:53 +0200
## Comment 27544
Date: 2020-02-13 15:24:50 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Build Identifier:
sql/backends/monet5/rel_bin.c:920: exp_bin: Assertion `0' failed.
mserver5 is killed.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (compiled from Nov2019 branch on 13 febr 2020 with assertions enabled: --enable-assert --disable-debug)
2. start mclient
3. run sql commands:
CREATE TABLE "dd_field" (
"TABEL" VARCHAR(25) NOT NULL,
"VELD" VARCHAR(25) NOT NULL,
"TYPE" VARCHAR(4) NOT NULL
);
select "TABEL", "VELD"
from dd_field f
where ("TABEL", "VELD") in (select "TABEL", "VELD" from dd_field);
-- no problemo
select "TABEL", "VELD"
from dd_field f
where (rtrim("TABEL"), rtrim("VELD")) in (select "TABEL", "VELD" from dd_field);
-- server reports: Assertion `0' failed and stops the server.
### Actual Results:
dinther@monetdb-nuc2 ~]$ ./start_INSTALL_mserver5.sh
builtin opt gdk_dbpath = /home/dinther/dev/dev/INSTALL/var/monetdb5/dbfarm/demo
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_ipv6 = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt embedded_py = 3
cmdline opt embedded_c = true
cmdline opt mapi_port = 41000
MonetDB 5 server v11.35.14 (hg id: 6146f33fc10b)
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
Found 31.237 GiB available main-memory of which we use 25.459 GiB
Copyright (c) 1993 - July 2008 CWI.
Copyright (c) August 2008 - 2020 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
MonetDB/Python3 module loaded
MonetDB/R module loaded
mserver5: /home/dinther/dev/dev/MonetDB/sql/backends/monet5/rel_bin.c:920: exp_bin: Assertion `0' failed.
./start_INSTALL_mserver5.sh: line 8: 895328 Aborted (core dumped) /home/dinther/dev/dev/INSTALL/bin/mserver5 -d10 --set embedded_r=true --set embedded_py=3 --set embedded_c=true --set mapi_port=41000
[dinther@monetdb-nuc2 ~]$
[dinther@monetdb-nuc2 Tests]$ mclient -p41000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.35.14 (hg id: 6146f33fc10b), 'demo'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE "dd_field" (
more> "TABEL" VARCHAR(25) NOT NULL,
more> "VELD" VARCHAR(25) NOT NULL,
more> "TYPE" VARCHAR(4) NOT NULL
more>);
operation successful
sql>select "TABEL", "VELD"
more> from dd_field f
more> where ("TABEL", "VELD") in (select "TABEL", "VELD" from dd_field)
more>;
+-------+------+
| TABEL | VELD |
+=======+======+
+-------+------+
0 tuples
sql>select "TABEL", "VELD"
more> from dd_field f
more> where ("TABEL", "VELD") in (select "TABEL", "VELD" from dd_field);
+-------+------+
| TABEL | VELD |
+=======+======+
+-------+------+
0 tuples
sql>select "TABEL", "VELD"
more> from dd_field f
more> where (rtrim("TABEL"), rtrim("VELD")) in (select "TABEL", "VELD" from dd_field);
sql>
write error on stream
[dinther@monetdb-nuc2 Tests]
### Expected Results:
No assertion error or killing of the server.
On windows (Nov2019-SP2 release candidate of 12 febr 2020 without assertions) I got:
client2:!ERROR:MALException:optimizer.garbagecollector:42000!Incorrect MAL plan encountered
instead.
## Comment 27545
Date: 2020-02-13 15:34:02 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [1b4a2a363dbc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1b4a2a363dbc) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1b4a2a363dbc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1b4a2a363dbc)
Changeset description:
Add test for bug #6818
## Comment 27546
Date: 2020-02-13 15:48:56 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [728077f72f6d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=728077f72f6d) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=728077f72f6d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=728077f72f6d)
Changeset description:
Set bug #6818 as KNOWNFAIL. Tuple matching IN operator was fixed in the subquery branch and it will be available in the next feature release
## Comment 27547
Date: 2020-02-13 17:16:33 +0100
From: Martin van Dinther <<martin.van.dinther>>
Additional test query:
select "TABEL", "VELD"
from dd_field f
where (rtrim("TABEL")) in (select "TABEL" from dd_field);
also has no problem.
So the problem occurs only when using multiple columns with an expression (such as rtrim()) are used, such as:
where (rtrim("TABEL"), rtrim("VELD")) in (select "TABEL", "VELD" from dd_field);
## Comment 27548
Date: 2020-02-14 05:51:58 +0100
From: Martin van Dinther <<martin.van.dinther>>
Additional Info:
It worked OK on older versions. I tested:
MonetDB 5 server v11.29.7 "Mar2018-SP1"
MonetDB 5 server v11.33.11 (Apr2019-SP1)
But fails since:
MonetDB 5 server v11.35.3 (Nov2019)
and releases:
MonetDB 5 server v11.35.9 (Nov2019-SP1)
MonetDB 5 server v11.35.13 (Nov2019-SP2)
with mclient showing:
sql>select "TABEL", "VELD"
more> from dd_field f
more> where (rtrim("TABEL"), rtrim("VELD")) in (select "TABEL", "VELD" from dd_field);
Error in optimizer garbageCollector
sql>
and mserver5 console lists:
client1:!ERROR:MALException:optimizer.garbagecollector:42000!Incorrect MAL plan encountered
client1:!ERROR:MALException:garbageCollector:42000!Error in optimizer garbageCollector
client1:!ERROR:MALException:garbageCollector:42000!Error in optimizer garbageCollector
| usage of multiple column expressions in where-clause (f(a), f(b)) in (select a, b) causes assertion failure on mserver5 | https://api.github.com/repos/MonetDB/MonetDB/issues/6818/comments | 0 | 2020-11-30T16:53:39Z | 2024-06-27T13:07:59Z | https://github.com/MonetDB/MonetDB/issues/6818 | 753,640,156 | 6,818 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-13 13:26:58 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-02-21 12:36:58 +0100
## Comment 27540
Date: 2020-02-13 13:26:58 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Build Identifier:
It is possible to run analyze on all tables existing in a schema or a specific table or even column.
However when a schema contains a stream table, it produces an error for the stream table (Table 'strt' is not persistent SQLState: 42S02) and stops analysing any other table in the schema.
This makes analyzing all tables in a schema, not possible anymore.
If a stream table is not persisted, analyze should skip it (like done with views).
Reproducible: Always
### Steps to Reproduce:
delete from statistics;
select count(*) from statistics;
CREATE STREAM TABLE "sys"."strt" (
"id" INTEGER NOT NULL,
"nm" VARCHAR(123) NOT NULL,
CONSTRAINT "strt_id_pkey" PRIMARY KEY ("id")
);
select * from "sys"."strt";
analyze "sys"."strt";
-- Error: Table 'strt' is not persistent SQLState: 42S02
select (count(*) > 0) as has_rows from statistics;
analyze sys;
-- Error: Table 'strt' is not persistent SQLState: 42S02
select (count(*) > 0) as has_rows from statistics;
drop table "sys"."strt";
-- now run analyze without the stream table
analyze sys;
select (count(*) > 0) as has_rows from statistics;
-- true (181)
delete from statistics;
### Actual Results:
sql>delete from statistics;
0 affected rows
sql>select count(*) from statistics;
+------+
| L2 |
+======+
| 0 |
+------+
1 tuple
sql>
sql>CREATE STREAM TABLE "sys"."strt" (
more> "id" INTEGER NOT NULL,
more> "nm" VARCHAR(123) NOT NULL,
more> CONSTRAINT "strt_id_pkey" PRIMARY KEY ("id")
more>);
operation successful
sql>
sql>select * from "sys"."strt";
+----+----+
| id | nm |
+====+====+
+----+----+
0 tuples
sql>
sql>analyze "sys"."strt";
Table 'strt' is not persistent
sql>-- Error: Table 'strt' is not persistent SQLState: 42S02
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| false |
+----------+
1 tuple
sql>
sql>analyze sys;
Table 'strt' is not persistent
sql>-- Error: Table 'strt' is not persistent SQLState: 42S02
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| false |
+----------+
1 tuple
sql>
sql>drop table "sys"."strt";
operation successful
sql>-- now run analyze without the stream table
sql>analyze sys;
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| true |
+----------+
1 tuple
sql>-- true (181)
sql>delete from statistics;
181 affected rows
sql>
### Expected Results:
sql>delete from statistics;
0 affected rows
sql>select count(*) from statistics;
+------+
| L2 |
+======+
| 0 |
+------+
1 tuple
sql>
sql>CREATE STREAM TABLE "sys"."strt" (
more> "id" INTEGER NOT NULL,
more> "nm" VARCHAR(123) NOT NULL,
more> CONSTRAINT "strt_id_pkey" PRIMARY KEY ("id")
more>);
operation successful
sql>
sql>select * from "sys"."strt";
+----+----+
| id | nm |
+====+====+
+----+----+
0 tuples
sql>
sql>analyze "sys"."strt";
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| false |
+----------+
1 tuple
sql>
sql>analyze sys;
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| true |
+----------+
1 tuple
sql>
sql>drop table "sys"."strt";
operation successful
sql>-- now run analyze without the stream table
sql>analyze sys;
sql>select (count(*) > 0) as has_rows from statistics;
+----------+
| has_rows |
+==========+
| true |
+----------+
1 tuple
sql>-- true (181)
sql>delete from statistics;
181 affected rows
sql>
## Comment 27541
Date: 2020-02-13 13:59:26 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [7832d33851e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7832d33851e5) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=7832d33851e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=7832d33851e5)
Changeset description:
add test for bug #6817
## Comment 27543
Date: 2020-02-13 14:24:37 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [dda55ac48ee9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dda55ac48ee9) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=dda55ac48ee9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=dda55ac48ee9)
Changeset description:
Fix for bug #6817
| running analyze on a schema which contains a stream table stops with an error | https://api.github.com/repos/MonetDB/MonetDB/issues/6817/comments | 0 | 2020-11-30T16:53:37Z | 2024-06-27T13:07:58Z | https://github.com/MonetDB/MonetDB/issues/6817 | 753,640,123 | 6,817 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-02-05 12:55:01 +0100
From: Manuel <<manuel>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-02-21 12:36:58 +0100
## Comment 27536
Date: 2020-02-05 12:55:01 +0100
From: Manuel <<manuel>>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Build Identifier:
I am using SQuirrel configured to connect to a monetdb instance running the latest version.
I open two connections to the same database instance.
On the first I submit the following SQL:
CREATE TABLE "testVarcharToClob" ("varcharColumn" varchar(255));
INSERT INTO "testVarcharToClob" VALUES ('value1');
INSERT INTO "testVarcharToClob" VALUES ('value2');
ALTER TABLE "testVarcharToClob" add "clobColumn" TEXT NULL;
UPDATE "testVarcharToClob" SET "clobColumn" = "varcharColumn";
ALTER TABLE "testVarcharToClob" drop "varcharColumn";
Everything is good up to this point.
In the second connection I submit the query
INSERT INTO "testVarcharToClob" VALUES ('value3');
which causes the monetdb server to crash.
Reproducible: Always
### Steps to Reproduce:
1. Open two connections to the same Monetdb instance
2. Create a table, and use the ALTER TABLE statement as in Details
3. Perform an INSERT on another connection
### Actual Results:
Mserver5 crashes.
## Comment 27537
Date: 2020-02-05 14:07:24 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [a1c1e2b1a7d7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a1c1e2b1a7d7) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a1c1e2b1a7d7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a1c1e2b1a7d7)
Changeset description:
Added test and fix for bug #6816, ie propagate 'colnr' field at reset_column and update_table. Also added missing column 'type' field propagations
## Comment 27542
Date: 2020-02-13 14:10:31 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [efd1634b5dc2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=efd1634b5dc2) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=efd1634b5dc2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=efd1634b5dc2)
Changeset description:
Rename test alter-table-add-column-Bug-6816
to alter-table-add-column.Bug-6816
to comply with naming convention.
| Monetdb Crashes on INSERT statement after ALTER statement in another connection | https://api.github.com/repos/MonetDB/MonetDB/issues/6816/comments | 0 | 2020-11-30T16:53:34Z | 2024-06-27T13:07:57Z | https://github.com/MonetDB/MonetDB/issues/6816 | 753,640,089 | 6,816 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-01-30 13:59:04 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-02-21 12:36:58 +0100
## Comment 27533
Date: 2020-01-30 13:59:04 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Build Identifier:
following 2 sql commands let mserver5 crash.
create table t6815 (type_digits int);
select ifthenelse((type_digits > 0), '('||type_digits||')', '') as opt_len from t6815;
Reproducible: Always
### Steps to Reproduce:
1. start mserver5
2. start mclient
3. run sql commands:
create table t6815 (type_digits int);
select ifthenelse((type_digits > 0), '('||type_digits||')', '') as opt_len from t6815;
### Actual Results:
builtin opt gdk_dbpath = /home/dinther/dev/dev/INSTALL/var/monetdb5/dbfarm/demo
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_ipv6 = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt embedded_py = 3
cmdline opt embedded_c = true
cmdline opt mapi_port = 41000
MonetDB 5 server v11.35.10 (hg id: 5560e86e5fdf)
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
Found 31.243 GiB available main-memory of which we use 25.463 GiB
Copyright (c) 1993 - July 2008 CWI.
Copyright (c) August 2008 - 2020 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
MonetDB/Python3 module loaded
MonetDB/R module loaded
./start_INSTALL_mserver5.sh: line 8: 15990 Segmentation fault (core dumped) /home/dinther/dev/dev/INSTALL/bin/mserver5 -d10 --set embedded_r=true --set embedded_py=3 --set embedded_c=true --set mapi_port=41000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.35.10 (hg id: 5560e86e5fdf), 'demo'
FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/MonetDB
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>create table t6815 (type_digits int);
operation successful
sql>select ifthenelse((type_digits > 0), '('||type_digits||')', '') as opt_len from t6815;
sql>
write error on stream
[home ~]$
### Expected Results:
no crash of mserver5 please
## Comment 27534
Date: 2020-01-30 15:20:59 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [45734606a35c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=45734606a35c) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=45734606a35c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=45734606a35c)
Changeset description:
Compilation fix and added test for bug #6815
## Comment 27535
Date: 2020-01-30 16:00:34 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [a8ed813d5c81](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a8ed813d5c81) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a8ed813d5c81](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a8ed813d5c81)
Changeset description:
Fix for bug #6815, ie call exp_subtype to get the type of an expression instead of differentiating the 'tpe' field, because for e_func and e_aggr, it's not stored in there
| query with ifthenelse() crashes mserver5 | https://api.github.com/repos/MonetDB/MonetDB/issues/6815/comments | 0 | 2020-11-30T16:53:30Z | 2024-06-27T13:07:55Z | https://github.com/MonetDB/MonetDB/issues/6815 | 753,640,036 | 6,815 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-01-29 17:28:54 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-10-19 11:06:19 +0200
## Comment 27531
Date: 2020-01-29 17:28:54 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Build Identifier:
The scalar functions sys.degrees(rad) and sys.radians(deg) are currently implemented as SQL system functions (in sql/scripts/10_math.sql).
CREATE FUNCTION degrees(r double) RETURNS double RETURN r*180/pi();
CREATE FUNCTION radians(d double) RETURNS double RETURN d*pi()/180;
This implies that when using them from any schema other than sys, you must include the sys. prefix, else you get an error.
Error: SELECT: no such unary operator 'degrees(decimal)'
Error: SELECT: no such unary operator 'radians(decimal)'
It would be more user friendly if this sys. prefix in SQL queries would not be needed, as is the case with all the other trigonometric functions.
This can be achieved by implementing the function logic in C (as done for sin(x), cos(x)) and removing the SQL implementation.
Possibly the native C implementations would also be faster and more efficient (less overhead).
Reproducible: Always
### Steps to Reproduce:
select current_schema;
-- sys
set schema profiler;
select current_schema;
-- profiler
select degrees(0.5);
-- SELECT: no such unary operator 'degrees(decimal)'
select degrees(2);
-- SELECT: no such unary operator 'degrees(tinyint)'
select radians(45.0);
-- SELECT: no such unary operator 'radians(decimal)'
select sys.degrees(0.5), sys.degrees(2), sys.radians(45);
### Actual Results:
sql>select current_schema;
+------+
| L2 |
+======+
| sys |
+------+
1 tuple
sql>set schema profiler;
operation successful
sql>select current_schema;
+----------+
| L2 |
+==========+
| profiler |
+----------+
1 tuple
sql>select degrees(0.5);
SELECT: no such unary operator 'degrees(decimal)'
sql>select degrees(2);
SELECT: no such unary operator 'degrees(tinyint)'
sql>select radians(45.0);
SELECT: no such unary operator 'radians(decimal)'
sql>select sys.degrees(0.5), sys.degrees(2), sys.radians(45);
+--------------------------+--------------------------+--------------------------+
| L2 | L4 | L6 |
+==========================+==========================+==========================+
| 28.64788975654116 | 114.59155902616465 | 0.7853981633974483 |
+--------------------------+--------------------------+--------------------------+
1 tuple
### Expected Results:
Allow functions degrees() and radians() to be called without sys. prefix when current schema is not sys.
## Comment 27605
Date: 2020-03-17 20:12:28 +0100
From: Martin van Dinther <<martin.van.dinther>>
See also https://www.monetdb.org/bugzilla/show_bug.cgi?id=3553
## Comment 27780
Date: 2020-06-03 11:09:42 +0200
From: Martin van Dinther <<martin.van.dinther>>
Further optimizations possible:
180/pi() can be replaced with constant: 57.295779513082320876798154814105
pi()/180 can be replaced with constant: 0.01745329251994329576923690768489
## Comment 27871
Date: 2020-06-23 09:27:37 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4c270abe4e2d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4c270abe4e2d) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4c270abe4e2d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4c270abe4e2d)
Changeset description:
Removed 10_math.sql script. Mada functions degree and radians SQL compliant, ie without schema. This fixes bug #6814
| provide native implementations for scalar functions sys.degrees(rad) and sys.radians(deg) | https://api.github.com/repos/MonetDB/MonetDB/issues/6814/comments | 0 | 2020-11-30T16:53:26Z | 2024-06-27T13:07:54Z | https://github.com/MonetDB/MonetDB/issues/6814 | 753,639,987 | 6,814 |
[
"MonetDB",
"MonetDB"
] | Date: 2020-01-29 16:49:03 +0100
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.35.9 (Nov2019-SP1)
CC: @PedroTadim
Last updated: 2020-06-03 16:58:52 +0200
## Comment 27530
Date: 2020-01-29 16:49:03 +0100
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Build Identifier:
select not_uniques(1);
returns: Error: Implementation for function sql.not_uniques not found.
SQLState: HY005
The function is listed in sys.functions as system function twice with signatures:
not_uniques(bigint) returns oid
not_uniques(oid) returns oid
Either add implementation for the function or remove it from sys.functions and sys.args
Reproducible: Always
### Steps to Reproduce:
select not_uniques(1);
select not_uniques(cast (1 as oid));
select * from sys.functions where name = 'not_uniques';
select * from sys.args a where func_id in (select id from sys.functions where name = 'not_uniques');
### Actual Results:
sql>select not_uniques(1);
Implementation for function sql.not_uniques not found
sql>select not_uniques(cast (1 as oid));
Implementation for function sql.not_uniques not found
sql>select * from sys.functions where name = 'not_uniques';
+------+-------------+-------------+------+----------+------+-------------+--------+--------+-----------+--------+
| id | name | func | mod | language | type | side_effect | varres | vararg | schema_id | system |
+======+=============+=============+======+==========+======+=============+========+========+===========+========+
| 64 | not_uniques | not_uniques | sql | 0 | 1 | false | false | false | 2000 | true |
| 65 | not_uniques | not_uniques | sql | 0 | 1 | false | false | false | 2000 | true |
+------+-------------+-------------+------+----------+------+-------------+--------+--------+-----------+--------+
2 tuples
sql>select * from sys.args a where func_id in (select id from sys.functions where name = 'not_uniques');
+------+---------+-------+--------+-------------+------------+-------+--------+
| id | func_id | name | type | type_digits | type_scale | inout | number |
+======+=========+=======+========+=============+============+=======+========+
| 2257 | 64 | res_0 | oid | 63 | 0 | 0 | 0 |
| 2258 | 64 | arg_1 | bigint | 64 | 0 | 1 | 1 |
| 2259 | 65 | res_0 | oid | 63 | 0 | 0 | 0 |
| 2260 | 65 | arg_1 | oid | 63 | 0 | 1 | 1 |
+------+---------+-------+--------+-------------+------------+-------+--------+
4 tuples
### Expected Results:
No 'Implementation for function sql.not_uniques not found' error.
## Comment 27532
Date: 2020-01-30 10:16:21 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [274dd36dafe6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=274dd36dafe6) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=274dd36dafe6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=274dd36dafe6)
Changeset description:
Find backend implementation for SQL basic functions at server startup. Removed 'not_uniques' and 'in' functions as they don't have a backend implementation. This fixes bug #6813
| function not_uniques(bigint) returns error when called | https://api.github.com/repos/MonetDB/MonetDB/issues/6813/comments | 0 | 2020-11-30T16:53:23Z | 2024-06-27T13:07:54Z | https://github.com/MonetDB/MonetDB/issues/6813 | 753,639,943 | 6,813 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.