[MonetDB-users] Compiling with optimizer
Hi, I have been compiling MonetDB successfuly under Windows so far. Now I have tried compiling as I have done before, but with "optimize=yes". Now when I start the server, I get this message: !FATAL: BBPinit: BBP.dir is empty What does this mean? Am I doing something wrong? Thanks. -- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23022199.html Sent from the monetdb-users mailing list archive at Nabble.com.
Alex Bo. wrote:
Hi,
I have been compiling MonetDB successfuly under Windows so far. Now I have tried compiling as I have done before, but with "optimize=yes".
Now when I start the server, I get this message:
!FATAL: BBPinit: BBP.dir is empty start mserver with debugging on then you will see where it attempts to find the database directory. It has encountered an empty file BBP.dir, which is indicative something went wrong in a previous session. I suggest to remove the dbfarm and try again. Otherwise, report on the output of mserver -d 10
What does this mean? Am I doing something wrong?
Thanks.
Hi, Removing the dbfarm didn't help. When I run mserver it crashes without any error message. Only when trying to run it for the second time gives me the BBPinit error. Here's the output of mserver -d 10: # builtin opt gdk_arch = 32biti686-pc-win32 # builtin opt gdk_version = 1.29.0 # builtin opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # builtin opt exec_prefix = ${prefix} # builtin opt gdk_dbname = tst # builtin opt gdk_dbfarm = ${prefix}\var\MonetDB # builtin opt gdk_debug = 8 # builtin opt gdk_alloc_map = yes # builtin opt gdk_vmtrim = yes # builtin opt Monet_admin = adm # builtin opt Monet_prompt = > # builtin opt Monet_welcome = yes # builtin opt Monet_mod_path = ${exec_prefix}\lib\MonetDB # builtin opt Monet_daemon = yes # builtin opt host = localhost # builtin opt mapi_port = 50000 # builtin opt mapi_noheaders = no # builtin opt mapi_debug = 0 # builtin opt mapi_clients = 2 # builtin opt sql_debug = 0 # builtin opt sql_logdir = sql_logs # builtin opt xquery_logdir = xquery_logs # builtin opt standoff_ns = http://Monetdb.cwi.nl/standoff # builtin opt standoff_start = start # builtin opt standoff_end = end # config opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # config opt config = %prefix%\etc\Monetdb5.conf # config opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # config opt exec_prefix = %prefix% # config opt gdk_dbfarm = %prefix%\var\MonetDB5\dbfarm # config opt gdk_dbname = demo # config opt gdk_alloc_map = no # config opt gdk_embedded = no # config opt gdk_debug = 0 # config opt Monet_mod_path = %exec_prefix%\lib\MonetDB5;%exec_prefix%\lib\MonetDB5\lib;%exec_prefix%\lib\MonetDB5\bin # config opt Monet_daemon = no # config opt Monet_welcome = yes # config opt mero_msglog = %prefix%\var\log\MonetDB\merovingian.log # config opt mero_errlog = %prefix%\var\log\MonetDB\merovingian.log # config opt mero_timeinterval = 600 # config opt mero_pidfile = %prefix%\var\run\MonetDB\merovingian.pid # config opt mero_exittimeout = 7 # config opt mero_doproxy = yes # config opt mero_discoveryttl = 600 # config opt mal_init = %exec_prefix%\lib\MonetDB5/mal_init.mal # config opt mal_listing = 2 # config opt mapi_port = 50000 # config opt mapi_open = false # config opt sql_logdir = sql_logs # cmdline opt prefix = C:\MonetBuilds\09.04.13\Monet32_opt # cmdline opt exec_prefix = C:\MonetBuilds\09.04.13\Monet32_opt # cmdline opt gdk_dbfarm = \dbfarm Thanks. Martin Kersten wrote:
Alex Bo. wrote:
Hi,
I have been compiling MonetDB successfuly under Windows so far. Now I have tried compiling as I have done before, but with "optimize=yes".
Now when I start the server, I get this message:
!FATAL: BBPinit: BBP.dir is empty start mserver with debugging on then you will see where it attempts to find the database directory. It has encountered an empty file BBP.dir, which is indicative something went wrong in a previous session. I suggest to remove the dbfarm and try again. Otherwise, report on the output of mserver -d 10
What does this mean? Am I doing something wrong?
Thanks.
------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23152268.html Sent from the monetdb-users mailing list archive at Nabble.com.
Alex, which version of Windows are you using? Which version of MonetDB are you using? Which compiler are you using? How exactly did you compile MonetDB withou and which optimization, i.e., how exactly do your respective complete commands look like? How exactly do you start MonetDB? (both the non-optimized version that works and the optimized version that does not work) Your output suggests that you called Mserver.exe (or mserver5.exe ??) (directly or via a .bat script) with "--dbfarm=\dbfarm" (see below). Does that directory exist? Are you allowed to write in \ ? "mserver -d 10" indicates that you are using MonetDB version 4, but the (incomplete) output you sent looks more like MonetDB version 5? Does "mserver" mean you're calling Mserver.bat or Mserver.exe (i.e. which is first in your PATH?)? Could you please also send the remainder of the output, i.e., MonetDB's welcome message? Stefan On Tue, Apr 21, 2009 at 02:29:00AM -0700, Alex Bo. wrote:
Hi,
Removing the dbfarm didn't help. When I run mserver it crashes without any error message. Only when trying to run it for the second time gives me the BBPinit error.
Here's the output of mserver -d 10:
# builtin opt gdk_arch = 32biti686-pc-win32 # builtin opt gdk_version = 1.29.0 # builtin opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # builtin opt exec_prefix = ${prefix} # builtin opt gdk_dbname = tst # builtin opt gdk_dbfarm = ${prefix}\var\MonetDB # builtin opt gdk_debug = 8 # builtin opt gdk_alloc_map = yes # builtin opt gdk_vmtrim = yes # builtin opt Monet_admin = adm # builtin opt Monet_prompt = > # builtin opt Monet_welcome = yes # builtin opt Monet_mod_path = ${exec_prefix}\lib\MonetDB # builtin opt Monet_daemon = yes # builtin opt host = localhost # builtin opt mapi_port = 50000 # builtin opt mapi_noheaders = no # builtin opt mapi_debug = 0 # builtin opt mapi_clients = 2 # builtin opt sql_debug = 0 # builtin opt sql_logdir = sql_logs # builtin opt xquery_logdir = xquery_logs # builtin opt standoff_ns = http://Monetdb.cwi.nl/standoff # builtin opt standoff_start = start # builtin opt standoff_end = end # config opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # config opt config = %prefix%\etc\Monetdb5.conf # config opt prefix = C:\MonetCVS_base_09.04.13\MonetCVS32_09.04.13_opt\Install # config opt exec_prefix = %prefix% # config opt gdk_dbfarm = %prefix%\var\MonetDB5\dbfarm # config opt gdk_dbname = demo # config opt gdk_alloc_map = no # config opt gdk_embedded = no # config opt gdk_debug = 0 # config opt Monet_mod_path = %exec_prefix%\lib\MonetDB5;%exec_prefix%\lib\MonetDB5\lib;%exec_prefix%\lib\MonetDB5\bin # config opt Monet_daemon = no # config opt Monet_welcome = yes # config opt mero_msglog = %prefix%\var\log\MonetDB\merovingian.log # config opt mero_errlog = %prefix%\var\log\MonetDB\merovingian.log # config opt mero_timeinterval = 600 # config opt mero_pidfile = %prefix%\var\run\MonetDB\merovingian.pid # config opt mero_exittimeout = 7 # config opt mero_doproxy = yes # config opt mero_discoveryttl = 600 # config opt mal_init = %exec_prefix%\lib\MonetDB5/mal_init.mal # config opt mal_listing = 2 # config opt mapi_port = 50000 # config opt mapi_open = false # config opt sql_logdir = sql_logs # cmdline opt prefix = C:\MonetBuilds\09.04.13\Monet32_opt # cmdline opt exec_prefix = C:\MonetBuilds\09.04.13\Monet32_opt # cmdline opt gdk_dbfarm = \dbfarm
^^^^^^^^^^^ ^^^^^^^^^^ ^^^^^^^
Thanks.
Martin Kersten wrote:
Alex Bo. wrote:
Hi,
I have been compiling MonetDB successfuly under Windows so far. Now I have tried compiling as I have done before, but with "optimize=yes".
Now when I start the server, I get this message:
!FATAL: BBPinit: BBP.dir is empty start mserver with debugging on then you will see where it attempts to find the database directory. It has encountered an empty file BBP.dir, which is indicative something went wrong in a previous session. I suggest to remove the dbfarm and try again. Otherwise, report on the output of mserver -d 10
What does this mean? Am I doing something wrong?
Thanks.
------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23152268.html Sent from the monetdb-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
I'm building the latest Monet files from CVS (Monet5, not Monet4) on Windows Server 2003. After reading in the documentation that optimization is disabled by default, I added optimize=yes to my nmake commands. I start MonetDB with MSQLserver.bat from the Install directory. Whatever I'm doing is working when I leave out optimize=yes from the build procedure. To add the output I have been asked for I added "-d 10" to Mserver.bat after "%MONETDB%\bin\mserver.exe" ... When running MSQLserver.bat like this, I don't get any welcome message at all. I immediately get the output I put here before. Thanks. -- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23155829.html Sent from the monetdb-users mailing list archive at Nabble.com.
On Tue, Apr 21, 2009 at 06:13:46AM -0700, Alex Bo. wrote:
I'm building the latest Monet files from CVS (Monet5, not Monet4) on Windows
I'd advise you to use the latest release from CVS, i.e., the Feb2009 branch.
Server 2003.
After reading in the documentation that optimization is disabled by default,
Where exactly does the documentation say so? Unless you call nmake with DEBUG=1, we use -Ox, i.e., optimization is enabled by default... Just check your nmake logs/output (without optimize=yes) to see which options are given to the compiler. (and potentially compare with that of optimize=yes to see whether there are any differences)
I added optimize=yes to my nmake commands.
Nm, does nmake recognize/handle that option? I'm not aware that our Makefile do ...
I start MonetDB with MSQLserver.bat from the Install directory. Whatever I'm doing is working when I leave out optimize=yes from the build procedure.
If I look at the original sql/NT/MSQLserver.bat and MonetDB5/NT/M5server.bat, I cannot see how they can result in mserver5.exe being called with --dbfarm=\dbfarm, as your -d10 output suggests ...
To add the output I have been asked for I added "-d 10" to Mserver.bat after "%MONETDB%\bin\mserver.exe" ...
Mserver.bat is MonetDB4, not MonetDB5 . M5server.bat is MonetDB5. MonetDB/SQL requires (and works with) MonetDB5, only, not (with) MonetDB4. (MonetDB/XQuery requires (and works with) MonetDB4, only, not (with) MonetDB5.)
When running MSQLserver.bat like this, I don't get any welcome message at all. I immediately get the output I put here before.
Your -d10 output says # config opt Monet_welcome = yes hence, I'd expect a welcome message ... Stefan
Thanks.
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23155829.html Sent from the monetdb-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
I saw this in the release documentation for June 2008: Compilation from sources For convenience of both developers and users as well as to comply even more with open source standards, we now set/use the following defaults for the configure options --enable-strict, --enable-assert, --enable-debug, --enable-optimize When compiling from CVS sources (as mainly done by developers): strict=yes assert=yes debug=yes optimize=no (*) ... (*) IMPORTANT NOTE: Since --enable-optimize=yes is no longer the default for any case except binary packages, it is strongly recommended to (re)compile everything from scratch, explicitly configured with --enable-debug=no --enable-assert=no --enable-optimize=yes This is why I assumed that I am compiling from CVS with the optimizer being disabled. So could you please clear that up for me? Is the optimizer enabled by default or not when building from CVS? Also, how can I tell if the optimizer is running or not when MonetDB is up and running? Thanks. Stefan Manegold wrote:
On Tue, Apr 21, 2009 at 06:13:46AM -0700, Alex Bo. wrote:
I'm building the latest Monet files from CVS (Monet5, not Monet4) on Windows
I'd advise you to use the latest release from CVS, i.e., the Feb2009 branch.
Server 2003.
After reading in the documentation that optimization is disabled by default,
Where exactly does the documentation say so?
Unless you call nmake with DEBUG=1, we use -Ox, i.e., optimization is enabled by default...
Just check your nmake logs/output (without optimize=yes) to see which options are given to the compiler. (and potentially compare with that of optimize=yes to see whether there are any differences)
I added optimize=yes to my nmake commands.
Nm, does nmake recognize/handle that option? I'm not aware that our Makefile do ...
I start MonetDB with MSQLserver.bat from the Install directory. Whatever I'm doing is working when I leave out optimize=yes from the build procedure.
If I look at the original sql/NT/MSQLserver.bat and MonetDB5/NT/M5server.bat, I cannot see how they can result in mserver5.exe being called with --dbfarm=\dbfarm, as your -d10 output suggests ...
To add the output I have been asked for I added "-d 10" to Mserver.bat after "%MONETDB%\bin\mserver.exe" ...
Mserver.bat is MonetDB4, not MonetDB5 . M5server.bat is MonetDB5.
MonetDB/SQL requires (and works with) MonetDB5, only, not (with) MonetDB4.
(MonetDB/XQuery requires (and works with) MonetDB4, only, not (with) MonetDB5.)
When running MSQLserver.bat like this, I don't get any welcome message at all. I immediately get the output I put here before.
Your -d10 output says # config opt Monet_welcome = yes hence, I'd expect a welcome message ...
Stefan
Thanks.
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23155829.html Sent from the monetdb-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23311296.html Sent from the monetdb-users mailing list archive at Nabble.com.
Alex Bo. wrote:
I saw this in the release documentation for June 2008:
Compilation from sources
For convenience of both developers and users as well as to comply even more with open source standards, we now set/use the following defaults for the configure options
--enable-strict, --enable-assert, --enable-debug, --enable-optimize When compiling from CVS sources (as mainly done by developers): strict=yes assert=yes debug=yes optimize=no (*)
...
(*) IMPORTANT NOTE: Since --enable-optimize=yes is no longer the default for any case except binary packages, it is strongly recommended to (re)compile everything from scratch, explicitly configured with --enable-debug=no --enable-assert=no --enable-optimize=yes
Optimization here is to advice the C-compiler to optimize code. The MonetDB optimizer default pipeline can be seen with select optimizer; For further information see: http://monetdb.cwi.nl/SQL/Documentation/Optimizer-Control.html
This is why I assumed that I am compiling from CVS with the optimizer being disabled. So could you please clear that up for me? Is the optimizer enabled by default or not when building from CVS? Also, how can I tell if the optimizer is running or not when MonetDB is up and running?
Thanks.
Stefan Manegold wrote:
On Tue, Apr 21, 2009 at 06:13:46AM -0700, Alex Bo. wrote:
I'm building the latest Monet files from CVS (Monet5, not Monet4) on Windows I'd advise you to use the latest release from CVS, i.e., the Feb2009 branch.
Server 2003.
After reading in the documentation that optimization is disabled by default, Where exactly does the documentation say so?
Unless you call nmake with DEBUG=1, we use -Ox, i.e., optimization is enabled by default...
Just check your nmake logs/output (without optimize=yes) to see which options are given to the compiler. (and potentially compare with that of optimize=yes to see whether there are any differences)
I added optimize=yes to my nmake commands. Nm, does nmake recognize/handle that option? I'm not aware that our Makefile do ...
I start MonetDB with MSQLserver.bat from the Install directory. Whatever I'm doing is working when I leave out optimize=yes from the build procedure. If I look at the original sql/NT/MSQLserver.bat and MonetDB5/NT/M5server.bat, I cannot see how they can result in mserver5.exe being called with --dbfarm=\dbfarm, as your -d10 output suggests ...
To add the output I have been asked for I added "-d 10" to Mserver.bat after "%MONETDB%\bin\mserver.exe" ... Mserver.bat is MonetDB4, not MonetDB5 . M5server.bat is MonetDB5.
MonetDB/SQL requires (and works with) MonetDB5, only, not (with) MonetDB4.
(MonetDB/XQuery requires (and works with) MonetDB4, only, not (with) MonetDB5.)
When running MSQLserver.bat like this, I don't get any welcome message at all. I immediately get the output I put here before. Your -d10 output says # config opt Monet_welcome = yes hence, I'd expect a welcome message ...
Stefan
Thanks.
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23155829.html Sent from the monetdb-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On Thu, Apr 30, 2009 at 10:28:29AM +0200, Martin Kersten wrote:
Alex Bo. wrote:
I saw this in the release documentation for June 2008:
Compilation from sources
For convenience of both developers and users as well as to comply even more with open source standards, we now set/use the following defaults for the configure options
--enable-strict, --enable-assert, --enable-debug, --enable-optimize When compiling from CVS sources (as mainly done by developers): strict=yes assert=yes debug=yes optimize=no (*)
...
(*) IMPORTANT NOTE: Since --enable-optimize=yes is no longer the default for any case except binary packages, it is strongly recommended to (re)compile everything from scratch, explicitly configured with --enable-debug=no --enable-assert=no --enable-optimize=yes
Thes are configure options, i.e., for systems that have configure and the auto* tools --- basically all Unix-like systems -- surely not Windows. For Windows build instructions see http://monetdb.cwi.nl/MonetDB/Documentation/Windows-Installation.html As said before, compiler optimization options are on by default on Windows.
Optimization here is to advice the C-compiler to optimize code. The MonetDB optimizer default pipeline can be seen with select optimizer;
For further information see: http://monetdb.cwi.nl/SQL/Documentation/Optimizer-Control.html
This is why I assumed that I am compiling from CVS with the optimizer being disabled. So could you please clear that up for me? Is the optimizer enabled by default or not when building from CVS? Also, how can I tell if the optimizer is running or not when MonetDB is up and running?
As Martin said: MonetDB optimizers are not affected by / related to the C compiler optimization (-switches) mentioned above. Stefan
Thanks.
Stefan Manegold wrote:
On Tue, Apr 21, 2009 at 06:13:46AM -0700, Alex Bo. wrote:
I'm building the latest Monet files from CVS (Monet5, not Monet4) on Windows I'd advise you to use the latest release from CVS, i.e., the Feb2009 branch.
Server 2003.
After reading in the documentation that optimization is disabled by default, Where exactly does the documentation say so?
Unless you call nmake with DEBUG=1, we use -Ox, i.e., optimization is enabled by default...
Just check your nmake logs/output (without optimize=yes) to see which options are given to the compiler. (and potentially compare with that of optimize=yes to see whether there are any differences)
I added optimize=yes to my nmake commands. Nm, does nmake recognize/handle that option? I'm not aware that our Makefile do ...
I start MonetDB with MSQLserver.bat from the Install directory. Whatever I'm doing is working when I leave out optimize=yes from the build procedure. If I look at the original sql/NT/MSQLserver.bat and MonetDB5/NT/M5server.bat, I cannot see how they can result in mserver5.exe being called with --dbfarm=\dbfarm, as your -d10 output suggests ...
To add the output I have been asked for I added "-d 10" to Mserver.bat after "%MONETDB%\bin\mserver.exe" ... Mserver.bat is MonetDB4, not MonetDB5 . M5server.bat is MonetDB5.
MonetDB/SQL requires (and works with) MonetDB5, only, not (with) MonetDB4.
(MonetDB/XQuery requires (and works with) MonetDB4, only, not (with) MonetDB5.)
When running MSQLserver.bat like this, I don't get any welcome message at all. I immediately get the output I put here before. Your -d10 output says # config opt Monet_welcome = yes hence, I'd expect a welcome message ...
Stefan
Thanks.
-- View this message in context: http://www.nabble.com/Compiling-with-optimizer-tp23022199p23155829.html Sent from the monetdb-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
participants (3)
-
Alex Bo. -
Martin Kersten -
Stefan Manegold