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

Too many VALUES in INSERT freeze mserver5 #3845

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

Too many VALUES in INSERT freeze mserver5 #3845

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

Comments

@monetdb-team
Copy link

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

Date: 2015-11-02 15:19:11 +0100
From: @hannesmuehleisen
To: SQL devs <>
Version: 11.19.3 (Oct2014)
CC: @mlkersten

Last updated: 2016-01-15 11:37:48 +0100

Comment 21427

Date: 2015-11-02 15:19:11 +0100
From: @hannesmuehleisen

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

The query never finishes

Reproducible: Always

Steps to Reproduce:

  1. Run test case
  2. Observe issue

Actual Results:

Second INSERT never finishes

Expected Results:

Both INSERTs finishes in reasonable time.

Comment 21428

Date: 2015-11-02 15:21:33 +0100
From: MonetDB Mercurial Repository <>

Changeset b56208efd402 made by Hannes Muehleisen hannes@cwi.nl in the MonetDB repo, refers to this bug.

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

Changeset description:

Test for Bug #3845

Comment 21429

Date: 2015-11-02 15:38:15 +0100
From: @hannesmuehleisen

Also saw a crash on Linux

Comment 21490

Date: 2015-11-09 15:30:53 +0100
From: MonetDB Mercurial Repository <>

Changeset 56a7f0f475c4 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=56a7f0f475c4

Changeset description:

Abort reorder optimizer if recursion too deep.
When aborting, we just stop reordering and continue the query.
This fixes bug #3845.

Comment 21491

Date: 2015-11-09 15:34:13 +0100
From: @sjoerdmullender

Even though the bug is now fixed, it is still not recommended to use the INSERT VALUES query to insert many values.

Comment 21493

Date: 2015-11-09 15:43:44 +0100
From: @mlkersten

To add to this comment, each insert lead also to a check of the sortedness property, which (currently) becomes prohibitively more expensive when
you insert in sort order.
Improvement in that direction would require more code in the SQL-append implementation to avoid the linear scan triggered in deriveProps()

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