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

segmentation fault in mserver5 process #3575

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

segmentation fault in mserver5 process #3575

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

Comments

@monetdb-team
Copy link

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

Date: 2014-09-19 15:26:06 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <>
Version: 11.17.21 (Jan2014-SP3)
CC: @njnes

Last updated: 2014-10-31 14:14:35 +0100

Comment 20166

Date: 2014-09-19 15:26:06 +0200
From: Martin van Dinther <<martin.van.dinther>>

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Build Identifier:

Folllowing SQL command crashes th mserver5 with a segmentation fault:
CREATE SCHEMA AUTHORIZATION monetdb;

Reproducible: Always

Steps to Reproduce:

  1. Start mserver5 (MonetDB 5 server v11.17.21 "Jan2014-SP3")
  2. Start mclient
  3. execute SQL command:
    CREATE SCHEMA AUTHORIZATION monetdb;

Actual Results:

bash-4.2$ start_mserver5
builtin opt gdk_dbpath = /ufs/dinther/MonetDB201408/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt mapi_port = 49000
MonetDB 5 server v11.17.21 "Jan2014-SP3"
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.356 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:49000/
MonetDB/GIS module loaded
MonetDB/JAQL module loaded
MonetDB/SQL module loaded

5279 Segmentation fault ./MonetDB201408/bin/mserver5 -d10 --set mapi_port=49000
bash-4.2$

bash-4.2$ mclient -p 49000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.17.21 (Jan2014-SP3), 'demo'
Type \q to quit, ? for a list of available commands
auto commit mode: on
sql>CREATE SCHEMA AUTHORIZATION monetdb;
sql>
bash-4.2$

Expected Results:

No segmentation fault or mserver crash.

According to https://www.monetdb.org/Documentation/SQLreference/Schema
the CREATE SCHEMA command is defined as:

schema:
CREATE SCHEMA schema_name_clause
[ DEFAULT CHARACTER SET ident ]
[ PATH schema_name ','... ]
[ schema_element ... ]

schema_name_clause: ident | [ ident ] AUTHORIZATION

This implies it should be possible to do:
CREATE SCHEMA AUTHORIZATION;
as in schema_name_clause the [ ident ] is optional.

I think that is incorrect. Every schema should have a name and when AUTHORIZATION is specified also an authorisation name should be supplied.
See example on https://www.monetdb.org/Documentation/UserGuide/Tutorial:
CREATE SCHEMA "voc" AUTHORIZATION "voc";

So syntax should probably be:
schema:
CREATE SCHEMA schema_name
[ AUTHORIZATION ident ]
[ DEFAULT CHARACTER SET ident ]
[ PATH schema_name ','... ]
[ schema_element ... ]

Comment 20177

Date: 2014-09-21 16:44:25 +0200
From: @njnes

we now handle the fallback to user_name in case the schema name isn't specified.

Comment 20180

Date: 2014-09-21 17:28:30 +0200
From: MonetDB Mercurial Repository <>

Changeset 3c7675b36829 made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

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

Changeset description:

fixes for bug #3579 and bug #3575

Comment 20380

Date: 2014-10-31 14:14:35 +0100
From: @sjoerdmullender

Oct2014 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