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

optimizers are not getting set correctly through set optimizer #3036

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

optimizers are not getting set correctly through set optimizer #3036

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

Comments

@monetdb-team
Copy link

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

Date: 2012-02-22 15:54:49 +0100
From: mrunal.gawade
To: SQL devs <>
Version: -- development
CC: @njnes

Last updated: 2012-03-16 14:56:53 +0100

Comment 16968

Date: 2012-02-22 15:54:49 +0100
From: mrunal.gawade

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build Identifier: default branch-21st Feb

I did following steps

  1. Set a user defined optimizer (add mitosis to minimal_pipe)
  2. Check using "select optimizer" to see its set
  3. Re-set a predefined optimizer, like minimal_pipe
  4. Check using "select optimizer" to see its set. However, the UI keeps on showing "user" optimizer instead of minimal_pipe
  5. Disconnect the client and re-connect and try "select optimizer" and I see the minimal_pipe.

Here is the sequence.

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.617ms)

sql>set optimizer='minimal_pipe';
operation successful (0.531ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.539ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.470ms)

sql>set optimizer='minimal_pipe';
operation successful (0.445ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.478ms)

sql>\q

bash-4.2$ mclient -dSF-100
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.8.0 (unreleased), 'mapi:monetdb://cologne.ins.cwi.nl:54321/SF-100'
Type \q to quit, ? for a list of available commands
auto commit mode: on

sql>select optimizer;
+--------------+
| single_value |
+==============+
| minimal_pipe |
+--------------+
1 tuple (0.517ms)

Reproducible: Always

Steps to Reproduce:

I did following steps

  1. Set a user defined optimizer (add mitosis to minimal_pipe)
  2. Check using "select optimizer" to see its set
  3. Re-set a predefined optimizer, like minimal_pipe
  4. Check using "select optimizer" to see its set. However, the UI keeps on showing "user" optimizer instead of minimal_pipe
  5. Disconnect the client and re-connect and try "select optimizer" and I see the minimal_pipe.

Here is the sequence.

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.617ms)

sql>set optimizer='minimal_pipe';
operation successful (0.531ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.539ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.470ms)

sql>set optimizer='minimal_pipe';
operation successful (0.445ms)

sql>select optimizer;
+--------------+
| single_value |
+==============+
| user |
+--------------+
1 tuple (0.478ms)

sql>\q

bash-4.2$ mclient -dSF-100
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.8.0 (unreleased), 'mapi:monetdb://cologne.ins.cwi.nl:54321/SF-100'
Type \q to quit, ? for a list of available commands
auto commit mode: on

sql>select optimizer;
+--------------+
| single_value |
+==============+
| minimal_pipe |
+--------------+
1 tuple (0.517ms)

Expected Results:

corret optimizer should get set

Comment 17098

Date: 2012-03-16 14:56:53 +0100
From: @grobian

Released in Dec2011-SP2

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