Query produces error: HEAPalloc: Insufficient space for HEAP of 1168033427456 bytes. #6134
Last updated: 2019-11-28 10:00:06 +0100
Date: 2016-12-01 13:30:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Query results in: HEAPalloc: Insufficient space for HEAP of 1168033427456 bytes.
Steps to Reproduce:
CREATE TABLE all_dates (d_date date, month_code varchar(7));
COPY INTO category FROM 'category.csv' DELIMITERS '|' , '\n', '"';
GDK reported error.
Query returns results
It seems there is something wrong with "OR" parsing/processing.
Also depending on how many tables/columns are in SQL, sometimes it just takes 100G of hdd space/virtual memory and never returns result.
Date: 2016-12-01 13:31:10 +0100
Created attachment 520
Date: 2016-12-21 16:03:54 +0100
Tested with 11.25.3: still produces same error
Date: 2017-01-10 15:26:59 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d21bef4f8fdd
Date: 2017-01-10 15:36:39 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f0eaa26022fe
Date: 2017-01-10 15:41:49 +0100
From looking at plan, it seems like the joins deteriorate into cross products when adding that single condition.
Date: 2017-01-10 15:55:08 +0100
This also happens in default
Date: 2017-10-06 18:05:10 +0200
Still hapens only latest version.
However we can't control order of tables listed as SQL generated by BI.
Date: 2019-08-19 09:19:27 +0200
We see the same error with SQL select query in version: v11.33.3, v11.31.13 and current development version.
Steps to reproduce:
After doing the above select query, we found
Date: 2019-08-23 12:10:16 +0200
In the main development branch of MonetDB we optimized IN statements as well OR clauses inside WHERE statements to perform a single semi-join instead of multiple theta-select statements. The performance of these queries should improve in the next feature release of MonetDB.
Date: 2019-11-15 13:47:05 +0100
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=3cf4189df085
The text was updated successfully, but these errors were encountered: