Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query on large string table fails on HEAPextend #3789

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Query on large string table fails on HEAPextend #3789

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2015-08-13 14:54:30 +0200
From: @hannesmuehleisen
To: GDK devs <>
Version: 11.21.1 (Jul2015)

Last updated: 2015-11-03 10:18:19 +0100

Comment 21139

Date: 2015-08-13 14:54:30 +0200
From: @hannesmuehleisen

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:

Reproducible: Always

Steps to Reproduce:

  1. Run mserver5 with gdk_nr_threads to largish number, e.g. 96 (like the default on diamonds1)
  2. CREATE TABLE s(s STRING);
  3. Insert significant amount of unique strings, e.g. 10M strings with 10 random characters, in our example this leads to a string heap of ~24 GB.
  4. SELECT * FROM s;

Actual Results:

Query fails,
HEAPextend: failed to extend to 2303616614400 for 03/324.theap: h->storage == STORE_MEM && can_map && fd >= 0 && HEAPload_intern() != GDK_SUCCEED

Expected Results:

Query should run, even though its result is admittedly very large.

From debugging, we found that MATpackIncrement() calls HEAPextend()

Comment 21141

Date: 2015-08-13 16:18:11 +0200
From: MonetDB Mercurial Repository <>

Changeset 32935e5e09fb made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=32935e5e09fb

Changeset description:

Don't extend string heaps since they may get replaced due to sharing.
This fixes bug #3789.

Comment 21303

Date: 2015-09-29 14:28:23 +0200
From: @sjoerdmullender

I'm assuming this was indeed fixed.

Comment 21439

Date: 2015-11-03 10:18:19 +0100
From: @sjoerdmullender

Jul2015 SP1 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant