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

Monetdb Crashes on INSERT statement after ALTER statement in another connection #6816

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
bug Something isn't working major SQL

Comments

@monetdb-team
Copy link

Date: 2020-02-05 12:55:01 +0100
From: Manuel <>
To: SQL devs <>
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 <>

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 <>

Changeset 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

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 <>

Changeset 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

Changeset description:

Rename test  alter-table-add-column-Bug-6816
         to  alter-table-add-column.Bug-6816
to comply with naming convention.
@monetdb-team monetdb-team added bug Something isn't working major SQL labels Nov 30, 2020
@sjoerdmullender sjoerdmullender added this to the Ancient Release milestone Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major SQL
Projects
None yet
Development

No branches or pull requests

2 participants