- users-list - monetdb.org

Re: MonetDB header Datatype Question
by Stefan Manegold 04 Jan '18

04 Jan '18

What's the (SQL-)type of your column COLUMN_NAME?Which version of MonetDB are you using?Which version of the MonetDB ODBC driver are you using?Which compiler did you use to compile MonetDB on which OS?What did configure say about what the largest supported integer type is? -------- Original message --------From: "Sharma, Sreejith" <Sreejith.Sharma(a)harman.com> Date: 12/31/17 18:33 (GMT+01:00) To: users-list(a)monetdb.org Subject: RE: MonetDB header Datatype Question All, Here is the specifics of error – typeODBC: SQL_UNKNOWN_TYPE mDataType: HG_NULL_VALUE(hgColumnType) precision: 0 scale: 0 nullable: true Column name: L6. Regards, Sreejith From: Sharma, Sreejith Sent: Sunday, December 31, 2017 11:21 AM To: users-list(a)monetdb.org Subject: MonetDB header Datatype Question All, I would like to know what is the MonetDB header datatype if no alias or column name provided? In my BI application, am getting an error while using SELECT SUM(DISTINCT COLUMN_NAME) FROM TABLE_NAME. I see it works in 11.27.9 build when installed in CentOS. However, when i download the source tarball and recompile the code, this fox seems to be lost. Is there anywhere this can be identified? Or fixed? Regards, Sreejith

3 5

Re: MonetDB header Datatype Question
by Stefan Manegold 04 Jan '18

04 Jan '18

Looks fine to me, but of course you're free to try a different compiler of your choice. Stefan -------- Original message --------From: "Sharma, Sreejith" <Sreejith.Sharma(a)harman.com> Date: 1/4/18 10:31 (GMT+01:00) To: Communication channel for MonetDB users <users-list(a)monetdb.org> Subject: RE: MonetDB header Datatype Question Thanks Stefan. However am suspecting if it's to do with the compiler. Did you got a chance to look at the details I sent across for the questions. configure:5039: gcc --version >&5 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16) Regards, Sreejith -----Original Message----- From: users-list [mailto:users-list-bounces+sreejith.sharma=harman.com@monetdb.org] On Behalf Of Stefan Manegold Sent: Wednesday, January 03, 2018 2:11 PM To: Communication channel for MonetDB users <users-list(a)monetdb.org> Subject: [EXTERNAL] Re: MonetDB header Datatype Question I was mislead by the "HG" prefix in the error message. I now realize that the error message does not seem to be a MonetDB error message. Hence, I'm afraid we cannot help much. You said is works/worked with a binary installation of Jul2017-SP2 (11.27.9), but does not with a self-compiled installation of the very same release. You'd need to double-check you compilation and installation of the self-compiled release. You can also try with the latest Jul2017-SP3 (11.27.11) release --- binary and/or self-compiled --- but as said, since the error message is not from MonetDB, you'd need to search for the problem (also) in the client software / application you're using. Best, Stefan ----- On Jan 1, 2018, at 5:55 PM, Sharma, Sreejith Sreejith.Sharma(a)harman.com wrote: > Hi Stefan, > > > > Here are the details you had asked for. Any help here soon is appreciated. > > > > What's the (SQL-)type of your column COLUMN_NAME? – > > INTEGER > > > > Which version of MonetDB are you using? – > > MonetDB 5 server v11.27.9 "Jul2017-SP2" (64-bit, 128-bit integers) > > > > Which version of the MonetDB ODBC driver are you using? > > ODBC Driver - /usr/lib64/libMonetODBC.so (11.27.9 and tried 11.27.5 > updated) > > > > Which compiler did you use to compile MonetDB on which OS? > > configure:5030: checking for C compiler version > > configure:5039: gcc --version >&5 > > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16) > > > > #define PACKAGE_NAME "MonetDB" > >| #define PACKAGE_TARNAME "MonetDB" > >| #define PACKAGE_VERSION "11.27.9" > >| #define PACKAGE_STRING "MonetDB 11.27.9" > >| #define PACKAGE_BUGREPORT "https://clicktime.symantec.com/a/1/js6skxjfSiwdIJPQwPy1ginHSudH8-MwrUFzw00H…" > >| #define PACKAGE_URL "https://clicktime.symantec.com/a/1/ZNQS7LXKm8wqT3QEExvIAnZ3Vk2CRq8bspHohtAV…" > >| #define PACKAGE "MonetDB" > >| #define VERSION "11.27.9" > >| #define HOST "x86_64-pc-linux-gnu" > >| #define MONETDB_RELEASE "Jul2017-SP2" > > > > What did configure say about what the largest supported integer type is? > > hge_bits='128' > > largest integer type: ${hge_bits} bits" > > > > > > Regards, > > Sreejith > > > > > From: users-list > [mailto:users-list-bounces+sreejith.sharma=harman.com@monetdb.org] On > Behalf Of Stefan Manegold > Sent: Monday, January 01, 2018 7:05 AM > To: Communication channel for MonetDB users <users-list(a)monetdb.org> > Subject: [EXTERNAL] Re: MonetDB header Datatype Question > > > > > > > > > What's the (SQL-)type of your column COLUMN_NAME? > > > Which version of MonetDB are you using? > > > Which version of the MonetDB ODBC driver are you using? > > > Which compiler did you use to compile MonetDB on which OS? > > > What did configure say about what the largest supported integer type is? > > > > > > > > > -------- Original message -------- > > > From: "Sharma, Sreejith" < Sreejith.Sharma(a)harman.com > > > > Date: 12/31/17 18:33 (GMT+01:00) > > > To: users-list(a)monetdb.org > > > Subject: RE: MonetDB header Datatype Question > > > > > > All, > > > > Here is the specifics of error – > > > > typeODBC: SQL_UNKNOWN_TYPE mDataType: HG_NULL_VALUE(hgColumnType) > precision: 0 > scale: 0 nullable: true Column name: L6. > > > > Regards, > > Sreejith > > > > > From: Sharma, Sreejith > Sent: Sunday, December 31, 2017 11:21 AM > To: users-list(a)monetdb.org > Subject: MonetDB header Datatype Question > > > > > All, > > > > > > I would like to know what is the MonetDB header datatype if no alias > or column name provided? In my BI application, am getting an error > while using SELECT SUM(DISTINCT COLUMN_NAME) FROM TABLE_NAME. I see it > works in 11.27.9 build when installed in CentOS. However, when i > download the source tarball and recompile the code, this fox seems to be lost. Is there anywhere this can be identified? > Or fixed? > > > Regards, > > > Sreejith > > _______________________________________________ > users-list mailing list > users-list(a)monetdb.org > https://clicktime.symantec.com/a/1/EiR5ebgK8iUa4CLKJS5IhZJEZAKRFGZRDFU > FUCIYntY=?d=l99sUyvGli3efslX3N2ZiOXRT2oUDQGPF4w16I0hM9zUMoOkJQMri6AAcO > e4XlOqB4NFs5YhzH2NIIET0LyAMDvzRQkCYnLv2cWSJsLXuGRkmOTx5BxDA1nwzncmE0Ex > YksGCv1OTBY5h8YekFgUFxCvagkJjjUM6qSdc8J_3jJdMcNfFBT-6B5sCtZZWTBqGFRvVr > mq4XFYO_7DYsI9LdIJf7p8tqhBL-xSVWB3pCxqFx46Iyjz8nidH-BXBjg-pRI2Gk56GQ4p > kiPFSFlud_PVfn48XxozGVFit5p6x7F-AVEgKrooyJUyAchXTTYPKW5qN60JUu-5toDlGZ > U0tcE6B8a_-BAZmcVxJiZTehQx5mL1hAm0sBK2BdVeLD5BkXQ_JG8gnBigTg0N4E9I6b5C > geHSGmxUBIKMr_4WO21MsBtAqElF9oRpXg%3D%3D&u=https%3A%2F%2Fwww.monetdb.o > rg%2Fmailman%2Flistinfo%2Fusers-list -- | Stefan.Manegold(a)CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | _______________________________________________ users-list mailing list users-list(a)monetdb.org https://clicktime.symantec.com/a/1/EiR5ebgK8iUa4CLKJS5IhZJEZAKRFGZRDFUFUCIY… _______________________________________________ users-list mailing list users-list(a)monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

1 0

MonetDB header Datatype Question
by Sharma, Sreejith 31 Dec '17

31 Dec '17

All, I would like to know what is the MonetDB header datatype if no alias or column name provided? In my BI application, am getting an error while using SELECT SUM(DISTINCT COLUMN_NAME) FROM TABLE_NAME. I see it works in 11.27.9 build when installed in CentOS. However, when i download the source tarball and recompile the code, this fox seems to be lost. Is there anywhere this can be identified? Or fixed? Regards, Sreejith

1 1

Monetdb date column issue
by Amit Ambekar 27 Dec '17

27 Dec '17

Hi, i am using MonetDB v11.23.7 (Jun2016-SP1) version. in that when is reboot my ubuntu machine, my date columns in all tables becoming null . is there any issue related to version? Warm Regards, *Amit Suryakant Ambekar*** */Technology Associate/* Office: Ist floor, Poddar Chambers, Mathruradas Mill Compound, Lower Parel, Mumbai 400013 | Landline: +91 22 43470408 Cell: +91 7741823310 | Email: amit(a)g-square.in | Website:www.g-square.in

1 0

SELECT: too many nested operators
by Sharma, Sreejith 19 Dec '17

19 Dec '17

All, I have a valid scenario where our application generates a SQL which is around 4.4MB and contains 75K of combination of AND and OR operators. This SQL fails with "SELECT: too many nested operators" error while executing this SQL. While I went through the code, I noticed any thread size above THREAD_STACK_SIZE - 16 * 1024 is getting aborted. Is there any possibility that we can change this? Any reason why it's set to 16MB? As server our server has enough memory and storage and we need to understand if this can be handled in code or via parameter as this is valid scenario. Also, we can't split the SQL too. Regards, Sreejith

4 4

too many nested operators - Query size 4MB
by Sharma, Sreejith 16 Dec '17

16 Dec '17

All, Have a quick question- I have been trying to perform a test on bigger SQL and I see SQL's are failing which are above 4 MB with error "too many nested operators". There are many AND and OR operators. Not sure if there is any limitations. Regards, Sreejith

1 0

Announcement: New Jul2017-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 14 Dec '17

14 Dec '17

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2017-SP3 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Jul 2017-SP3 bugfix release (11.27.11) MonetDB Common * Reimplemented summing of a column of floating point (flt and dbl) values. The old code could give wildly inaccurate results when adding up lots and lots of values due to lack of precision. Try SELECT sum(c) FROM t; where t is 100,000,000 rows, c is of type REAL and all values are equal to 1.1. (The old code returned 33554432 instead of 1.1e8.) Bug Fixes * 3898: Deadlock on insertion * 6429: ROUND produces wrong data type * 6436: Query sequence with 2x ifthenelse() and next nullif() causes mserver5 Segmentation fault * 6437: System schemas "profiler" and "json" shouldn't be allowed to be dropped. * 6439: Invalid references to sys.columns.id from sys.statistics.column_id * 6442: SEGFAULT with COPY INTO BEST EFFORT and skipping input columns * 6443: complex(?) query forgets(?) column name * 6444: Using 'with' keyword with table returning function crashes monetdb * 6445: Sqlitelogictest crash in MySQL query * 6446: sql_parser.y bug? * 6448: 'insert into' with multiple rows containing subqueries crashes * 6449: Assertion error in rel_dce_refs (sqlsmith) * 6450: Assertion error in exp_bin (sqlsmith) * 6451: Assertion error in sql_ref_dec (sqlsmith) * 6453: Assertion error in rel_rename_exps (sqlsmith) * 6454: SQL lexical error * 6455: Assertion error in rel_apply_rewrite (sqlsmith) * 6456: NULL becomes 0 in outer join * 6459: Assertion error in exp_bin (sqlsmith) * 6462: large virtual memory spike on BLOB column select * 6465: appending to variables sized atom bats other than str bats with force flag may result in corrupted heap * 6467: date_to_str formatter is wrong * 6470: mitosis gets in the way of simple select * 6471: calls to sys.generate_series should auto-convert arguments * 6472: Assertion failure in rel_rename (Sqlsmith) * 6477: assertion eror rel_push_project_up (sqlsmith) * 6478: Crash with nested order by/ limit offset * 6479: Mserver receives an assertion error on a procedure call * 6480: Segfault in mvc_find_subexp (sqlsmith)

1 0

Excessive slowness in query
by Alfio Bettini 14 Dec '17

14 Dec '17

Hi all, we're testing MonetDB performances in order to understand if it could be possible to use it as data mart in our BI software. We're considering a set of queries executed in our test environment (CentOS 7, 32 GB RAM, 4 cpu). All the executed queries have quite good performances (between 10 and 45 seconds) except the following one that is taking several minutes in order to be executed: SELECT id, count(distinct value) FROM table GROUP BY id; The table contains 100 millions of data. It has about 130 columns (varchar, int, bigint, smallint, tinyint, timestamp, datetime). We have no BLOB/CLOB/Text types. Can you suggest us any optimizations in order to have this query run faster? Do you know some possible reasons why it's so slow? Kind Regards, Alfio Bettini The information contained in this message, together with any attachments, may be privileged and confidential and is intended for the use of the addressee(s) only. Any review, copying, use or distribution of this email by others (including any of its attachments) is strictly prohibited. If you are not the intended recipient, please destroy this email and its attachments and contact the sender immediately. This email was sent by EidosMedia SpA<http://www.eidosmedia.com>

1 0

Excessive slowness in a query
by Alfio Bettini 14 Dec '17

14 Dec '17

Hi all, we're testing MonetDB performances in order to understand if it could be possible to use it as data mart in our BI software. We're considering a set of queries executed in our test environment (CentOS 7, 32 GB RAM, 4 cpu). All the executed queries have quite good performances (between 10 and 45 seconds) except the following one that is taking several minutes in order to be executed: SELECT id, count(distinct value) FROM table GROUP BY id; The table contains 100 millions of data. It has about 130 columns (varchar, int, bigint, smallint, tinyint, timestamp, datetime). We have no BLOB/CLOB/Text types. The fields used in the query have these data types: id: int value: bigint Can you suggest us any optimizations in order to have this query run faster? Do you know some possible reasons why it's so slow? Kind Regards, Alfio Bettini The information contained in this message, together with any attachments, may be privileged and confidential and is intended for the use of the addressee(s) only. Any review, copying, use or distribution of this email by others (including any of its attachments) is strictly prohibited. If you are not the intended recipient, please destroy this email and its attachments and contact the sender immediately. This email was sent by EidosMedia SpA<http://www.eidosmedia.com>

1 0

Re: algebra.join heapextend crash
by Stefan Manegold 13 Dec '17

13 Dec '17

Allocating "only" about 2.8 GB does not ring alarms that the plan night be degenerated - assuming your data is not tiny. Could you share:OS, full query, data sizes, free disk space at time of failure, mserver5 process size at time of failure? Thanks,Stefan -------- Original message --------From: Anthony Damico <ajdamico(a)gmail.com> Date: 11/22/17 12:13 (GMT+01:00) To: Communication channel for MonetDB users <users-list(a)monetdb.org> Subject: algebra.join heapextend crash hi, i'm using monetdblite-r 0.5.0 on a confidential dataset. my syntax worked on monetdblite 0.3.1 on the same machine ftruncate: Invalid argument Error in .local(conn, statement, ...) : Unable to execute statement 'CREATE TABLE ccaed123_b_svcmon_xwalk AS ( SELECT a.enrolid , a.yr , a.dataty...'. Server says 'MALException:algebra.join:GDK reported error. !ERROR: GDKextendf: c !ERROR: HEAPextend: failed to extend to 2890530816 for 02\57\25766.tail: GDKmre map() failed '. it's a local drive, the hard disk isn't close to full and the machine has 700gb of ram, but the table it's trying to create might be bigger than that. dunno if related to https://www.monetdb.org/bugzilla/show_bug.cgi?id=3791 thanks

2 4