issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-19 04:27:54 +0100
From: winston <<wwinston>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
CC: alex_us01
Last updated: 2010-08-20 14:04:04 +0200
## Comment 11286
Date: 2009-03-19 04:27:54 +0100
From: winston <<wwinston>>
mserver appears to start OK. However, the pathfinder option does not appear to start. The start up process exits after the PF/Tijah module v0.9.0 is loaded; the start up exits to the DOS command prompt. This is shown below under the heading: ACTUAL CONSOLE OUTPUT.
According the Tijah documentation, these following two steps should appear last and the command prompt should appear as shown here, and are thus missing:
MonetDB/XQuery module v0.20.0 loaded
XRPC administrative console at http://localhost:50001/admin
MonetDB>
=x=x=x=x=x=
ACTUAL CONSOLE OUTPUT:
C:\MonetDB\MonetDB4>mserver
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>Terminate batch job (Y/N)? y
C:\MonetDB\MonetDB4>mserver --dbinit="module(pathfinder);"
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
C:\MonetDB\MonetDB4>
## Comment 11287
Date: 2009-03-19 07:39:12 +0100
From: @drstmane
I am not sure, which Tijah documentation you refer to, but the MonetDB/XQuery documentation tells clearly how to start a MonetDB/XQuery server *on Windows*;
http://monetdb.cwi.nl/XQuery/QuickTour/HelloWorld/index.html
says
"
Starting Mserver
The first task is to start the MonetDB Server. On Windows platforms this is done by clicking:
Start -> Programs -> MonetDB -> MonetDB XQuery Server
If you are a Linux user, you should type something like:
Mserver --dbinit="module(pathfinder);"
"
Alternatively, on Windows, you can also call "MXQserver.bat" to start the MonetDB/XQuery server.
Maybe, you want to inform the maintainers of the Tijah documentation that you refer to to update their Windows-specific documentation accordingly.
## Comment 11288
Date: 2009-03-19 09:04:19 +0100
From: Henning Rode <<hrode>>
The PF/Tijah documentation was already pointing to MonetDB/XQuery pages here, but I added another direct link to the very helpful "first steps" page, Stefan suggested below.
Does this solve the problem? Or do you still face problems to starting the Mserver with PF/Tijah?
## Comment 11289
Date: 2009-03-21 15:40:59 +0100
From: winston <<wwinston>>
I still have the same problem. Your recommendation does not address the issue. I have the same problem when executing the mxqserver command or from windows menu pick. I merely showed you the command string so that you would see the problem in the MS-DOS command window.
Essentially, I can't get the XQuery part started. The database startup exits without any error message and without giving me a command prompt. Below, please observe the mxqserver output as contrasted to the mserver output; mserver starts OK and gives a MonetDB command prompt, but mxqserver does not start and does not give a MonetDB command prompt, instead exiting to a MS-DOS command prompt.
C:\MonetDB\MonetDB4>mserver
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>
MonetDB>Terminate batch job (Y/N)? y
C:\MonetDB\MonetDB4>mxqserver
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
C:\MonetDB\MonetDB4>
## Comment 11290
Date: 2009-03-22 08:46:04 +0100
From: Henning Rode <<hrode>>
Can someone else take over here? This is so far not a PF/Tijah related problem. Since the XQuery server does not even start correctly, I am in fact not sure, if we should handle this as a bug. It seems to fall more in the category "installation problems". And if there is anyone else able to help you, we need to know also your system details: what kind of machine and windows version you are using.
## Comment 11291
Date: 2009-03-22 10:01:54 +0100
From: @drstmane
Winston,
here are a couple of questions for information that we'd need to analyse/debug your problem:
- Which version of Windows are you using?
- May we assume you installed http://monetdb.cwi.nl/downloads/Windows/Feb2009/MonetDB4-XQuery-Installer-i386-20090227.msi
and no problems occured during installation?
- Is this your first and only installation of MonetDB/XQuery, or did you upgrade/replace a previous version of MonetDB/XQuery?
If the latter, which version of MonetDB/XQuery did you use before, and do you still have database created by that version on your machine?
- Are the following directories writeable for you on your machine?
%APPDATA%\MonetDB4
%APPDATA%\MonetDB4\dbfarm
%APPDATA%\MonetDB4\xquery_logs
- Is general networking enabled or disabled on your machine?
- Did you once manage to successfully start MonetDB with XQuery/pathfinder module, or did already the first attempt fail?
- In case you once managed, what did you do/experience since between the last successful start-up and the first failing one?
(Load & query documents? Encouter errors? If the latter, which ones?)
- Do you happen to have any other servers/services running on your machine that use/block ports 50000 and/or 50001?
You might try to start MonetDB/XQuery with alternative ports, e.g.,
MXQserver.bat --mapi_port=50505
MXQserver.bat --xrpc_port=55555
MXQserver.bat --mapi_port=50505 --xrpc_port=55555
Stefan
## Comment 11292
Date: 2009-03-22 22:27:56 +0100
From: winston <<wwinston>>
Windows XP Pro, SP3
Yes, Installed MonetDB4-XQuery-Installer-i386-20090227.msi
Replaced a previous version of MonetDB and I had troubles doing so: see Ticket 2687825 for more information.
Yes, the directories are writable. MonetDB did create the demo directory.
Yes, networking is enabled.
XQuery never started. It failed on the first and all subsequent attempts.
I tried switching the ports to 50505 and 55555, but I get the same results.
Is there anyway to debug the start up process?
## Comment 11293
Date: 2009-03-23 09:18:43 +0100
From: @drstmane
Thanks.
In
[ 2687825 ] Installation problem - MonetDB will not startup
https://sourceforge.net/tracker/index.php?func=detail&aid=2687825&group_id=56967&atid=482468
you say
"After installing a clean version of MoneyDB4 in a new directory, ..."
^^^^^^^^^^^^^^^^^^
Are you sure that there are no remains of a previous installation of MonetDB left on your system?
Did you next to %APPDATA%\MonetDB4\dbfarm also clean/remove %APPDATA%\MonetDB4\xquery_logs?
Could you possibly consider uninstalling all versions of MonetDB from your system, remove all leftover remains of previous installation and their database (dbfarm) and logs (xquery_logs, sql_logs) and the re-install the latest installer from scratch?
## Comment 11294
Date: 2009-03-25 04:43:50 +0100
From: winston <<wwinston>>
I deleted the %APPDATA%/MonetDB directory and all files.
I reran the MonetDB4-XQuery-Installer-i386-20090227.msi and selected remove MonetDB.
I reran the MonetDB4-XQuery-Installer-i386-20090227.msi and reinstalled MonetDB.
The same exact problem is occuring.
Is there any way to get more debug detail on the startup of MonetDB4?
## Comment 11295
Date: 2009-03-25 07:17:59 +0100
From: @drstmane
Next to
%APPDATA%\MonetDB
did you also remove
%APPDATA%\MonetDB4
^
?
If not, please remove %APPDATA%\MonetDB4\dbfarm & %APPDATA%\MonetDB4\xquery_logs and try again --- otherwise, I'll try to think of some more debugging options and come back to you later ...
## Comment 11296
Date: 2009-03-25 13:18:00 +0100
From: @drstmane
Winston,
with removed or empty %APPDATA%\MonetDB4\dbfarm & %APPDATA%\MonetDB4\xquery_logs --- and in case starting MXQserver.bat still does not work, could you please try to start a plain Mserver.bat, give the following commands in the given order on its "MonetDB>" console prompt, and check/report whether/which work without errors?
module(mapi);
module(pf_support);
module(logger);
module(mkey);
module(xrpc_server);
module(xrpc_client);
module(pf_standoff);
module(pathfinder);
Stefan
## Comment 11297
Date: 2009-04-29 06:56:34 +0200
From: @drstmane
Winston,
is there any news regarding your problem?
Did you test my latest suggestions?
Stefan
## Comment 11298
Date: 2009-05-02 22:45:31 +0200
From: winston <<wwinston>>
Stefan
This appears to have worked OK, but when I try to load documents from the client it fails:
xquery>pf:add-doc("C:\data\XMarkStandard\f0.xml","f0.xml","f0")
more><>
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc("C:\data\XMarkStandard\f0.xml","f0.xml","f0")
ERROR = !ERROR: interpret: no matching MIL operator to 'ws_create(int)'.
xquery>
## Comment 11299
Date: 2009-05-02 23:31:10 +0200
From: winston <<wwinston>>
Stefan,
I followed your procedure one more time, making sure to delete the %APPDATA%\MonetDB4\* files followed by the set of server commands that you gave me on 2009-03-25 08:18.
This time I was able to get the server started and I was able to load documents through the client interface.
I was able to load several documents except for one that was >1GB in size, so I opened a separate bug ticket for this problem.
Thank you for your assistance. You may close this bug.
## Comment 11300
Date: 2009-05-03 08:12:28 +0200
From: @drstmane
Winston,
thanks for the update!
However, if only my work-around of loading all modules by hand works, but using MXQserver.bat or `Mserver.bat --dbinit="module(pathfinder);" does not, this bug report should stay open, and we should (try to) find out what is going wrong and (preferably) fit it (provided it is a problem inside MonetDB).
Stefan
## Comment 11301
Date: 2009-05-05 23:49:03 +0200
From: @drstmane
Same problem has also been reported in
ID: 2787535 "XQuery Server doesn't start in Windows XP"
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2787535&group_id=56967
## Comment 11302
Date: 2009-05-07 04:41:14 +0200
From: winston <<wwinston>>
The installation that I am having trouble with is a Dell laptop with Windows XP SP3, Intel Core 2.
ACTION TAKEN: I installed MonetDB on one of my older HP PCs with Win XP SP2, Intel Pentium 4.
RESULTS: The WinXP SP2 installation seems to be working OK. The problems I am encountering are all on the WinXP SP3 on the Dell.
## Comment 11303
Date: 2009-05-07 06:49:38 +0200
From: @drstmane
Winston,
thanks for the update!
Do I understand correctly, that on the WinXP SP2 starting the MonetDB/XQuery server via the start menu entry and/or via MXQserver.bat works fine, while it fails on the WinXP SP3 machine?
The hardware should not make a difference, so I expect the problems to be related to WinXP SP2 vs. SP3.
Are both of your Windows 32-bit?
Alex (who posted ID: 2787535),
which version of Windows XP are you using?
SP2 or SP3?
32-bit or 64-bit?
Stefan
## Comment 11304
Date: 2009-05-07 15:21:28 +0200
From: @sjoerdmullender
Winston,
I have a couple of questions for you:
- which older version of MonetDB did you replace with the new installation?
- the default location of older versions of MonetDB was C:\Program Files\CWI\MonetDB4, whereas now it is C:\Program Files\MonetDB\MonetDB4. In which location did you install, and are there any files left over in the old location?
- still older versions of MonetDB installed a few files in C:\Windows\system32 (files matching the pattern lib*.dll). We don't do that anymore. Do you have any of those files still lying around?
- the default database location is %APPDATA%\MonetDB4. Did you remove that folder?
- older versions of MonetDB used %APPDATA%\MonetDB (note the missing 4) as the location of the database. The Mserver.bat script has code to use that folder if the MonetDB4 folder does not exist. Did you have the MonetDB folder?
The installers are built on a Windows XP Professional SP3 system and have also been tested on such a system. I was able to start the server from the Start menu and do a simple query.
## Comment 11305
Date: 2009-05-08 04:03:44 +0200
From: winston <<wwinston>>
The version of windows XP is 32-bit. I have several software products installed, including DB2 and SQL Server.
I don't recall the older MonetDB versions I replaced, but there were a couple going back a few years. Previously, I also installed and removed MonetDB5. I have no C:\Program Files\CWI directory.
I installed the March 2009 3/24 version of MonetDB. I installed this version in C:\MonetDB\MonetDB4 directory. Today, I removed and reinstalled MonetDB in the default location Program Files.
I found libfdnvin.dll in C:\Windows\system32 with a date of 6/8/2000. I removed this file from this directory. Also removed a file call libeay32.dll. (OpenSSL ?)
The same behavior occurred.
Is there a way to trace what files MonetDB is loading from what directories?
## Comment 11306
Date: 2009-05-08 10:15:20 +0200
From: @sjoerdmullender
To see which files are loaded by MonetDB, you can do the following:
Go to the Microsoft Sysinternals website (http://technet.microsoft.com/en-us/sysinternals/default.aspx). On the left of the page there is a link to Sysinternals Suite. Go there. Then either download the whole suite (top right of the page), or just the Process Monitor (which is part of the suite). Install the download (i.e. extract somewhere) and start the Process Monitor (Procmon.exe).
After accepting the license, select the menu entry Filter -> Filter... (or click on the Filter toolbutton). In the pop up, change the fields at the top to read:
Process Name is Mserver.exe then Include
then Add and Apply (or OK).
Then start MonetDB XQuery Server from the Start menu.
After this you can File -> Save... the captured events. Save them as CSV and attach the file to this bug report.
## Comment 11307
Date: 2009-05-09 17:39:16 +0200
From: winston <<wwinston>>
Trace added. Split into two files due to size restrictions
## Comment 11308
Date: 2009-05-12 17:59:29 +0200
From: @sjoerdmullender
I see lots of differences between your log and one I made on my system.
Can you try removing the file C:\WINDOWS\Prefetch\MSERVER.EXE-2DF2C547.pf and then try again?
This file has to do with prefetching. It should make loading the program faster. I can imagine it somehow got corrupted, so if you remove it, perhaps it works better.
Lines 8 to 14973 in your log are equivalent to lines 8 to 11 in mine. So there is a *huge* difference.
## Comment 11309
Date: 2009-05-19 04:16:25 +0200
From: winston <<wwinston>>
Why the difference? In the DOS window, before starting MServer, I cleared out the path environment variable. The size was reduced, but it is still many hundreds of lines.
What should the environment variables look like?
I tried to delete the file: C:\WINDOWS\Prefetch\MSERVER.EXE-2DF2C547.pf, but it is no longer there.
No difference after emptying the path variable.
## Comment 11310
Date: 2009-05-20 16:10:24 +0200
From: @sjoerdmullender
I just attached two files to this bug. One contains a copy/paste of a cmd session of a successful start with the output of the "set" command to show my environment. It's pretty small. The other file is a zip containing two log dump from procmon for two different successful runs. Notice that both these logs are significantly smaller than yours (two of them together fit easily within the sourceforge limit).
I compared your log with mine by removing the first few columns from the logs (up to and including the PID column) and then using diff.
In the mean time, I have no idea what the problem can be.
## Comment 11311
Date: 2009-06-04 22:28:39 +0200
From: @drstmane
Just for the records, here's a small correction for my suggested work-around of 2009-03-25 13:18 :
If loading modules individually, this should happen in the following order:
module(pf_support);
module(logger);
module(mkey);
module(xrpc_server);
module(xrpc_client);
module(pf_standoff);
module(pathfinder);
module(mapi);
i.e., module "mapi" should be last, not first.
Stefan
## Comment 11312
Date: 2009-10-11 20:29:53 +0200
From: winston <<wwinston>>
Reinstalled Windows XP from scratch -> installed MonetDB -> everything works OK.
## Comment 11313
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2693363 at http://sourceforge.net/support/tracker.php?aid=2693363
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 14116
Date: 2010-06-17 15:44:49 +0200
From: @sjoerdmullender
*** Bug #2068 has been marked as a duplicate of this bug. ***
## Comment 15809
Date: 2011-05-16 21:50:58 +0200
From: @njnes
Changeset [f169139660d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f169139660d8) 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=f169139660d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f169139660d8)
Changeset description:
add test for count-count-distinct bug #2808
check variable sized types on binary copy into (solves bug #2010).
| PF: mserver does not start with pathfinder option on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2010/comments | 0 | 2020-11-30T10:16:27Z | 2024-06-28T13:27:02Z | https://github.com/MonetDB/MonetDB/issues/2010 | 753,345,581 | 2,010 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-17 03:23:07 +0100
From: Vera Hollink <<vhollink>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
CC: @sjoerdmullender
Last updated: 2010-08-31 13:40:34 +0200
## Comment 11281
Date: 2009-03-17 15:23:07 +0100
From: Vera Hollink <<vhollink>>
mclient gives an error on the following code:
return <item> {tijah:tokenize(concat($record/Bijschrift_NL/text(), " Hallo wereld!"))} </item>
I get the error:
ERROR = !fatal error: column 'pos15' with type '0xB00001' not found in environment
! halted in ../../../../source/pathfinder/compiler/mil/milgen.brg (env_mvar_), line 704
The following `partial' queries do give correct results:
return <item> {tijah:tokenize("Hallo wereld!")} </item>
return <item> {concat($record/Bijschrift_NL/text(), " Hallo wereld!")} </item>
## Comment 11282
Date: 2009-03-17 15:32:52 +0100
From: Henning Rode <<hrode>>
hej jan, i just guess we have a problem here in the iter/item/pos handling for this function:
to make debugging easier you can use any other collection/document an reproduce the same error:
tijah:tokenize(concat((pf:collection("thesis")//thesis//text()), "hello"))
btw. it works this way correctly:
tijah:tokenize(concat(string-join((pf:collection("thesis")//thesis//text()), ""), "hello"))
maybe that helps.
## Comment 11283
Date: 2009-03-18 10:24:41 +0100
From: Jan Flokstra <<jflokstra>>
This is the polymorphic pos problem which keeps bothering is. This case is different because for tokenize() I do not use the pack/unpack scheme used for other functions. I first tried to use the empty dummypos I used in in the pack/unpack scheme but ran into CTrefine errors with non-matching bats. Could not solve this and I now detect polymorphic pos bats and retrieve pos from the env by using only the aat_pre type. This works for my small examples, like
for $d in doc("dilbert.xml")//bubble
return tijah:tokenize(concat($d/text(),"newtail"))
I fixed it in Stable so it could take some time before it is also in Current,
JanF.
## Comment 11284
Date: 2009-08-14 13:55:21 +0200
From: @drstmane
tagged subject
## Comment 11285
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2690141 at http://sourceforge.net/support/tracker.php?aid=2690141
## Comment 14868
Date: 2010-08-31 13:39:59 +0200
From: @sjoerdmullender
Changeset [f969c8bc9c3c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f969c8bc9c3c) 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=f969c8bc9c3c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f969c8bc9c3c)
Changeset description:
Added test for ancient bug #2009.
## Comment 14869
Date: 2010-08-31 13:40:34 +0200
From: @sjoerdmullender
Fixed long ago.
| PFtijah: tokenize() fails when applied to result of concat() | https://api.github.com/repos/MonetDB/MonetDB/issues/2009/comments | 0 | 2020-11-30T10:16:25Z | 2024-06-27T11:38:35Z | https://github.com/MonetDB/MonetDB/issues/2009 | 753,345,550 | 2,009 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-15 06:29:30 +0100
From: winston <<wwinston>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-03-19 04:17:26 +0100
## Comment 11277
Date: 2009-03-15 18:29:30 +0100
From: winston <<wwinston>>
After installing a clean version of MoneyDB4 in a new directory, I get the following message when trying to start the database. How do I correct this problem? What is MonetDB talking about? What file/directory is MonetDB looking at?
C:\MonetDB\MonetDB4>mxqserver
!ERROR: BBPinit: old BBP without version number
!ERROR: dump the database using a compatible version,
!ERROR: then restore into new database using this version.
Press any key to continue . . .
## Comment 11278
Date: 2009-03-15 18:48:36 +0100
From: @drstmane
Which version of MonetDB(/XQuery?) did you install?
The latest Feb2009 release?
It seems to still have an old database in %APPDATA%\MonetDB4\{dbfarm,xquery_logs}.
If you need/want to migrate this database, you need to install a compatible version of MonetDB (the one it was originally created and/or last successfully used with), dump the database, upgrade to the latest Feb2009 release and then restore the dump. See the release notes for details: http://monetdb.cwi.nl/projects/monetdb/Development/Releases/Feb2009/index.html
In case you don't want/need to keep/migrate this database simply remove the respective directories.
## Comment 11279
Date: 2009-03-19 04:17:26 +0100
From: winston <<wwinston>>
Thank You! I deleted the old database and the system started.
## Comment 11280
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687825 at http://sourceforge.net/support/tracker.php?aid=2687825
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Installation problem - MonetDB will not startup | https://api.github.com/repos/MonetDB/MonetDB/issues/2008/comments | 0 | 2020-11-30T10:16:21Z | 2024-06-28T13:27:01Z | https://github.com/MonetDB/MonetDB/issues/2008 | 753,345,505 | 2,008 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-15 03:28:01 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-17 03:58:03 +0200
## Comment 11273
Date: 2009-03-15 15:28:01 +0100
From: Jan Rittinger <<jan.rittinger>>
I open this bug as a reminder for memory problems in the current STABLE and HEAD versions.
(All observations where made on Mac OS X 10.5.6)
Running the example queries on dblp.xml (441 MB):
Q0: count(/dblp//author[text()="Michael Stonebraker"])
Q1: count(/dblp/*/author[text()="Michael Stonebraker"])
leads to various observations:
1.) Release 0.24 is faster than Feb2009
2.) Release Feb2009 is faster than Nov2008
3.) Release Nov2008 is faster than HEAD (03/10/2009)
4.) Document loading is getting slower if query is run multiple times
5.) Queries are getting slower if run multiple times
For more details please look into the MonetDB developers mailing list topic: [MonetDB-users] too deep recursion.
A related observation is that running XMark Q11 and Q12 (sf=1) needs twice the time due to the checkin to MonetDB/src/gdk gdk_heap.mx,,1.107,1.108 on February, 5th. This problem is even more dramatic in the current HEAD version on XIRAF queries (see pathfinder wiki).
## Comment 11274
Date: 2009-03-15 16:06:43 +0100
From: @drstmane
a) from 1.) - 3.) I derive
0.24 < Feb2009 < Nov2008 < HEAD
b) the various releases diff by more than only memory management
c) for analysis of their respective performance impact,
here are the details of Peter's recent memory managment changes
(changes that involve more than 2 files have been wrapped in CVS tags as indicated below):
===================================================================
2009/02/10 - sjoerd: MonetDB/src/gdk/gdk_heap.mx,1.110
propagated changes of Tuesday Feb 10 2009
from the Feb2009 branch to the development trunk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2009/02/10 - stmane: src/gdk/gdk_heap.mx,1.107.2.1
[on behalf of Peter] re-doing
2009/02/05 - boncz: MonetDB/src/gdk/gdk_heap.mx,1.108
- make large allocs fall back again on mmap
now only the actually intended changes
and as bug fix, i.e., in the Feb2009 release branch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
===================================================================
===================================================================
2009/03/02 - boncz: MonetDB/src/common/monet_options.py.in,1.40
MonetDB/src/gdk/gdk.mx,1.275 MonetDB/src/gdk/gdk_bat.mx,1.209
MonetDB/src/gdk/gdk_heap.mx,1.111 MonetDB/src/gdk/gdk_utils.mx,1.228
MonetDB4/conf/MonetDB.conf.in,1.17
MonetDB4/src/gdk/Tests/directsemijoin.milS,1.3
MonetDB4/src/gdk/Tests/directsemijoin.stable.out,1.3
MonetDB4/src/gdk/Tests/malloc_mmap_priv.milS,1.2
MonetDB4/src/gdk/Tests/malloc_mmap_priv.stable.out,1.2
MonetDB4/src/modules/plain/sys.mx,1.18
MonetDB4/src/tools/Tests/client.stable.out,1.2
MonetDB4/src/tools/Tests/client.stable.out.64bit,1.2
MonetDB4/src/tools/Tests/multiClientSeq.stable.out,1.2
MonetDB4/src/tools/Tests/multiClientSeq.stable.out.64bit,1.2
MonetDB4/src/tools/Tests/server.stable.out,1.2
MonetDB4/tests/Availability/Tests/01_Modules_static.stable.out,1.18
MonetDB4/tests/BugTracker/Tests/mmap_bats.SF-1428389.prelude,1.2
MonetDB4/tests/BugTracker/Tests/project_on_BAT_with_batFirst.SF-2020806.milS,1.3
MonetDB4/tests/BugTracker/Tests/project_on_BAT_with_batFirst.SF-2020806.stable.out,1.5
MonetDB4/tests/by_Peter/Tests/tst_append_readonly.milS,1.3
MonetDB4/tests/by_Peter/Tests/tst_append_readonly.stable.out,1.5
MonetDB4/tests/by_Peter/Tests/tst_append_readonly_commit.milS,1.3
MonetDB4/tests/by_Peter/Tests/tst_append_readonly_commit.stable.out,1.6
MonetDB4/tests/by_Peter/Tests/tst_mmap.milS,1.4
MonetDB4/tests/by_Peter/Tests/tst_mmap.stable.out,1.4
MonetDB4/tests/by_Peter/Tests/tst_updatestr.milS,1.4
MonetDB4/tests/by_Peter/Tests/tst_updatestr.stable.out,1.5
MonetDB4/tests/by_Peter/Tests/tst_writestr.milS,1.4
MonetDB4/tests/by_Peter/Tests/tst_writestr.stable.out,1.4
MonetDB5/conf/monetdb5.conf.in,1.41
MonetDB5/src/mal/Tests/performanceTests/perf.conf,1.16
MonetDB5/src/modules/kernel/status.mx,1.58
OK, back from holiday I decided to fix this mmap issue.
There are two distinct vm thresholds of importance:
(1) the miminum heap size after which a heap may become memory mapped
(2) the allocation size after which mmap is obligatory
I have decided for (2) to simply use GDK_mem_maxsize (ie allocations
larger than the RAM). Creating files for heap allocation is to
be avoided unless in extreme situations. I also checked that
HEAPalloc/HEAPextend fall back onto file-based mmap if allocation
fails.
Regarding (1) there was already inconsistency, because apart from
GDK_vm_minsize, some other code pieces were already using
REMAP_PAGE_MAXSIZE. I have decided to convert all such checks to the latter.
This means GDK_vm_minsize is removed as a variable in GDK, and also
as a configurable environment variable. Less knobs is better.
===================================================================
is wrapped in CVS tags "with_GDK_vm_minsize" & "without_GDK_vm_minsize"
===================================================================
2009/03/05 - boncz: MonetDB/src/common/monet_options.mx,1.31
MonetDB/src/common/monet_options.py.in,1.41
MonetDB/src/gdk/gdk.mx,1.276 MonetDB/src/gdk/gdk_heap.mx,1.112
MonetDB/src/gdk/gdk_utils.mx,1.229
re-introducing a knob to set the threshold above which to use mmap-
on-tempfile now named: gdk_mmap_minsize
on large jobs, setting this one to e.g. 200MB should be of interest
===================================================================
is wrapped in CVS tags "without_GDK_mmap_minsize" & "with_GDK_mmap_minsize"
===================================================================
2009/03/06 - boncz: MonetDB/src/gdk/gdk_utils.mx,1.230
- adaptively swap GDK_mmap_minsize back to small (128MB) if vmtrim detects memory crunch.
===================================================================
===================================================================
2009/03/07 - boncz: MonetDB/src/gdk/gdk_posix.mx,1.164
MonetDB/src/gdk/gdk_utils.mx,1.231
- start vmtrim actions when rss > .5mem_maxsize (was: .75mem_maxsize)
- make the mmap_minsize adaptive between 256MB and 16MB depending on
the severity of the memory shortage
===================================================================
===================================================================
2009/03/08 - boncz: MonetDB/src/gdk/gdk_posix.mx,1.165
MonetDB/src/gdk/gdk_utils.mx,1.232
- made the mmap-on-tempfile a bit more adaptive
===================================================================
## Comment 11275
Date: 2009-04-17 15:57:37 +0200
From: @peterboncz
The performance problems on Jan's machine and especially those related to multiple queries were related to swapping (BBPtrim) triggering on the near full use of the VM address space. On 32-bits systems, MonetDB tries to limit VM usage below 2GB, though Jan in his machine has 4GB RAM.
In february there have been a number of tweaks regarding TPCH 100GB experiments, some iterations of that process indeed brought performance degradation. However, I consider those problems as solved.
btw, I ran xmark 100MB on the same platform as the sigmod paper
sigmod now
q01 0.12 0.10
q02 0.19 0.12
q03 1.20 0.37
q04 0.42 0.29
q05 0.08 0.08
q06 0.00 0.02
q07 0.01 0.02
q08 0.47 0.52
q09 0.52 0.62
q10 5.18 2.99
q11 3.62 7.16
q12 2.11 4.37
q13 0.10 0.07
q14 0.93 1.10
q15 0.07 0.10
q16 0.08 0.13
q17 0.15 0.19
q18 0.05 0.09
q19 0.38 0.44
q20 0.62 0.23
This is mostly a mps/alg comparison, not so much memory consumption. One can say performance is at least on par, generally better. Only q11/q12 are slower. I remember we did some special things in mps to avoid materializing columns that were not needed in the aggregation, but you would expect that algebra DCE wouls automatically do that as well.
anyway, I am closing this one for now
## Comment 11276
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687705 at http://sourceforge.net/support/tracker.php?aid=2687705
| Performance degradation due to memory management | https://api.github.com/repos/MonetDB/MonetDB/issues/2007/comments | 0 | 2020-11-30T10:16:18Z | 2024-06-27T11:38:33Z | https://github.com/MonetDB/MonetDB/issues/2007 | 753,345,457 | 2,007 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-15 12:01:57 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2009-05-28 11:11:32 +0200
## Comment 11270
Date: 2009-03-15 12:01:57 +0100
From: @drstmane
test sql/src/test/VOC/Tests/VOC.SQL.sh fails with multiple
Connection warning: BBPdecref: range error -770364496
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora8/src_test_VOC/VOC.out.00.html
## Comment 11271
Date: 2009-05-28 23:11:32 +0200
From: @njnes
fixed the problem (copy paste bug)
## Comment 11272
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687557 at http://sourceforge.net/support/tracker.php?aid=2687557
| SQL: VOC test fails with BBPdecref: range error | https://api.github.com/repos/MonetDB/MonetDB/issues/2006/comments | 0 | 2020-11-30T10:16:15Z | 2024-06-27T11:38:32Z | https://github.com/MonetDB/MonetDB/issues/2006 | 753,345,419 | 2,006 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-15 11:58:54 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-04-01 07:42:10 +0200
## Comment 11267
Date: 2009-03-15 11:58:54 +0100
From: @drstmane
since today Sun Mar 15 2009 test union_leak.SF-2540169 fails with
/bin/sh: line 1: 23551 Segmentation fault mserver5 "--config=/scratch/monet.GNU.64.64.d.1.26473/MonetDB5/.GNU.64.64.d.1-Fedora8/etc/monetdb5.conf" --debug=10 --set gdk_nr_threads=4 --set "monet_mod_path=/scratch/monet.GNU.64.64.d.1.26473/sql/Fedora8/src/backends/monet5/.libs:/scratch/monet.GNU.64.64.d.1.26473/sql/Fedora8/src/backends/monet5:/scratch/monet.GNU.64.64.d.1.26473/MonetDB5/.GNU.64.64.d.1-Fedora8/lib64/MonetDB5:/scratch/monet.GNU.64.64.d.1.26473/MonetDB5/.GNU.64.64.d.1-Fedora8/lib64/MonetDB5/lib:/scratch/monet.GNU.64.64.d.1.26473/MonetDB5/.GNU.64.64.d.1-Fedora8/lib64/MonetDB5/bin" --set "gdk_dbfarm=/scratch/monet.GNU.64.64.d.1.26473/sql/Fedora8/dbfarm" --set "sql_logdir=/scratch/monet.GNU.64.64.d.1.26473/sql/Fedora8/sql_logs" --set "xquery_logdir=/scratch/monet.GNU.64.64.d.1.26473/sql/Fedora8/xquery_logs" --set mapi_open=true --set xrpc_open=true --set mapi_port=30565 --set xrpc_port=46410 --set xrpc_docroot=/scratch/monet.GNU.64.64.d.1.26473/sql --set monet_prompt= --trace "--dbname=mTests_src_test_BugTracker-2009" --set mal_listing=0 "--dbinit= include sql;"
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora8/src_test_BugTracker-2009/union_leak.SF-2540169.err.00.html
## Comment 11268
Date: 2009-04-01 19:42:10 +0200
From: @drstmane
Tests appears to be working fine, again, since Thu Mar 19 2009.
## Comment 11269
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687553 at http://sourceforge.net/support/tracker.php?aid=2687553
| SQL: test union_leak.SF-2540169 segfault since Mar 15 2009 | https://api.github.com/repos/MonetDB/MonetDB/issues/2005/comments | 0 | 2020-11-30T10:16:11Z | 2024-06-27T11:38:31Z | https://github.com/MonetDB/MonetDB/issues/2005 | 753,345,370 | 2,005 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-15 11:53:40 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2009-06-09 10:12:00 +0200
## Comment 11263
Date: 2009-03-15 11:53:40 +0100
From: @drstmane
test fails since Sat Feb 28 2009 i.e., after checkins on Friday Feb 27 2009, (now) with
Error: MALException:mkey.bulk_rotate_xor_hash:command failed
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora8/src_test_BugDay_2005-10-06_2.9.3/type_dump_test.SF-989257.err.00.html
## Comment 11264
Date: 2009-06-05 13:29:50 +0200
From: @drstmane
The error message is now a bit more verbose:
Error: MALException:mkey.bulk_rotate_xor_hash:Operation failed Operands not synced on head
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-10-06_2.9.3/type_dump_test.SF-989257.err.00.html
## Comment 11265
Date: 2009-06-09 22:12:00 +0200
From: @njnes
fixed by using leftjoin's for projection joins
## Comment 11266
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687549 at http://sourceforge.net/support/tracker.php?aid=2687549
| SQL: test type_dump_test.SF-989257.SQL.sh fails since Feb 28 | https://api.github.com/repos/MonetDB/MonetDB/issues/2004/comments | 0 | 2020-11-30T10:16:08Z | 2024-06-27T11:38:30Z | https://github.com/MonetDB/MonetDB/issues/2004 | 753,345,334 | 2,004 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-14 05:17:48 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-03-16 11:23:14 +0100
## Comment 11257
Date: 2009-03-14 17:17:48 +0100
From: @drstmane
checkins between Tue Mar 10 2009 & Fri Mar 13 2009 (there was no reliable testing in between due to SF CVS problems) cause test MonetDB4/src/modules/plain/Tests/bat.py to fail; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora8/src_modules_plain/bat.out.00.html
## Comment 11258
Date: 2009-03-16 21:48:24 +0100
From: @sjoerdmullender
You only need to execute the code starting at the comment "create large bats bc (chr) and bl (lng)" to reproduce this.
When I do both (with of course --set gdk_mem_pagebi1970-01-01 01:00:16 +0100) in the Feb2009 release and today's stable, I see this difference:
Feb2009:
MonetDB>bc.info().find("tail.storage").print();
[ "memory mapped" ]
MonetDB>mc.info().find("tail.storage").print();
[ "private map" ]
Stable:
MonetDB>bc.info().find("tail.storage").print();
[ "malloced" ]
MonetDB>mc.info().find("tail.storage").print();
[ "malloced" ]
So for some reason the bat is no longer mmap'ed in the Stable.
## Comment 11259
Date: 2009-03-16 23:06:14 +0100
From: @sjoerdmullender
I figured it out:
The test code creates a bat with bat(void,chr,n-1LL) where n=lng(100*REMAP_PAGE_SIZE). In other words, bat(void,chr,6553599LL) and then calls mmap(theBat,1) on it.
In the old situation, the capacity of the new bat would be 6553599, but since the bat is iteratively filled to size n, i.e. one larger than the asked for size, the bat is extended. This will get into HEAPextend and because of the call to mmap, HEAPextend will extend the bat using a memory-mapped file.
In the new situation, because of a change I made for the bat cache, bat capacities are always rounded up to the next multiple of BATTINY (128), which in this case is exactly the aforementioned n. This means that the bat is never extended since the capacity is large enough, and so the heap never becomes memory-mapped.
The question is, is this something we should fix in the test (use n-128LL instead of n-1LL) or in the C code (only round up if the capacity is smaller than some threshold)?
## Comment 11260
Date: 2009-03-16 23:15:39 +0100
From: @sjoerdmullender
Make that n-256LL (BATTINY=256, not 128). Then the test works, modulo the MIL trace which differs of course.
## Comment 11261
Date: 2009-03-16 23:23:14 +0100
From: @sjoerdmullender
I checked in a change to the test, thus fixing the bug.
## Comment 11262
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2687040 at http://sourceforge.net/support/tracker.php?aid=2687040
| M4: test src/modules/plain/Tests/bat.py fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2003/comments | 0 | 2020-11-30T10:16:05Z | 2024-06-27T11:38:29Z | https://github.com/MonetDB/MonetDB/issues/2003 | 753,345,291 | 2,003 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-13 01:58:36 +0100
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-06-19 11:10:20 +0200
## Comment 11252
Date: 2009-03-13 13:58:36 +0100
From: Wouter Alink <<alink>>
Adding documents using an XML document which lists the names of the documents doesn't work in the Algebra version. Using MPS works fine. See below.
I'm using the stable Feb2009 branch
$ cat /tmp/aap.xml
<aap/>
$ cat test.xq
for $i in <docs>
<doc>/tmp/aap.xml</doc>
</docs>//doc
let $docname := $i cast as xs:string
let $data := $i cast as xs:string
return pf:add-doc($data,$docname,"patents04")
$ mclient -G -lxq -p50030 test.xq
MAPI = monetdb@localhost:50030
QUERY = for $i in <docs>
ERROR = !ERROR: interpret: no matching MIL operator to 'DocmgmTape(BAT[oid,BAT], BAT[oid,str], BAT[oid,str], BAT[oid,str], BAT[oid,lng])'.
!MAYBE YOU MEAN:
! DocmgmTape(BAT[void,BAT], BAT[void,str], BAT[void,str], BAT[void,str], BAT[void,lng]) : void
$ mclient -g -lxq -p50030 test.xq
$
## Comment 11253
Date: 2009-03-13 15:13:15 +0100
From: @lsidir
A fix has been commited to the Feb2009 branch. A test is pending
## Comment 11254
Date: 2009-06-16 10:41:16 +0200
From: @lsidir
This is fixed but there is no test still? Wouter can you come up with a test and add it?
Thank you,
lefteris
## Comment 11255
Date: 2009-06-19 11:10:20 +0200
From: Wouter Alink <<alink>>
Test added in tests/BugTracker: oidInDocMgmt.SF-2686121
Closing bug.
## Comment 11256
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2686121 at http://sourceforge.net/support/tracker.php?aid=2686121
| XQ: oids in DocmgmTape | https://api.github.com/repos/MonetDB/MonetDB/issues/2002/comments | 0 | 2020-11-30T10:16:01Z | 2024-06-27T11:38:28Z | https://github.com/MonetDB/MonetDB/issues/2002 | 753,345,251 | 2,002 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-13 12:05:57 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-03-13 02:34:52 +0100
## Comment 11248
Date: 2009-03-13 12:05:57 +0100
From: @drstmane
.../MonetDB5/src/mal/mal_recycle.mx(1028): error 175: subscript out of range
li = *(bit*)getVarValue(recycleBlk,getArg(q,4));
^
.../MonetDB5/src/mal/mal_recycle.mx(1029): error 175: subscript out of range
hi = *(bit*)getVarValue(recycleBlk,getArg(q,5));
^
.../MonetDB5/src/mal/mal_recycle.mx(1033): error 175: subscript out of range
lip = *(bit*)VALget(&s->stk[getArg(p,4)]);
^
.../MonetDB5/src/mal/mal_recycle.mx(1034): error 175: subscript out of range
hip = *(bit*)VALget(&s->stk[getArg(p,5)]);
^
compilation aborted for mal_recycle.c (code 2)
.../MonetDB5/src/modules/mal/mal_io.mx(596): error 175: subscript out of range
case 5: msg= IOprintf_(&fmt2,*fmt G(2) G(3) G(4));
^
[...]
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
.../MonetDB5/src/modules/mal/mal_io.mx(640): error 175: subscript out of range
case 11: msg= IOprintf_(&fmt2,*fmt G(3) G(4) G(5) G(6) G(7) G(8) G(9) G(10));
^
compilation aborted for mal_io.c (code 2)
.../MonetDB5/src/compiler/mal_compiler.mx(639): error 175: subscript out of range
mccVar(f,mb,getArg(p,4));
^
compilation aborted for mal_compiler.c (code 2)
.../MonetDB5/src/optimizer/opt_crack.mx(85): error 175: subscript out of range
mb->var[getArg(p,4)]->value.val.ival != 0 ) continue;
^
compilation aborted for opt_crack.c (code 2)
[...]
.../MonetDB5/src/optimizer/opt_history.mx(160): error 175: subscript out of range
getVarConstant(mb,getArg(p,4)).val.lval =
^
.../MonetDB5/src/optimizer/opt_history.mx(161): error 175: subscript out of range
GDKusec()-getVarConstant(mb,getArg(p,4)).val.lval ;
^
compilation aborted for opt_history.c (code 2)
## Comment 11249
Date: 2009-03-13 12:18:40 +0100
From: @drstmane
might be related to / cause by
MonetDB5/src/mal/mal_instruction.mx:307:define MAXARG 4 /* BEWARE the code depends on this knowledge */
MonetDB5/src/mal/mal_instruction.mx:328: int prps[MAXARG]; /* property array */
MonetDB5/src/mal/mal_instruction.mx:374: int argv[MAXARG]; /* at least a few entries */
## Comment 11250
Date: 2009-03-13 14:34:52 +0100
From: @drstmane
Fixed by Martin.
Thanks.
## Comment 11251
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2686045 at http://sourceforge.net/support/tracker.php?aid=2686045
| M5 fails to compile with optimization enabled (gcc & icc) | https://api.github.com/repos/MonetDB/MonetDB/issues/2001/comments | 0 | 2020-11-30T10:15:58Z | 2024-06-27T11:38:27Z | https://github.com/MonetDB/MonetDB/issues/2001 | 753,345,208 | 2,001 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-13 10:43:44 +0100
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-11-20 02:05:37 +0100
## Comment 11244
Date: 2009-03-13 10:43:44 +0100
From: @swingbit
-- A table with unsorted values in a and b
create table unsorted (a int,b int);
insert into unsorted values (2, 3);
insert into unsorted values (1, 2);
insert into unsorted values (4, 1);
insert into unsorted values (3, 2);
insert into unsorted values (2, 3);
insert into unsorted values (3, 3);
insert into unsorted values (3, 1);
insert into unsorted values (4, 3);
-- Store it in a new table with tuples sorted on a,b
create table sorted (a int, b int);
insert into sorted
select * from unsorted
order by a,b;
-- these tho are semantically equivalent (the group by attributes are swapped)
trace select a,b from sorted group by a,b;
trace select a,b from sorted group by b,a;
The first version is much faster, as it exploits the sortedness on a,b when grouping on a,b.
The second version identifies the same groups. Therefore, the sortedness on a,b could be exploited when grouping on b,a, but it isn't.
Even on such a small example, the trace shows already a performance difference, which becomes dramatic on larger data.
In general, when a table is sorted on a1,a2,...,aN ,
grouping on any permutation of a1,a2,...,aK with K<=N should exploit sortedness.
## Comment 11245
Date: 2009-03-13 10:51:55 +0100
From: @drstmane
Good point --- while performance can be considered bugs, a solution might only become available as new feature in the CVS HEAD and hence in the next feature release --- Martin's recently added "derivepath" MAL optimizer provides a framework that can be exploited to do the proposed (and other, e.g., exploit also uniqueness) optimization for multi-attribute grouping, very similar to what the "joinpath" optimizer does for (binary- / mapping- / pivot-) join paths.
## Comment 11246
Date: 2009-11-20 14:05:36 +0100
From: @njnes
added a test to src/test/BugTracker-2009/Tests/use_order_column_first.SF-2686008.sql
fixed by an optimizer which checks for sorted columns in the group by (only works when we can easily derive the base table)
## Comment 11247
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2686008 at http://sourceforge.net/support/tracker.php?aid=2686008
| SQL: multi-attribute GROUP BY may ignore sortedness | https://api.github.com/repos/MonetDB/MonetDB/issues/2000/comments | 0 | 2020-11-30T10:12:34Z | 2024-06-27T11:38:26Z | https://github.com/MonetDB/MonetDB/issues/2000 | 753,342,722 | 2,000 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-11 08:57:17 +0100
From: Loredana Afanasiev <<lafanasi>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-18 06:30:35 +0200
## Comment 11237
Date: 2009-03-11 20:57:17 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi team,
After running one query in a multi-user scenario (N clients/threads simultaneously) the memory footprint of mserver (% of the memory that the server occupies) grew. After repeating the experiment M times the memory grew each time and eventually crashed. Running the same query sequentially the same number of times leaves the footprint of mserver constant. Could it be a faulty memory cleaning? Details below.
Thanks,
l.
Query: q3.xq
let $col := fn:collection("MotiesTweedeKamer")
let $years := fn:distinct-values(
for $date in $col//hiddendatum
return fn:substring(fn:string($date),1,4))
for $y in $years
order by $y ascending
return <result year="{$y}" count="{
count($col//document[fn:substring(fn:string(.//hiddendatum),1,4) = $y])
}"/>
N = number of parallel users
M = number of sequential runs
* CVS HEAD 2009-03-04
Multithreaded
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
N=60,M=1
5793 lafanasi 20 0 11.5g 9.5g 10m S 2 48.4 16:53.90 Mserver
N=60,M=1
5793 lafanasi 20 0 14.7g 12g 10m S 0 61.6 32:56.46 Mserver
N=60,M=1
5793 lafanasi 20 0 16.4g 13g 10m S 0 67.9 48:10.48 Mserver
N=60,M=1
5793 lafanasi 20 0 17.1g 13g 7968 S 1 68.2 64:07.58 Mserver
N=60,M=1
5793 lafanasi 20 0 17.5g 13g 7564 S 2 67.4 78:18.33 Mserver
N=60,M=4
5793 lafanasi 20 0 20.4g 14g 5320 S 2 72.0 143:11.85 Mserver
N=60,M=6
MAPI = monetdb@localhost:50000
QUERY = let $col := fn:collection("MotiesTweedeKamer")
ERROR = !ERROR: BBPdecref: 1000061400_prop_val does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_attr_qn does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_attr_prop does not have pointer fixes.
QUERY = let $col := fn:collection("MotiesTweedeKamer")
ERROR = !ERROR: BBPdecref: 1000061400_rid_level does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_rid_prop does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_prop_text does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_prop_val does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_attr_qn does not have pointer fixes.
!ERROR: BBPdecref: 1000061400_attr_prop does not have pointer fixes.
N=60,M=9
Setup connection failed
$stopMserver
$startMserver
Sequential
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
N=1, M=60
13895 lafanasi 20 0 899m 152m 7924 S 0 0.8 9:18.75 Mserver
N=1, M=200
13895 lafanasi 20 0 930m 181m 7924 S 1 0.9 20:46.68 Mserver
N=1, M=200
13895 lafanasi 20 0 930m 181m 7924 S 2 0.9 39:15.99 Mserver
* Pathfinder Stable version
Multithreaded
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
N=60,M=1
20370 ilps_bg 20 0 3783m 430m 9084 S 2 2.1 126:07.23 Mserver
N=60,M=10
20370 ilps_bg 20 0 8377m 889m 9092 S 1 4.4 133:33.95 Mserver
N=60,M=20
20370 ilps_bg 20 0 17.1g 1.7g 9092 S 2 8.4 147:48.97 Mserver
N=60,M=100
20370 ilps_bg 20 0 62.4g 5.7g 9092 S 2 28.8 223:33.26 Mserver
N=60,M=200
20370 ilps_bg 20 0 153g 13g 9092 S 2 69.6 373:01.82 Mserver
N=60,M=200
Server crash
Setup connection failed
MAPI = monetdb@localhost:50100
ACTION= read_line
QUERY = MAPI = monetdb@localhost:50100
Sequential
N=1,M=60
19694 ilps_bg 20 0 922m 418m 10m S 0 2.1 0:27.42 Mserver
N=1,M=200
19694 ilps_bg 20 0 926m 422m 10m S 2 2.1 1:52.17 Mserver
Machine name:ZOOKST4
OS: Linux, 2.6.24.3-50.fc8
Mem: 19GB
Compiler: gcc 4.1.2
Parser tools: ?
autoconf (GNU Autoconf) 2.61
automake (GNU automake) 1.10
ltmain.sh (GNU libtool) 1.5.24
## Comment 11238
Date: 2009-03-12 12:39:25 +0100
From: Loredana Afanasiev <<lafanasi>>
btw,
<collection updatable="false" size="120 MiB" numDocs="27946">MotiesTweedeKamer</collection>
## Comment 11239
Date: 2009-04-17 23:53:18 +0200
From: @peterboncz
Mserver creates a new thread for each new entering request (to a certain limit)
with 60 concurrent requests you will get 60 threads, which execute the query.
Mserver until a few weeks ago in Linux used the normal globc ptmalloc() library for much of its work. However, this library tends to create a different memory arena for each different thread, and tends to cause huge fragmentation. That is what you were observing.
To reduce memory pressure, indepently from this report, we already changed over to the direct use of anonymous mmap (vmalloc) for much of the BAT requests. This means that memory pressure on malloc() is now much less. Therefore, this issue has disappeared by itself.
However, when re-running your query scrip, I actually got quite a few crashes, as I was easily able to overwhelm Mserver with too many threads. I fixed this (in HEAD) and now it does not crash anymore. However, under overload, mclient might produce an error in trying to connect with a server. This is a fact of life (deinal of service), though Mserver could theoretically be made to be much more resilient against this.
## Comment 11240
Date: 2009-04-17 23:54:20 +0200
From: @peterboncz
Ah, the BBPdecref error you got was also fixed by a recent bug reported by Wouter (BBPtrim would unload logical views)
## Comment 11241
Date: 2009-04-18 11:06:43 +0200
From: @drstmane
re-opened to remind us that we should consider adding a test,
or at least give a reason why not test can be added.
## Comment 11242
Date: 2009-04-18 18:30:35 +0200
From: @peterboncz
The test you propose is almost impossible. First, this dataset is private. But you could do this ony any dataset. However, large datasets and the testweb do not go well inthe first place. More seriously, the issue here was memory fragmentation in a muklti-threaded malloc() implementation. There is no real system-independent way to measure RSS, and even if you had one, it would e hard to tune, because the RSS used by MonetDB varies by the OS and compile settings,a nd also as MonetDB matures (or ages).
closing
## Comment 11243
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2683759 at http://sourceforge.net/support/tracker.php?aid=2683759
| PF:memory leak when fireing multiple simultaneous clients | https://api.github.com/repos/MonetDB/MonetDB/issues/1999/comments | 0 | 2020-11-30T10:12:30Z | 2024-06-27T11:35:31Z | https://github.com/MonetDB/MonetDB/issues/1999 | 753,342,667 | 1,999 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-10 05:26:38 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-03-13 05:51:08 +0100
## Comment 11233
Date: 2009-03-10 17:26:38 +0100
From: Jens Oehlschlägel <<jens_oehl>>
NOTE: relates to RequestIDs 2679457 and 2679434
Niels,
The following query returns a row with NULLs instead of an empty result set. This was my entry point to the tri-boolean investigation.
Stefan,
please put the problem and its workaround into our autotest repository
Cheers
Jens
sql>-- autotest 93 tri-boolean problem
0 tuples
sql>SELECT sum(DT_VOLUME) as volume, sum(DT_D00) as vStart, sum(DT_C01_01) as VB01, sum(DT_C02_01) as VB02, sum(DT_C03_0
1) as VB03, sum(DT_C04_01) as VB04, sum(DT_C05_01) as VB05 FROM voc.q_SourceExplorer WHERE (DT_CURR='USD') AND (DT_UOM=
'kg') AND ( (PostingYear=2006) AND (PostingWeek=8) )
more>HAVING sum(DT_VOLUME) > 0
more>;
+----------+----------+----------+----------+----------+----------+-----------+
| volume | vstart | vb01 | vb02 | vb03 | vb04 | vb05 |
+==========+==========+==========+==========+==========+==========+===========+
| null | null | null | null | null | null | null |
+----------+----------+----------+----------+----------+----------+-----------+
1 tuple
sql>
0 tuples
sql>-- autotest 94 tri-boolean workaround
0 tuples
sql>SELECT sum(DT_VOLUME) as volume, sum(DT_D00) as vStart, sum(DT_C01_01) as VB01, sum(DT_C02_01) as VB02, sum(DT_C03_0
1) as VB03, sum(DT_C04_01) as VB04, sum(DT_C05_01) as VB05 FROM voc.q_SourceExplorer WHERE (DT_CURR='USD') AND (DT_UOM=
'kg') AND ( (PostingYear=2006) AND (PostingWeek=8) )
more>HAVING sum(DT_VOLUME) IS NOT NULL
more> AND sum(DT_VOLUME) > 0
more>;
!relational query without result
0 tuples
## Comment 11234
Date: 2009-03-12 18:55:53 +0100
From: @drstmane
added autotest_93 & autotest_94.
both fail as reported.
## Comment 11235
Date: 2009-03-13 17:51:08 +0100
From: @drstmane
Fixed by Niels in Feb2009 CVS branch.
autotest_93 & autotest_94 do work fine, now.
## Comment 11236
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2679525 at http://sourceforge.net/support/tracker.php?aid=2679525
| HAVING returns row with NULLs instead of empty result set | https://api.github.com/repos/MonetDB/MonetDB/issues/1998/comments | 0 | 2020-11-30T10:12:27Z | 2024-06-27T11:35:30Z | https://github.com/MonetDB/MonetDB/issues/1998 | 753,342,626 | 1,998 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-10 05:05:18 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-07-29 05:13:58 +0200
## Comment 11229
Date: 2009-03-10 17:05:18 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Sorry,
My worst bug-report ever: no context, no replication instructions, but probably true.
Jens
## Comment 11230
Date: 2009-03-19 10:16:43 +0100
From: @sjoerdmullender
We compile the whole suite with Microsoft Visual Studio 2005 (aka 8). If we compile with 2008 (9.0) the installation seemingly works correctly. Compiling with 2008 does have other disadvantages. All third party libraries that we use will need to be recompiled. For most we use precompiled versions which were all compiled using 2005. If we switch to 2008, we will need to use versions compiled by ourselves. Also, we loose (at least until we figured out a solution) the PHP, Python, and Perl interfaces (at least the ones that rely on compiled code).
I have tried a 2008 compiled version and I was able to install on Vista 32 (the only Vista I have available). I haven't tried whether the installed driver actually works on Vista. It does work on XP.
## Comment 11231
Date: 2009-07-29 17:12:53 +0200
From: @sjoerdmullender
We switched over to compiling with Visual Studio 2008 and the ODBC driver now does install on Vista.
## Comment 11232
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2679457 at http://sourceforge.net/support/tracker.php?aid=2679457
| ODBC installation fails under Vista 32 and 64 | https://api.github.com/repos/MonetDB/MonetDB/issues/1997/comments | 0 | 2020-11-30T10:12:23Z | 2024-06-27T11:35:29Z | https://github.com/MonetDB/MonetDB/issues/1997 | 753,342,580 | 1,997 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-10 04:58:14 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-11-13 06:09:43 +0100
## Comment 11225
Date: 2009-03-10 16:58:14 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Dear all,
I found a couple of inconsistencies (guess bugs) around tri-boolean evaluations (involving NULL, or more precisely UNKNOWN).
1) NULL arithmetically compared should always give NULL, and in bi-boolean decisions like WHERE or HAVING conditions NULL should always be mapped to FALSE, i.e. dropping the rows. At least in combination with subquerying this is not the case.
2) NULL logically compared should be propagated using tri-boolean logic. It is not.
-- A greek seer says: if an operator is given a null operand, the result is always null. The only operator that does not follow this rule is concatenation (||).
-- A big blue Gaul says: if any operand determines the result (like TRUE OR something is TRUE) then the result is NOT NULL
-- SQL92 defines tri-booleans
<truth value> ::=
TRUE
| FALSE
| UNKNOWN
-- and says
"A null value is an implementation-dependent special value that is distinct from all non-null values of the associated data type. There is effectively only one null value and that value is a member of every SQL data type. There is no <literal> for a null value, although the keyword NULL is used in some places to indicate that a null value is desired."
-- The truth tables in the SQL92 standard are hardly readable, but the intention is clearly aiming on tri-boolean: (TRUE OR UNKNOWN) = TRUE
Cheers
Jens
MonetDB server v5.10.1 (32-bit), based on kernel v1.28.1 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11226
Date: 2009-03-17 13:04:55 +0100
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/TribooleanFailureWithSubquery.SF-2679434.*
Everything appears to work fine, now,
except that
TRUE or NULL => NULL (instead of TRUE)
NULL or TRUE => NULL (instead of TRUE)
FALSE and NULL => NULL (instead of FALSE)
NULL and FALSE => NULL (instead of FALSE)
However, while not totally complying with tri-boolean logic,
the behavior as such is consistent.
## Comment 11227
Date: 2009-11-13 18:09:43 +0100
From: @drstmane
Fixed in Nov2009 branch:
Sjoerd fixed the tri-boolean implementation in batcalc.mx
## Comment 11228
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2679434 at http://sourceforge.net/support/tracker.php?aid=2679434
| SQL:tri-boolean problems with NULL | https://api.github.com/repos/MonetDB/MonetDB/issues/1996/comments | 0 | 2020-11-30T10:12:20Z | 2024-06-27T11:35:28Z | https://github.com/MonetDB/MonetDB/issues/1996 | 753,342,534 | 1,996 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-10 12:44:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-03-13 05:50:13 +0100
## Comment 11222
Date: 2009-03-10 12:44:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
sql>-- aparently correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE b='x'
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>-- WRONG
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE b<>'x'
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>-- WRONG
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE b = 'y'
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE NOT b='x'
more>;
0 tuples
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE NOT b<>'x'
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE NOT b = 'y'
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE b IN ('x')
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE b IN ('y')
more>;
0 tuples
sql>
0 tuples
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE NOT b IN ('x')
more>;
0 tuples
sql>
0 tuples
sql>-- correct
0 tuples
sql>SELECT a, b
more>FROM (select 1 AS a, 'x' AS b) sub
more>WHERE NOT b IN ('y')
more>;
+---+---+
| a | b |
+===+===+
| 1 | x |
+---+---+
1 tuple
MonetDB server v5.10.1 (32-bit), based on kernel v1.28.1 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11223
Date: 2009-03-13 17:50:13 +0100
From: @drstmane
Fixed by Niels in Feb2009 CVS branch.
Test added by Niels in sql/src/test/BugTracker-2009/Tests/not_equal.SF-2678502.sql
## Comment 11224
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2678502 at http://sourceforge.net/support/tracker.php?aid=2678502
| Scary: (not)equal evaluated wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1995/comments | 0 | 2020-11-30T10:12:17Z | 2024-06-27T11:35:27Z | https://github.com/MonetDB/MonetDB/issues/1995 | 753,342,503 | 1,995 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-07 02:04:58 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-04-20 09:44:18 +0200
## Comment 11219
Date: 2009-03-07 14:04:58 +0100
From: @skinkie
Deleting sequences by delete from sequences; has undefined results:
create sequence test as integer;
select * from sequences;
select * from test;
delete from sequences;
select * from sequences;
select * from test;
Test thus still exists; I see another sequence that isn't selectable, but cannot be recreated again.
## Comment 11220
Date: 2009-04-20 21:44:18 +0200
From: @njnes
admin's are supposed to correctly use create/drop statements.
## Comment 11221
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2671463 at http://sourceforge.net/support/tracker.php?aid=2671463
| delete from sequences does not delete it | https://api.github.com/repos/MonetDB/MonetDB/issues/1994/comments | 0 | 2020-11-30T10:12:13Z | 2024-06-28T13:27:01Z | https://github.com/MonetDB/MonetDB/issues/1994 | 753,342,461 | 1,994 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-07 01:45:36 +0100
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2010-08-31 10:07:54 +0200
## Comment 11210
Date: 2009-03-07 13:45:36 +0100
From: @skinkie
Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7f2003f8b700 (LWP 3884)]
> 0x00007f1ffe318ea4 in mapi_seek_row (hdl=0x330c140, rownr=1, whence=0)
> at ../../../src/mapilib/Mapi.mx:4178
> 4178 if (rownr > result->row_count && hdl->mid->active &&
> read_into_
> ache(hdl->mid->active, 0) != MOK)
> (gdb) bt
> 0 0x00007f1ffe318ea4 in mapi_seek_row (hdl=0x330c140, rownr=1, whence=0)
> at ../../../src/mapilib/Mapi.mx:4178
> 1 0x00007f1ffe542757 in SQLFetch_ (stmt=0x330c090)
> at ../../../../src/odbc/driver/SQLFetch.c:65
> 2 0x00007f1ffe542cfa in SQLFetch (hStmt=0x330c090)
> at ../../../../src/odbc/driver/SQLFetch.c:194
Did not find out yet what query it triggers.
## Comment 11211
Date: 2009-03-07 14:40:58 +0100
From: @skinkie
I have reduced the problem to the following lines within phpBB;
while ($row = $db->sql_fetchrow($result))
{
$search->index('post', $row['post_id'], $row['post_text'], $row['post_subject'], $row['poster_id'], $row['forum_id']);
}
As you can see in the output the last function that 'works' is the DELETE; That is equal to the final function in the index function. If I place an exit; direct after the index function, everything works as expected. The problem seems to be the next fetch row in the iteration.
## Comment 11212
Date: 2009-03-07 16:44:10 +0100
From: @skinkie
I also thing I found the problem in Mapi.mx
That one seems perfectly fine;
if (rownr < 0 || rownr > result->row_count)
return mapi_setError(hdl->mid, "Illegal row number", "mapi_seek_row", MERROR);
One line above it:
if (rownr > result->row_count && hdl->mid->active && read_into_cache(hdl->mid->active, 0) != MOK)
return MERROR;
Now how is it possible that the requested row number is HIGHER than the amount of rows in our result? It doesn't make any sense. Now I have solved my bug by changing > to <=; but after review the code why not swap the lines around, and remove the comparison at all?
if (rownr < 0 || rownr > result->row_count)
return mapi_setError(hdl->mid, "Illegal row number", "mapi_seek_row", MERROR);
if (hdl->mid->active && read_into_cache(hdl->mid->active, 0) != MOK)
return MERROR;
## Comment 11213
Date: 2009-03-09 12:17:56 +0100
From: @skinkie
0x00007f5a9582eea4 in mapi_seek_row (hdl=0x13b54d0, rownr=1, whence=0) at ../../../src/mapilib/Mapi.mx:4178
4178 if (rownr > result->row_count && hdl->mid->active && read_into_cache(hdl->mid->active, 0) != MOK)
(gdb) print *result
Cannot access memory at address 0x0
(gdb) bt
0 0x00007f5a9582eea4 in mapi_seek_row (hdl=0x13b54d0, rownr=1, whence=0) at ../../../src/mapilib/Mapi.mx:4178
1 0x00007f5a95a58757 in SQLFetch_ (stmt=0x13b5420) at ../../../../src/odbc/driver/SQLFetch.c:65
2 0x00007f5a95a58cfa in SQLFetch (hStmt=0x13b5420) at ../../../../src/odbc/driver/SQLFetch.c:194
3 0x00007f5a975ed41b in SQLFetch () from /usr/lib/libodbc.so.1
4 0x0000000000524490 in ?? ()
5 0x00000000006536fd in ?? ()
6 0x000000000063eefc in execute ()
7 0x0000000000653016 in ?? ()
8 0x000000000063eefc in execute ()
9 0x0000000000653016 in ?? ()
10 0x000000000063eefc in execute ()
11 0x0000000000653016 in ?? ()
12 0x000000000063eefc in execute ()
13 0x0000000000653016 in ?? ()
14 0x000000000063eefc in execute ()
15 0x000000000061be0b in zend_execute_scripts ()
16 0x00000000005d85aa in php_execute_script ()
17 0x0000000000691a45 in main ()
## Comment 11214
Date: 2009-03-09 12:19:28 +0100
From: @skinkie
(gdb) print *hdl
$1 = {mid = 0x13a5110, template = 0x0,
query = 0x13b6ef0 "SELECT post_id, post_subject, post_text, poster_id, forum_id\n\t\t\tFROM phpbb_posts", maxbindings = 0,
bindings = 0x0, maxparams = 0, params = 0x0, result = 0x0, active = 0x0, lastresult = 0x0, needmore = 0, pending_close = 0x0,
npending_close = 0, prev = 0x13b81e0, next = 0x0}
## Comment 11215
Date: 2009-03-09 12:27:31 +0100
From: @skinkie
(gdb) bt
0 0x00007faee2200ea4 in mapi_seek_row (hdl=0x229fc90, rownr=1, whence=0) at ../../../src/mapilib/Mapi.mx:4178
1 0x00007faee242a757 in SQLFetch_ (stmt=0x229fbe0) at ../../../../src/odbc/driver/SQLFetch.c:65
2 0x00007faee242acfa in SQLFetch (hStmt=0x229fbe0) at ../../../../src/odbc/driver/SQLFetch.c:194
3 0x00007faee3d0d41b in SQLFetch () from /usr/lib/libodbc.so.1
4 0x00000000004bf649 in php_odbc_fetch_hash (ht=<value optimized out>, return_value=0x23077b8,
return_value_ptr=<value optimized out>, this_ptr=<value optimized out>, return_value_used=<value optimized out>, result_type=2)
at /mnt/dv/skinkie/php-5.2.8/ext/odbc/php_odbc.c:1449
5 0x00000000006741c9 in zend_do_fcall_common_helper_SPEC (execute_data=0x7fffecc5f4f0)
at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:200
6 0x000000000065fe74 in execute (op_array=0x2226c38) at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:92
7 0x0000000000673b6d in zend_do_fcall_common_helper_SPEC (execute_data=0x7fffecc60520)
at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:234
8 0x000000000065fe74 in execute (op_array=0x7faee2f99fc8) at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:92
9 0x0000000000673b6d in zend_do_fcall_common_helper_SPEC (execute_data=0x7fffecc60e90)
at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:234
10 0x000000000065fe74 in execute (op_array=0x213d0a8) at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:92
11 0x0000000000673b6d in zend_do_fcall_common_helper_SPEC (execute_data=0x7fffecc61460)
at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:234
12 0x000000000065fe74 in execute (op_array=0x1c7a1f0) at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:92
13 0x0000000000673b6d in zend_do_fcall_common_helper_SPEC (execute_data=0x7fffecc63f10)
at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:234
14 0x000000000065fe74 in execute (op_array=0x1c6b038) at /mnt/dv/skinkie/php-5.2.8/Zend/zend_vm_execute.h:92
15 0x000000000063d671 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /mnt/dv/skinkie/php-5.2.8/Zend/zend.c:1134
16 0x00000000005fb94d in php_execute_script (primary_file=0x7fffecc68660) at /mnt/dv/skinkie/php-5.2.8/main/main.c:2023
17 0x00000000006b1397 in main (argc=3, argv=0x7fffecc68858) at /mnt/dv/skinkie/php-5.2.8/sapi/cgi/cgi_main.c:1989
## Comment 11216
Date: 2009-03-09 14:26:49 +0100
From: @skinkie
Index: clients/src/mapilib/Mapi.mx
===================================================================
RCS file: /cvsroot/monetdb/clients/src/mapilib/Mapi.mx,v
retrieving revision 1.49.2.2
diff --unified -p -r1.49.2.2 Mapi.mx
--- clients/src/mapilib/Mapi.mx 5 Mar 2009 14:40:47 -0000 1.49.2.2
+++ clients/src/mapilib/Mapi.mx 9 Mar 2009 11:51:03 -0000
@@ -4111,7 +4111,7 @@ mapi_cache_limit(Mapi mid, int limit)
MapiHdl hdl;
if (mid->active)
- finish_handle(mid->active);
+ read_into_cache(mid->active, 0);
if (mid->tracelog) {
mapi_log_header(mid, "W");
Works for me.
## Comment 11217
Date: 2009-03-10 09:37:09 +0100
From: @sjoerdmullender
Bug is fixed. I need to think about a test.
## Comment 11218
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2671445 at http://sourceforge.net/support/tracker.php?aid=2671445
## Comment 14866
Date: 2010-08-31 10:07:54 +0200
From: @sjoerdmullender
Fixed a long time ago. Can't come up with a test.
| Mapi read error when rows exceed maximum | https://api.github.com/repos/MonetDB/MonetDB/issues/1993/comments | 0 | 2020-11-30T10:12:09Z | 2024-06-27T11:35:25Z | https://github.com/MonetDB/MonetDB/issues/1993 | 753,342,413 | 1,993 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-06 03:30:11 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-04-17 09:03:59 +0200
## Comment 11195
Date: 2009-03-06 15:30:11 +0100
From: Jan Rittinger <<jan.rittinger>>
The following query returns the wrong number:
count(doc("consumer04.xml")//properties/../properties)
The reason is the parent step implementation (loop_lifted_parent_step) that makes some assumptions that are not true (see following example).
If I run the following query with debug mask 10 I get a warning:
> echo 'count(doc("consumer04.xml")//properties/..)' | pf | Mserver --debug=10
BATpropcheck: BAT tmpr_2464(-1332)[oid,oid] with 1156921 tuples was incorrectly marked sorted!
BATpropcheck: BAT tmpr_2464(-1332)[oid,oid] with 1156921 tuples remains marked radix-clustered on 32 bits; not checked!
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>1156921</XQueryResult>
The document consumer04.xml is linked in the XIRAF testset in the pathfinder wiki.
## Comment 11196
Date: 2009-03-12 19:13:09 +0100
From: @drstmane
I assume, that it is not the properties that are set incorrectly --- the result of PFll_parent is supposed to be ordered on [iter,pre], i.e., with only one iter this also means that it is sorted in pre --- hence, I suspect that either the ll_upwards implementation itself is wrong in this case, since is produces an obviously not sorted pre column, or is is working on inconsistent data/input due to a previous bug elsewhere, and hence, works incorrectly ...
... also getting Peter as original author of the ll_upwards code involved ...
## Comment 11197
Date: 2009-03-17 09:26:32 +0100
From: Maurice van Keulen <<mvankeulen>>
Just to be sure, backward axes need to produce their results in REVERSE document order. So I expect the result of PFll_parent to be first ordered on iter and then descending on pre.
## Comment 11198
Date: 2009-03-17 09:42:08 +0100
From: Jan Rittinger <<jan.rittinger>>
Maurice, you are wrong here---all steps are supposed to return their result in document order.
Reverse document order only plays a role in positional predicates, please read http://www.w3.org/TR/xquery/dt-predicate.
## Comment 11199
Date: 2009-03-17 09:53:58 +0100
From: Maurice van Keulen <<mvankeulen>>
You're right. I keep being amazed about some parts of the language design. I understand the logic behind it, but for me, it is quite counter-intuitive that preceding::foo[1] and (preceding::foo)[1] count the foo-elements in opposing directions.
## Comment 11200
Date: 2009-03-17 12:47:50 +0100
From: @drstmane
Added test in pathfinder/tests/BugTracker/Tests/parent_wrong_properties.SF-2668437.*
Fails with property error as reported.
When the sortedness property is not set
(i.e., removing "bn->tsorted = GDK_SORTED"
from pathfinder/runtime/ll_upwards.mx),
it seems to work fine --- at least there is
not property error any more --- the result
still need to be checked/verified.
However, I'm not sure whether not setting
the sortedness property is the correct solution,
since I still expect ll_parent to produce a result
with the tail values (pre/item) sorted per iter,
i.e., globally sorted with only one iter.
## Comment 11201
Date: 2009-03-19 20:20:11 +0100
From: @drstmane
With only 1 iter, the item's/pre's in the result should be sorted,
but they are apparently not.
Not setting the sortedness property seems to avoid
the reported property error
without harming any (other) Pathfinder/XQuery tests;
and seems to make all Xiraf test queries work.
Hence, I disable setting the tail-sorted property
of the ll_upwards results in the Feb2009 release branch,
but prevent propagation to the development trunk,
as I am not convinced that this is the proper fix.
Rather, we should check, why the result is not sorted
as we expect it to be ...
## Comment 11202
Date: 2009-04-16 13:20:16 +0200
From: @peterboncz
the algorithm produces parent nodes in the order of the context nodes.
it used to propagate ordering on the context into the result if the step was not loop-lifted.
however, if the context sequence contains nodes from different depths, this is simply incorrect.
e.g. <a x="1"><a x="2"><b x="3"/></a><b x="4"/></a>//a/../@x
has context sequence (<b x="3"/>,<b x="4"/>) and generates ("2","1")
## Comment 11203
Date: 2009-04-16 14:24:34 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Peter,
I think I do not understand your example (as the result of your query is 'x="1"') and I do not understand the 'solution'.
Up till now the assumption was that calling loop_lifted_parent_step() consumes the input in either iter|item or item|iter order and produces the result in iter|item or item|iter order based on the order flag. Do you now say that this assumption is false?
## Comment 11204
Date: 2009-04-16 14:39:52 +0200
From: @peterboncz
sure, typo in the example (//b) you should have seen that:
e.g. <a x="1"><a x="2"><b x="3"/></a><b x="4"/></a>//b/../@x
has context sequence (<b x="3"/>,<b x="4"/>) and generates ("2","1")
ll_upwards always demands item input order.
- the anc and anc-or-self produce iter|item order
- parent never did that, it produces parents in the same order as the input items, only with duplicates (in the same iter) eleminated. It wronly assumed that if there was only one iter, the input item being sorted, the output parents would also be sorted.
there is no contract that results are to be produced in a particular order, IMHO.
I think this is fixed. Please close if you agree.
## Comment 11205
Date: 2009-04-16 15:36:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Peter, thanks for the explanation.
Re-assigning to Stefan to answer the question about the correct semantics of the order flag. If the internal order is hidden correctly I'm confident that the bug is fixed :)
## Comment 11206
Date: 2009-04-17 18:19:10 +0200
From: @drstmane
As far as I can tell from looking at the sources, the order flag is indeed handled as intended.
Re-assigning to Jan to verify that the test now produces the correct result for the original query, i.e., 17291; cf., e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/parent_wrong_properties.SF-2668437.out.00.html
If so, we can clean-up the stable output and close this bug report, since also the Xiraf tests now appear to work fine; cf.,
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/index_short.html
(well, assuming their yet unconfirmed stable output is indeed correct ...)
## Comment 11207
Date: 2009-04-17 18:19:42 +0200
From: @drstmane
as said: assigning to Jan.
## Comment 11208
Date: 2009-04-17 21:03:59 +0200
From: Jan Rittinger <<jan.rittinger>>
Result looks good. Closing the bug again.
## Comment 11209
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2668437 at http://sourceforge.net/support/tracker.php?aid=2668437
| PF runtime: parent step produces not/wrongly sorted result | https://api.github.com/repos/MonetDB/MonetDB/issues/1992/comments | 0 | 2020-11-30T10:12:06Z | 2024-06-27T11:35:24Z | https://github.com/MonetDB/MonetDB/issues/1992 | 753,342,371 | 1,992 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-05 09:26:27 +0100
From: Jan Flokstra <<jflokstra>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 12:02:28 +0200
## Comment 11191
Date: 2009-03-05 09:26:27 +0100
From: Jan Flokstra <<jflokstra>>
When the argument to fn:collection() is non existent patthfinder return the empty sequence. I think this is incorrect. In the specs (http://www.w3.org/TR/xpath-functions/func-collection) the part on resolving the name of the collection says:
This function takes an xs:string as argument and returns a sequence of nodes obtained by interpreting $arg as an xs:anyURI and resolving it according to the mapping specified in Available collections described in Section C.2 Dynamic Context ComponentsXP. If Available collections provides a mapping from this string to a sequence of nodes, the function returns that sequence. If Available collections maps the string to an empty sequence, then the function returns an empty sequence. If Available collections provides no mapping for the string, an error is raised [err:FODC0004].
So in my opinion an error should be generated. We had a couple of cases where an error would have been very handy for the user to find errors in queries.
JanF.
## Comment 11192
Date: 2009-04-07 12:02:28 +0200
From: @peterboncz
fixed in head
## Comment 11193
Date: 2009-04-07 13:17:49 +0200
From: @drstmane
- added test in pathfinder/tests/BugTracker/Tests/fn-collection_DOES-NOT-EXIST.SF-2664405.* (CVS HEAD)
works as expected, i.e., an error is generated
- complete administration
## Comment 11194
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2664405 at http://sourceforge.net/support/tracker.php?aid=2664405
| fn:collection("DOES-NOT-EXIST") does not fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1991/comments | 0 | 2020-11-30T10:12:03Z | 2024-06-27T11:35:23Z | https://github.com/MonetDB/MonetDB/issues/1991 | 753,342,340 | 1,991 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-03 07:06:40 +0100
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-03-04 10:31:17 +0100
## Comment 11188
Date: 2009-03-03 19:06:40 +0100
From: @swingbit
I'm not completely sure what SQL standard says here:
when we have
INSERT INTO mytable
SELECT .... ORDER BY a
are mytable's tuples supposed to be stored in a's order?
I would expect so, but on the other hand I wouldn't be surprised if the standard didn't enforce that.
Anyway, currently the INSERT INTO seems to ignore the ORDER BY. Little test follows:
create table unsorted (n int);
insert into unsorted values (2);
insert into unsorted values (1);
insert into unsorted values (4);
insert into unsorted values (3);
insert into unsorted values (5);
create table sorted (n int);
insert into sorted
select * from unsorted
order by n;
sql>select * from unsorted;
+---+
| n |
+===+
| 2 |
| 1 |
| 4 |
| 3 |
| 5 |
+---+
5 tuples
sql>select * from sorted;
+---+
| n |
+===+
| 2 |
| 1 |
| 4 |
| 3 |
| 5 |
+---+
5 tuples
To be really sure table "sorted" is not stored as sorted on "n":
sql>debug select * from sorted;
mdb> mdb.start();
mdb>
mdb> user.s3_1();
mdb>
mdb>barrier _49 := language.dataflow();
mdb>
mdb> _1 := sql.bind("sys","sorted","n",0);
mdb>
mdb> _6 := sql.bind("sys","sorted","n",2);
mdb>info _1
Show info for 1458
-----------------------------------------
h t name
str str type
-----------------------------------------
...
[ "tsorted", "0" ]
...
## Comment 11189
Date: 2009-03-04 22:31:17 +0100
From: @njnes
added a test to BugTrackers-2009 insert_order_by.SF-2658243.sql
fixed the bug in rel_merge_project which incorrectly merged project-order-by
## Comment 11190
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2658243 at http://sourceforge.net/support/tracker.php?aid=2658243
| SQL: INSERT INTO + ORDER BY | https://api.github.com/repos/MonetDB/MonetDB/issues/1990/comments | 0 | 2020-11-30T10:11:59Z | 2024-06-27T11:35:22Z | https://github.com/MonetDB/MonetDB/issues/1990 | 753,342,291 | 1,990 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-03 06:27:22 +0100
From: @swingbit
To: Roberto Cornacchia <<roberto.cornacchia>>
Version: -- development
Last updated: 2010-06-14 15:52:36 +0200
## Comment 11181
Date: 2009-03-03 18:27:22 +0100
From: @swingbit
So far I could not come up with a simple test that can reproduce this bug,
I will for now just describe it.
When mitosis optimizer is activated, the INSERT INTO in the query below reports that 0 tuples were inserted.
However, the SELECT alone does return 752 tuples.
Many other INSERT INTO queries in the same session work correctly, I'm trying to figure out what makes this special, but couldn't so far.
Here the active optimizers:
sql>select optimizer;
+----------------------------------------------------------------------------------------------------------------------------------------------------------+
| single_value |
+==========================================================================================================================================================+
| inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,h |
: istory,multiplex :
+----------------------------------------------------------------------------------------------------------------------------------------------------------+
1 tuple
And the query that fails:
INSERT INTO sec_references_doc (secID, docID)
SELECT secDict.secID, docDict.docID
FROM secDict, docDict, sec_string, doc_string
WHERE sec_string.attribute = 'docid'
AND doc_string.attribute = 'docid'
AND sec_string.value = doc_string.value
AND sec_string.secID = secDict.secID
AND doc_string.docID = docDict.docID
AND secDict.type = 'patcit'
GROUP BY secDict.secID, docDict.docID;
with:
sql>\d sec_references_doc
CREATE TABLE "sys"."sec_references_doc" (
"secid" int,
"docid" int,
"prob" double DEFAULT 1,
CONSTRAINT "sec_references_doc_docid_fkey" FOREIGN KEY ("docid") REFERENCES "docdict" ("docid"),
CONSTRAINT "sec_references_doc_secid_fkey" FOREIGN KEY ("secid") REFERENCES "secdict" ("secid")
);
sql>\d secdict
CREATE TABLE "sys"."secdict" (
"secid" int NOT NULL DEFAULT next value for "sys"."seq_4215",
"sec" varchar(255),
"type" varchar(255),
"prob" double DEFAULT 1,
CONSTRAINT "secdict_secid_pkey" PRIMARY KEY ("secid")
);
sql>\d docdict
CREATE TABLE "sys"."docdict" (
"docid" int NOT NULL DEFAULT next value for "sys"."seq_4205",
"doc" varchar(255),
"type" varchar(255),
"prob" double DEFAULT 1,
CONSTRAINT "docdict_docid_pkey" PRIMARY KEY ("docid")
);
sql>\d sec_string
CREATE TABLE "sys"."sec_string" (
"secid" int,
"attribute" varchar(255),
"value" varchar(255),
"prob" double DEFAULT 1,
CONSTRAINT "sec_string_secid_fkey" FOREIGN KEY ("secid") REFERENCES "secdict" ("secid")
);
sql>\d doc_string
CREATE TABLE "sys"."doc_string" (
"docid" int,
"attribute" varchar(255),
"value" varchar(255),
"prob" double DEFAULT 1,
CONSTRAINT "doc_string_docid_fkey" FOREIGN KEY ("docid") REFERENCES "docdict" ("docid")
);
## Comment 11182
Date: 2009-03-03 18:39:10 +0100
From: @mlkersten
Indeed, you walk ahead of the core team. We are currently actively testing the mitosis/mergetable/dataflow combination.
## Comment 11183
Date: 2009-03-04 10:39:46 +0100
From: @swingbit
Hope this can help. I have run the same query with different optimizer combinations.
Starting from the one relative to this bug report (default + mitosis),
then removing one optimizer at the time.
The query becomes correct (i.e. the INSERT INTO does insert tuples)
when 'aliases' is removed.
However, when trying the combination (default + mitosis - aliases), I hit an assertion.
Details below.
-- incorrect (default + mitosis)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex';
-- incorrect (garbageCollector removed)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,multiplex';
-- incorrect (joinPath removed)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,constants,commonTerms,deadcode,reduce,dataflow,history,multiplex';
-- incorrect (commonTerms removed)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,constants,deadcode,reduce,dataflow,history,multiplex';
-- incorrect (constants removed)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,deadcode,reduce,dataflow,history,multiplex';
-- incorrect (deadcode removed)
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,reduce,dataflow,history,multiplex';
-- incorrect (coercions removed)
set optimizer='inline,remap,evaluate,costModel,emptySet,mitosis,aliases,mergetable,reduce,dataflow,history,multiplex';
-- incorrect (emptySet removed)
set optimizer='inline,remap,evaluate,costModel,mitosis,aliases,mergetable,reduce,dataflow,history,multiplex';
-- CORRECT (aliases removed)
set optimizer='inline,remap,evaluate,costModel,mitosis,mergetable,reduce,dataflow,history,multiplex';
-- ASSERTION (default + mitosis - aliases): src/mal/mal_interpreter.mx:1077: DFLOWexecute: Assertion `queued || pc == limit' failed.
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,mergetable,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex';
## Comment 11184
Date: 2009-08-07 09:42:18 +0200
From: @njnes
I guess by all changes this got fixed, but I cannot test this as there is no example data available. Could you add an example query which shows the problem
## Comment 11185
Date: 2009-08-11 11:39:15 +0200
From: @drstmane
Roberto,
could you please provide some sample data that used to give incorrect result with your query and different optimizer settings?
Thanks!
## Comment 11186
Date: 2009-08-14 14:22:54 +0200
From: @swingbit
Added a data sample, smaller than the one I was experimenting with.
The query reported in the bug report is now expected to return 2 rows (instead of the 23 of the original data).
I also mark the bug as fixed, as it seems to work fine with the latest stable (Aug2009)
## Comment 11187
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2658110 at http://sourceforge.net/support/tracker.php?aid=2658110
| SQL: mitosis optimizer + insert into | https://api.github.com/repos/MonetDB/MonetDB/issues/1989/comments | 0 | 2020-11-30T10:11:56Z | 2024-06-27T11:35:21Z | https://github.com/MonetDB/MonetDB/issues/1989 | 753,342,244 | 1,989 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-03 10:43:13 +0100
From: @swingbit
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-03-03 12:57:18 +0100
## Comment 11178
Date: 2009-03-03 10:43:13 +0100
From: @swingbit
This bug seems to be related to http://sourceforge.net/support/tracker.php?aid=2654300, which is now fixed in CVS. However, the fix doesn't solve the problem below:
drop table x cascade;
drop table y cascade;
create table x (id int);
insert into x (id) values (1);
insert into x (id) values (2);
insert into x (id) values (3);
create table y (n int, s varchar(10));
insert into y (n,s) values (1, 'one');
insert into y (n,s) values (2, 'two');
insert into y (n,s) values (3, 'three');
create view yv as select s as a1, n as a2 from y;
create view j as select yv.a2 as a1, yv.a1 as a2 from x,yv where x.id = yv.a2;
select * from j where a2='y-three';
drop table x cascade;
drop table y cascade;
Output:
MAPI = monetdb@localhost:50000
QUERY = select * from j where a2='y-three';
ERROR = !TypeException:user.s0_1[13]:'algebra.uselect' undefined in: _22:any := algebra.uselect(_17:bat[:oid,:str], _21:int)
!TypeException:user.s0_1[15]:'algebra.kdifference' undefined in: _24:any := algebra.kdifference(_22:any, _23:bat[:oid,:str])
!TypeException:user.s0_1[16]:'algebra.uselect' undefined in: _25:any := algebra.uselect(_23:bat[:oid,:str], _21:int)
!TypeException:user.s0_1[17]:'algebra.kunion' undefined in: _26:any := algebra.kunion(_24:any, _25:any)
!TypeException:user.s0_1[19]:'algebra.uselect' undefined in: _28:any := algebra.uselect(_27:bat[:oid,:str], _21:int)
!TypeException:user.s0_1[20]:'algebra.kunion' undefined in: _29:any := algebra.kunion(_26:any, _28:any)
!TypeException:user.s0_1[23]:'algebra.kdifference' undefined in: _32:any := algebra.kdifference(_29:any, _31:bat[:oid,:oid])
!TypeException:user.s0_1[25]:'algebra.markT' undefined in: _35:any := algebra.markT(_32:any, _33:oid)
!TypeException:user.s0_1[26]:'bat.reverse' undefined in: _36:any := bat.reverse(_35:any)
!TypeException:user.s0_1[33]:'algebra.join' undefined in: _48:any := algebra.join(_36:any, _47:bat[:oid,:int])
!TypeException:user.s0_1[34]:'bat.reverse' undefined in: _49:any := bat.reverse(_48:any)
!TypeException:user.s0_1[35]:'algebra.join' undefined in: _50:any := algebra.join(_16:bat[:oid,:int], _49:any)
!TypeException:user.s0_1[36]:'bat.reverse' undefined in: _51:any := bat.reverse(_50:any)
!TypeException:user.s0_1[38]:'algebra.markT' undefined in: _53:any := algebra.markT(_51:any, _52:oid)
!TypeException:user.s0_1[39]:'bat.reverse' undefined in: _54:any := bat.reverse(_53:any)
!TypeException:user.s0_1[40]:'algebra.join' undefined in: _55:any := algebra.join(_54:any, _48:any)
!TypeException:user.s0_1[44]:'algebra.join' undefined in: _59:any := algebra.join(_36:any, _58:bat[:oid,:str])
!TypeException:user.s0_1[45]:'algebra.join' undefined in: _60:any := algebra.join(_54:any, _59:any)
!SQLException:int:conversion of string 'y-three' failed
## Comment 11179
Date: 2009-03-03 12:57:18 +0100
From: @njnes
fixed and test added to BugTracker-2009 / lookup_column_name_bug_2.SF-2656762.sql
The lookup of column names (with table name and column) went wrong (looked at current projection, while it should
look at the parent)
## Comment 11180
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2656762 at http://sourceforge.net/support/tracker.php?aid=2656762
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Views with select on top of join - attribute lookup problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1988/comments | 0 | 2020-11-30T10:11:52Z | 2024-06-27T11:35:20Z | https://github.com/MonetDB/MonetDB/issues/1988 | 753,342,195 | 1,988 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 06:12:49 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: clients devs <<bugs-clients>>
Version: 1.40.1 (Oct2010) [obsolete]
CC: sellam
Last updated: 2012-11-27 16:20:04 +0100
## Comment 11176
Date: 2009-03-02 18:12:49 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Stefan,
Sjoerd,
Yet another reminder on a wishlist item: so far most tests bypass the ODBC (and JDBC) driver. Would be great to have end-to-end testing also covering the ODBC-driver as a potential source of error (say at least before each release).
Another potential 'leak' in the test coverage - if I remember right - is the fact that our larger test scenarios are build by repeatedly using COPY INTO reading the 150k. Theoreticall this could miss a failure which only gets visible if one does user COPY INTO of everything at once.
Cheers
Jens
## Comment 11177
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654967 at http://sourceforge.net/support/tracker.php?aid=2654967
## Comment 15420
Date: 2011-01-25 14:44:05 +0100
From: @grobian
It's not clear to me what's actually requested here.
| wishlist: end-to-end testing via ODBC | https://api.github.com/repos/MonetDB/MonetDB/issues/1987/comments | 0 | 2020-11-30T10:11:49Z | 2024-06-27T11:35:19Z | https://github.com/MonetDB/MonetDB/issues/1987 | 753,342,148 | 1,987 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 06:07:17 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-08-10 11:12:24 +0200
## Comment 11172
Date: 2009-03-02 18:07:17 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Sjoerd,
Stefan,
Here a short reminder of what one could do to test/make stable dumps: setup a rather complex DB with views, functions, sequences etc. over several user schemes.
Test dump and restore of complete DB from admin user.
Test dump and restore of user schema by the schema user.
Traps to look at:
CREATE SCHEMA fixes AUTHORIZATION
but there is no
ALTER SCHEMA to change this later
Cheers
Jens
P.S. Good that the buffer thing has been fixed!
## Comment 11173
Date: 2009-08-07 10:48:25 +0200
From: @njnes
wasn't this fixed already?
## Comment 11174
Date: 2009-08-10 11:12:24 +0200
From: @sjoerdmullender
We do indeed test dump with multiple users and schemas, so I think this is indeed covered.
I think we can close this.
## Comment 11175
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654959 at http://sourceforge.net/support/tracker.php?aid=2654959
| wishlist: stable dump | https://api.github.com/repos/MonetDB/MonetDB/issues/1986/comments | 0 | 2020-11-30T10:11:45Z | 2024-06-27T11:35:18Z | https://github.com/MonetDB/MonetDB/issues/1986 | 753,342,110 | 1,986 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 05:43:50 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-11-22 10:26:53 +0100
## Comment 11169
Date: 2009-03-02 17:43:50 +0100
From: Jens Oehlschlägel <<jens_oehl>>
It would be great if SQL functions could switch the returned view/table depending on its input parameters without a performance penalty for the one-time execution of the required IF ELSE END.
Attached is the script comparing performance of different approaches to view switching that I previously sent to Sjoerd.
Cheers
Jens
## Comment 11170
Date: 2009-11-22 22:26:53 +0100
From: @njnes
optimizing imperative languages is out of the scope of the sql optimizer.
## Comment 11171
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654923 at http://sourceforge.net/support/tracker.php?aid=2654923
| wishlist: SQL functions can switch views | https://api.github.com/repos/MonetDB/MonetDB/issues/1985/comments | 0 | 2020-11-30T10:11:42Z | 2024-06-28T13:27:00Z | https://github.com/MonetDB/MonetDB/issues/1985 | 753,342,068 | 1,985 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 05:38:34 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-03-02 07:03:24 +0100
## Comment 11166
Date: 2009-03-02 17:38:34 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Hi Sjoerd,
here the reminder to which syntax Oracle uses
ALTER USER IDENTIFIED BY <password> [REPLACE <old_password>];
Cheers
Jens
## Comment 11167
Date: 2009-03-02 19:03:24 +0100
From: @grobian
duplicate of 2633848
## Comment 11168
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654909 at http://sourceforge.net/support/tracker.php?aid=2654909
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| wishlist: let users change their password via SQL | https://api.github.com/repos/MonetDB/MonetDB/issues/1984/comments | 0 | 2020-11-30T10:11:39Z | 2024-06-28T13:26:59Z | https://github.com/MonetDB/MonetDB/issues/1984 | 753,342,037 | 1,984 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 03:27:39 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2009-03-03 12:50:04 +0100
## Comment 11163
Date: 2009-03-02 15:27:39 +0100
From: @sjoerdmullender
Probably due to conflicts between Roberto's and Niels's changes, the server generates an assertion failed:
mserver5: /ufs/sjoerd/src/MonetDB/virgin/sql/src/storage/store.mx:1213: store_init: Assertion `store_oid <= 1061' failed.
Roberto's change is only on the head, and Niels's change was made on the stable and was propagated to the head.
## Comment 11164
Date: 2009-03-03 12:50:04 +0100
From: @njnes
fixed. No test needed as its tested all normal tests
## Comment 11165
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654603 at http://sourceforge.net/support/tracker.php?aid=2654603
| assertion failed in store.mx | https://api.github.com/repos/MonetDB/MonetDB/issues/1983/comments | 0 | 2020-11-30T10:11:35Z | 2024-06-27T11:35:15Z | https://github.com/MonetDB/MonetDB/issues/1983 | 753,342,001 | 1,983 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 01:33:06 +0100
From: @swingbit
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1981
Last updated: 2010-07-09 15:06:44 +0200
## Comment 11160
Date: 2009-03-02 13:33:06 +0100
From: @swingbit
[ on Feb2009 branch ]
create table x (n int, s varchar(10));
insert into x values (1, 'one');
insert into x values (2, 'two');
insert into x values (3, 'three');
-- swap the two attributes
create view x1 as
select s as a1, n as a2 from x;
-- swap them again
create view x2 as
select a2 as a1, a1 as a2 from x1;
-- select on the original 's' attribute fails
select * from x2 where a2='two';
This is the output:
$ mclient -lsql -dtest02 -G < http://sourceforge.net/support/tracker.php?aid=2.sql
[ 1 ]
[ 1 ]
[ 1 ]
MAPI = monetdb@localhost:50000
QUERY = select * from x2 where a2='two';
ERROR = !TypeException:user.s0_1[4]:'algebra.uselect' undefined in: _9:any := algebra.uselect(_2:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[6]:'algebra.kdifference' undefined in: _12:any := algebra.kdifference(_9:any, _10:bat[:oid,:str])
!TypeException:user.s0_1[7]:'algebra.uselect' undefined in: _13:any := algebra.uselect(_10:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[8]:'algebra.kunion' undefined in: _14:any := algebra.kunion(_12:any, _13:any)
!TypeException:user.s0_1[10]:'algebra.uselect' undefined in: _17:any := algebra.uselect(_15:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[11]:'algebra.kunion' undefined in: _18:any := algebra.kunion(_14:any, _17:any)
!TypeException:user.s0_1[14]:'algebra.kdifference' undefined in: _21:any := algebra.kdifference(_18:any, _20:bat[:oid,:oid])
!TypeException:user.s0_1[16]:'algebra.markT' undefined in: _24:any := algebra.markT(_21:any, _22:oid)
!TypeException:user.s0_1[17]:'bat.reverse' undefined in: _25:any := bat.reverse(_24:any)
!TypeException:user.s0_1[24]:'algebra.join' undefined in: _33:any := algebra.join(_25:any, _32:bat[:oid,:int])
!TypeException:user.s0_1[28]:'algebra.join' undefined in: _37:any := algebra.join(_25:any, _36:bat[:oid,:str])
!SQLException:int:conversion of string 'two' failed
## Comment 11161
Date: 2009-03-02 13:35:55 +0100
From: @swingbit
This report was created by mistake: duplicate of http://sourceforge.net/support/tracker.php?aid=2654300
Closing it.
## Comment 11162
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654390 at http://sourceforge.net/support/tracker.php?aid=2654390
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14319
Date: 2010-07-09 15:06:44 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1981 ***
| problem with views reusing aliases ? | https://api.github.com/repos/MonetDB/MonetDB/issues/1982/comments | 0 | 2020-11-30T10:11:32Z | 2024-06-28T13:26:58Z | https://github.com/MonetDB/MonetDB/issues/1982 | 753,341,965 | 1,982 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 12:41:25 +0100
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2010-07-09 15:06:44 +0200
## Comment 11157
Date: 2009-03-02 12:41:25 +0100
From: @swingbit
[ on Feb2009 branch ]
create table x (n int, s varchar(10));
insert into x values (1, 'one');
insert into x values (2, 'two');
insert into x values (3, 'three');
-- swap the two attributes
create view x1 as
select s as a1, n as a2 from x;
-- swap them again
create view x2 as
select a2 as a1, a1 as a2 from x1;
-- select on the original 's' attribute fails
select * from x2 where a2='two';
This is the output:
$ mclient -lsql -dtest02 -G < http://sourceforge.net/support/tracker.php?aid=2.sql
[ 1 ]
[ 1 ]
[ 1 ]
MAPI = monetdb@localhost:50000
QUERY = select * from x2 where a2='two';
ERROR = !TypeException:user.s0_1[4]:'algebra.uselect' undefined in: _9:any := algebra.uselect(_2:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[6]:'algebra.kdifference' undefined in: _12:any := algebra.kdifference(_9:any, _10:bat[:oid,:str])
!TypeException:user.s0_1[7]:'algebra.uselect' undefined in: _13:any := algebra.uselect(_10:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[8]:'algebra.kunion' undefined in: _14:any := algebra.kunion(_12:any, _13:any)
!TypeException:user.s0_1[10]:'algebra.uselect' undefined in: _17:any := algebra.uselect(_15:bat[:oid,:str], _8:int)
!TypeException:user.s0_1[11]:'algebra.kunion' undefined in: _18:any := algebra.kunion(_14:any, _17:any)
!TypeException:user.s0_1[14]:'algebra.kdifference' undefined in: _21:any := algebra.kdifference(_18:any, _20:bat[:oid,:oid])
!TypeException:user.s0_1[16]:'algebra.markT' undefined in: _24:any := algebra.markT(_21:any, _22:oid)
!TypeException:user.s0_1[17]:'bat.reverse' undefined in: _25:any := bat.reverse(_24:any)
!TypeException:user.s0_1[24]:'algebra.join' undefined in: _33:any := algebra.join(_25:any, _32:bat[:oid,:int])
!TypeException:user.s0_1[28]:'algebra.join' undefined in: _37:any := algebra.join(_25:any, _36:bat[:oid,:str])
!SQLException:int:conversion of string 'two' failed
## Comment 11158
Date: 2009-03-03 12:55:14 +0100
From: @njnes
test added to BugTracker-2009 / lookup_column_name_bug_1.SF-2654300.sql
Fixed by correctly setting 'processed' and only returning columns from processed projections (ie not of the current in process project)
## Comment 11159
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654300 at http://sourceforge.net/support/tracker.php?aid=2654300
## Comment 14320
Date: 2010-07-09 15:06:44 +0200
From: @sjoerdmullender
*** Bug #1982 has been marked as a duplicate of this bug. ***
| problem with views reusing aliases ? | https://api.github.com/repos/MonetDB/MonetDB/issues/1981/comments | 0 | 2020-11-30T10:11:29Z | 2024-06-27T11:35:12Z | https://github.com/MonetDB/MonetDB/issues/1981 | 753,341,933 | 1,981 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-02 11:19:54 +0100
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-03-03 12:52:12 +0100
## Comment 11154
Date: 2009-03-02 11:19:54 +0100
From: @swingbit
drop table x cascade;
create table x (n int, s varchar(10));
insert into x (n,s) values (1, 'one');
insert into x (n,s) values (2, 'two');
insert into x (n,s) values (3, 'three');
select * from tables, x limit 10;
drop table x cascade;
This produces the following assertion:
ERR test02[5752]: mserver5: /export/scratch0/roberto/MonetDB/src/sql/src/server/rel_bin.mx:1302: rel2bin_project: Assertion `0' failed.
## Comment 11155
Date: 2009-03-03 12:52:12 +0100
From: @njnes
test added to bugtracker-2009 / join_topn.SF-2654133.sql
Fixed by correctly returning table_name for stmt st_limit
## Comment 11156
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2654133 at http://sourceforge.net/support/tracker.php?aid=2654133
| simple join fails on latest stable | https://api.github.com/repos/MonetDB/MonetDB/issues/1980/comments | 0 | 2020-11-30T10:11:26Z | 2024-06-27T11:35:12Z | https://github.com/MonetDB/MonetDB/issues/1980 | 753,341,897 | 1,980 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-01 11:31:08 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-03-01 12:08:20 +0100
## Comment 11148
Date: 2009-03-01 11:31:08 +0100
From: @drstmane
monetweb/Docs/MonetDB/MALhelp.texi.sh produces empty result; hence, then website cannot be updated accordingly.
## Comment 11149
Date: 2009-03-01 11:32:26 +0100
From: @drstmane
sorry --- "off-by-one" when choosing the right assignee ...
## Comment 11150
Date: 2009-03-01 11:39:33 +0100
From: @drstmane
In fact, the underlying M5 call manual.summary() produces an empty (or no) result.
## Comment 11151
Date: 2009-03-01 11:46:06 +0100
From: @grobian
ahhh, that explains ;)
## Comment 11152
Date: 2009-03-01 12:08:20 +0100
From: @mlkersten
The PATTERN tag was not used, while we need that for accessing the context
and list of modules.
## Comment 11153
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2651397 at http://sourceforge.net/support/tracker.php?aid=2651397
| M5: manual.summary() produces empty result | https://api.github.com/repos/MonetDB/MonetDB/issues/1979/comments | 0 | 2020-11-30T10:11:22Z | 2024-06-27T11:35:11Z | https://github.com/MonetDB/MonetDB/issues/1979 | 753,341,847 | 1,979 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-27 01:10:19 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-28 08:04:20 +0100
## Comment 11140
Date: 2009-02-27 13:10:19 +0100
From: Jens Oehlschlägel <<jens_oehl>>
We found a difference between MonetDB and Access that boils down to MonetDB doing wrong calculation if counts are mimicked via SUM(CASE WHEN <cond> 1 ELSE 0 END):
sql>SELECT
more> SUM( CASE WHEN postingYear=2005 THEN 1 ELSE 0 END ) as CNT_2005
more>, SUM( CASE WHEN postingYear=2006 THEN 1 ELSE 0 END ) as CNT_2006
more>FROM voc.t_base_sales
more>;
+----------+----------+
| cnt_2005 | cnt_2006 |
+==========+==========+
| 11535 | 7393 |
+----------+----------+
1 tuple
sql>
0 tuples
sql>-- correct would be
0 tuples
sql>SELECT postingYear, count(*) as cc
more>FROM voc.t_base_sales
more>GROUP BY postingYear
more>;
+-------------+-------+
| postingyear | cc |
+=============+=======+
| 2006 | 72929 |
| 2005 | 77071 |
+-------------+-------+
Stefan: please put the long attached SQL into autotests as 92.
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11141
Date: 2009-02-27 13:48:13 +0100
From: @drstmane
for Niels: sum of >=32767 bte does not (necessarily) fit in a sht
for all: we need to check for and consider adding proper overflow checks where ever they might occur ...
## Comment 11142
Date: 2009-02-27 13:52:21 +0100
From: @drstmane
for Niels: maybe, aggregations should always go for the largest result/target type (dbl/lng), and "downcase" only one we later see everything does fit in a smaller type ...
## Comment 11143
Date: 2009-02-27 14:20:29 +0100
From: @drstmane
added test as CASE_SUM_WRONG_COUNT.SF-2645133.sql
## Comment 11144
Date: 2009-02-27 18:05:25 +0100
From: @drstmane
Niels,
as an initial attempt to fix(?) this problem, I came up with the attached patch that basically makes sql_bind_aggr() find the last match instead of the first one (i.e., largest super-type instead of smallest super-type) --- while working fine with the Periscope tests, it makes many other SQL tests fail, maily due to type mismatches in calc.ifthenelse() calls during key- & uniques- constraint checking with bulk loading and updates --- hence, my attempt was apparently a bit short-sighted ...
Stefan
File Added: sql_bind_aggr.patch
## Comment 11145
Date: 2009-02-28 08:01:38 +0100
From: @drstmane
added test autotest_92
## Comment 11146
Date: 2009-02-28 08:04:20 +0100
From: @drstmane
Niels fixed the aggregation result type / overflow in CVS (Feb2009 branch).
## Comment 11147
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2645133 at http://sourceforge.net/support/tracker.php?aid=2645133
| Scary: CASE SUM counts wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1978/comments | 0 | 2020-11-30T10:11:18Z | 2024-06-27T11:35:10Z | https://github.com/MonetDB/MonetDB/issues/1978 | 753,341,796 | 1,978 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-27 11:49:43 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-04-02 08:28:38 +0200
## Comment 11132
Date: 2009-02-27 11:49:43 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Stefan,
attached you find a csv with the forward non-ODBC timings of
- 600k version from Feb20
- 600k version from Feb26
- 1.5M version from Feb26
The 1.5M was crashing several times, number of the crashing queries: 875, 983, 987, 999, the four SQLs follow for your convenience.
version from Feb26 is
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
crashing query SQL:
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT MIN(1) as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D02) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReportsTarget WHERE ((PostingYear>=2005) AND (PostingYear <= 2006)) GROUP BY PostingYear) as sSub3 GROUP BY KX, PostingYear, PostingStep;
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT Postingsemi as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D02) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReports WHERE (((PostingYear>2005 AND PostingYear<2006) OR (PostingYear=2005 AND Postingsemi>=1) OR (PostingYear=2006 AND Postingsemi<=2))) GROUP BY PostingYear, Postingsemi) as sSub3 GROUP BY KX, PostingYear, PostingStep;
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT Postingsemi as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D02) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReportsTarget WHERE (((PostingYear>2005 AND PostingYear<2006) OR (PostingYear=2005 AND Postingsemi>=1) OR (PostingYear=2006 AND Postingsemi<=2))) GROUP BY PostingYear, Postingsemi) as sSub3 GROUP BY KX, PostingYear, PostingStep;
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT Postingsemi as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D04) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReportsTarget WHERE (((PostingYear>2005 AND PostingYear<2006) OR (PostingYear=2005 AND Postingsemi>=1) OR (PostingYear=2006 AND Postingsemi<=2))) GROUP BY PostingYear, Postingsemi) as sSub3 GROUP BY KX, PostingYear, PostingStep;
## Comment 11133
Date: 2009-02-27 19:09:10 +0100
From: @drstmane
Jens,
thank you very much for the details.
I have not yet been able to have a closer look at the 4 failing queries on a 2 GB Win32 machine,
but we plugged some more leaks since yesterday's installer.
This afternoon, Sjoerd built new installers which will most probably be the version that we will "officially" release;
you find them at
http://monetdb.cwi.nl/downloads/Windows/Feb2009/
*Maybe* this already helps with the four failing queries ...
Unfortunately we have not yet been able to properly fix the (indeed) "scary" SUM-CASE bug you reported.
We'll provide you with an other installer, once also this bug is fixed.
Stefan
## Comment 11134
Date: 2009-02-27 21:44:20 +0100
From: @drstmane
some status info about my tests on Windows:
Win64 (Server 2003; v5.2) with 2 GB RAM:
mserver5 "Happily" survives 4 consecutive runs of all 1207 queries (without crash or restart) on both the 150k & the 1.5M data set.
Win32 (XP; v5.1) with 2 GB RAM:
mserver5 "happily" survives 4 consecutive runs of all 1207 queries (without crash or restart) only on the 150k data set.
On the 1.5M dataset,
running queries1207.sql in "forward" direction, query 983 crashes the server with
!FATAL: GDKmallocmax: failed for 247669440 bytes
while running queries1207.sql in "backward" direction, query 999 (209th query from the end) crashes the server with
!FATAL: GDKmallocmax: failed for 206391200 bytes
(did not yet test the queries between 983 & 999)
## Comment 11135
Date: 2009-02-28 00:43:03 +0100
From: @drstmane
some more experimental results:
On a 32-bit (Gentoo) Linux box with 1 GB RAM and 2 GB swap,
mserver5 "happily" survives 4 consecutive runs of all 1207 queries (without crash or restart) on both the 150k & the 1.5M data set.
On the 2 GB Win32 box,
mserver5 "happily" survives 4 consecutive runs of the first 982 out of the total 1207 queries without crash or restart) also on the 1.5M data set.
... more to come tomorrow, once nightly testing will have released the Windows box, again ...
## Comment 11136
Date: 2009-03-01 18:23:43 +0100
From: @drstmane
More observations with the 1.5M dataset on our 2GB Win32 machine
(still with the release code base as used for the installer at http://monetdb.cwi.nl/downloads/Windows/Feb2009/):
After successively removing the first query that crashes the server with
!FATAL: GDKmallocmax: failed for ? bytes
when running all queries from queries1207.sql in forward order,
i.e., queries 983, 987, 997, 999,
mserver5 "happily" survives 4 consecutive runs of the remaining 1203 queries (without crash or restart).
Likewise, a freshly started mserver5 also "happily" survives 4 consecutive runs of (only) the 4 "problem" queries (983, 987, 997, 999).
We can conclude that the 4 queries themselves do not require more memory/address space than available, but rather "only" more than left after running all previous queries --- more leak plugging might be required ...
## Comment 11137
Date: 2009-03-03 23:52:44 +0100
From: @drstmane
By their "nature", the 4 "problematic" queries (983, 987, 997, 999) and due the way they are currently translated/handled in MonetDB/SQL, produce the largest intermediate results and (also) on my 8GB 64-bit Linux machine require by a margin the longest execution times of the whole set --- ranked by decreasing execution time, the "top-scorers" are
0983 Timer 78029.632 msec
0997 Timer 77901.019 msec
0999 Timer 75571.707 msec
0987 Timer 73198.842 msec
0014 Timer 29003.736 msec
0019 Timer 23283.525 msec
0016 Timer 14071.814 msec
0017 Timer 13464.103 msec
0012 Timer 13250.273 msec
0009 Timer 13162.571 msec
0018 Timer 12509.712 msec
0875 Timer 9233.637 msec
We are working on improving the translation/evaluation of these queries --- but that might take some time ...
## Comment 11138
Date: 2009-04-02 08:28:38 +0200
From: @drstmane
Since the Feb2009-SP1 release, all 1207 queries now also work on a 2GB Win32 machine.
## Comment 11139
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2644925 at http://sourceforge.net/support/tracker.php?aid=2644925
| crash-points with 1.5M | https://api.github.com/repos/MonetDB/MonetDB/issues/1977/comments | 0 | 2020-11-30T10:11:16Z | 2024-06-27T11:35:09Z | https://github.com/MonetDB/MonetDB/issues/1977 | 753,341,774 | 1,977 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-26 03:56:03 +0100
From: Hans <<hans_0_>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-02-27 06:05:38 +0100
## Comment 11129
Date: 2009-02-26 15:56:03 +0100
From: Hans <<hans_0_>>
Attached some documents in a ZIP file {copybug.xq, testdoc, result, expected}.
We are using MonetDB-Nov2008-SuperBall-SP2 compiled and installed.
Perform the following action:
- add testdoc to database (updatable="true")
- execute copybug.xq
- the output of copybug equals "result".
- the last testdoc content should be as in "expected".
As you might notice, the replace action puts the replaced part at the wrong position. The third folder element (name="demo") becomes inserted into the second folder element, and the copied element is no longer accessible.
## Comment 11130
Date: 2009-02-27 18:05:38 +0100
From: @sjoerdmullender
The bug is fixed in the stable branch in CVS (too late for the release, unfortunately--it'll come in March).
Test added as tests/BugTracker copybug.SF-2642003.
## Comment 11131
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2642003 at http://sourceforge.net/support/tracker.php?aid=2642003
| XQUF replace insert cycle corrupts database | https://api.github.com/repos/MonetDB/MonetDB/issues/1976/comments | 0 | 2020-11-30T10:11:13Z | 2024-06-27T11:35:08Z | https://github.com/MonetDB/MonetDB/issues/1976 | 753,341,745 | 1,976 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-25 02:58:47 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-04-17 11:10:41 +0200
## Comment 11126
Date: 2009-02-25 14:58:47 +0100
From: @skinkie
CREATE TABLE "sys"."test2" (
"test1" int,
"test2" int
);
select test from test2 group by test;
!relational query without result
Shouldn't the error be like with out the group by?
select test from test2;
!SELECT: identifier 'test' unknown
## Comment 11127
Date: 2009-04-17 23:10:41 +0200
From: @njnes
fixed this bug (ie we now return the correct error). Test added to src/test/BugTracker-2009
## Comment 11128
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2637051 at http://sourceforge.net/support/tracker.php?aid=2637051
| Wrong error message for invalid identifier in group by | https://api.github.com/repos/MonetDB/MonetDB/issues/1975/comments | 0 | 2020-11-30T10:11:10Z | 2024-06-27T11:35:06Z | https://github.com/MonetDB/MonetDB/issues/1975 | 753,341,715 | 1,975 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-25 10:00:56 +0100
From: Floris Ouwendijk <<floris233>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-16 01:16:10 +0200
## Comment 11116
Date: 2009-02-25 10:00:56 +0100
From: Floris Ouwendijk <<floris233>>
An error occurs when running the following query:
doc("test.xml")//properties/../ancestor-or-self::*/name()
The error is:
ERROR = !ERROR: ancestor-or-self: illegal data in size column or context list.
!ERROR: PFll_ancestor_or_self: operation failed.
We're running the daily build of 24 Februari 2009
On startup the server reports:
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.0 loaded (default back-end is 'algebra')
The test file is added to the database as pf:add-doc("/var/dbtransfer/test.xml","test.xml")
## Comment 11117
Date: 2009-02-25 10:04:56 +0100
From: Floris Ouwendijk <<floris233>>
File Added: test.7z
## Comment 11118
Date: 2009-04-02 23:59:11 +0200
From: @drstmane
added test in pathfinder/tests/BugTracker/Tests/ancestor-or-self.SF-2636285.* (Feb2009 branch)
With the Feb2009-SP1, this works fine for me.
Floris,
could you please check, whether it (now) also works for you, and report?
If it works please close this bug report.
Thanks.
## Comment 11119
Date: 2009-04-09 09:11:53 +0200
From: Floris Ouwendijk <<floris233>>
I've tested the attached testcase on MonetDB-Feb2009-SP1, as well as Stable/.DailyBuilds./0_latest/SourceSuperBall. Can you confirm that this is not a 'works for me' but that there was an actual fix?
## Comment 11120
Date: 2009-04-09 11:03:16 +0200
From: @drstmane
Floris,
I am not consciously are of any fixes particular for this bug report, which does not mean that there have not been such a fixes.
All I can say is that
(a) it worked for me when I first tried your testcase (as reported),
(b) the test that I added on Apr 2 2009 has been working fine since then with both the Feb2009 branch and the CVS HEAD; cf., e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.unpack_doc.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.unpack_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.unpack_doc.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.unpack_doc.err.00.html
I did not check your test case with any version earlier than I reported --- I had planned to do so, but didn't have "7zip" available back then, and no time to get/install it ...
I assume that some of the fixes applied between Feb 25 2009 and the Feb2009-SP1 release did --- "consciously" or "by coincidence" --- also fix the problem reported here.
May I conclude from your statement, that it now also works for you?
If so, could you please close this bug report?
Thanks!
Stefan
## Comment 11121
Date: 2009-04-10 15:03:42 +0200
From: Floris Ouwendijk <<floris233>>
Hi Stefan,
Thanks for the response. Too bad there is no such specific fix.
I'm closing the report.
Floris
## Comment 11122
Date: 2009-04-13 19:28:54 +0200
From: Jan Rittinger <<jan.rittinger>>
Add missing cross reference: https://sourceforge.net/tracker/index.php?func=detail&aid=2668437&group_id=56967&atid=482468
Therefore the bug is still not properly fixed---only property check that makes the query fail is removed.
Stefan can you check whether the problem is still there for the example query generated with the STABLE pf version (because of the differeing optimizations there) and the HEAD runtime (as it does not contain the 'fix').
## Comment 11123
Date: 2009-04-13 23:44:08 +0200
From: @drstmane
Jan,
thanks for the hint!
However, neither the Feb2009 branch
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.err.00.html
nor the development trunk
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.err.00.html
show the originally reported error;
hence, I considered that one fixed.
Indeed, the development trunk
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/ancestor-or-self.SF-2636285.test.err.00.html
(now?) show the BATpropcheck error as reported for the parents (upwards) step(s).
## Comment 11124
Date: 2009-04-16 13:16:10 +0200
From: @peterboncz
this bug occurs due to the wrong sortedness property from 2668437
the ancestor step needs a sorted input, but if the input is marked sorted already, it does not re-sort it. with unsorted input, the consistency checks then detect
impossible behavior in the values of the size column it sees as it merges/tarverses the context sequence.
## Comment 11125
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2636285 at http://sourceforge.net/support/tracker.php?aid=2636285
| ancestor-or-self: illegal data in size column or context lis | https://api.github.com/repos/MonetDB/MonetDB/issues/1974/comments | 0 | 2020-11-30T10:11:06Z | 2024-06-27T11:35:05Z | https://github.com/MonetDB/MonetDB/issues/1974 | 753,341,677 | 1,974 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-24 08:37:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-03-18 02:40:07 +0100
## Comment 11112
Date: 2009-02-24 20:37:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Stefan,
Query 868 out of 1207 seems to systematically hang the server (almost never ending execution) if run on 750k rows (Win32 3GB RAM).
Sometimes it finishes and the next queries suffer the same, e.g.
== 868: 42770.94 sec
== 869: 130121.50 sec
== 870: 48700.14 sec
Cheers
Jens
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11113
Date: 2009-02-28 08:11:01 +0100
From: @drstmane
Jens,
with the 1.5M dataset, these three queries now seem to run
in ~3s on our 1.4GHz 2GB 32-bit Linux box, and
in ~1.5s on our 2.4 GHz 2GB Win32 box.
Could you please check, whether they are still problematic for you,
and report if so, or close this report if not?
Thanks!
Stefan
## Comment 11114
Date: 2009-03-18 14:40:07 +0100
From: @drstmane
Further tests confirmed the <= 1.5s for all three queries as I reported earlier.
## Comment 11115
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2634639 at http://sourceforge.net/support/tracker.php?aid=2634639
| Extreme query execution time | https://api.github.com/repos/MonetDB/MonetDB/issues/1973/comments | 0 | 2020-11-30T10:11:02Z | 2024-06-27T11:35:04Z | https://github.com/MonetDB/MonetDB/issues/1973 | 753,341,621 | 1,973 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-24 03:59:34 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 1970-01-01 01:00:00 +0100
## Comment 11105
Date: 2009-02-24 15:59:34 +0100
From: @grobian
Due to the security measures of mal_authorize, it is impossible for a user to change his/her own password through SQL, neither is the administrator able to change its own password through SQL (it can only (re)set passwords of other users).
We should extend the ALTER USER syntax a bit to add the required "old" password such that we can call clients.changePassword(old, new) from SQL.
## Comment 11106
Date: 2009-02-24 16:14:10 +0100
From: @grobian
currently we have:
ALTER USER user WITH PASSWORD 'string';
ALTER USER user SET SCHEMA schema;
ALTER USER user WITH PASSWORD 'string' SET SCHEMA schema;
I propose an extension like:
-- for every user to change his/her own password using the old one
CHANGE PASSWORD 'oldstring' INTO 'newstring';
and
-- root only to change username
ALTER USER user WITH USERNAME newuser;
## Comment 11107
Date: 2009-03-02 10:04:43 +0100
From: @sjoerdmullender
I'm told Oracle has
ALTER USER IDENTIFIED BY <password> [REPLACE <old_password>];
## Comment 11108
Date: 2009-03-02 19:19:30 +0100
From: @grobian
PostgreSQL uses the following:
ALTER USER name RENAME TO newname
ALTER USER davide WITH PASSWORD 'xxxxxx';
ALTER USER is an alias for ALTER ROLE
## Comment 11109
Date: 2009-05-28 22:27:01 +0200
From: @njnes
reassigned to mr-meltdown
## Comment 11110
Date: 2009-05-28 22:53:00 +0200
From: @grobian
This artifact has been marked as a duplicate of artifact 2794792 with reason:
dupe
## Comment 11111
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2633848 at http://sourceforge.net/support/tracker.php?aid=2633848
| SQL: unable to change password for a user | https://api.github.com/repos/MonetDB/MonetDB/issues/1972/comments | 0 | 2020-11-30T10:10:58Z | 2024-06-28T13:26:58Z | https://github.com/MonetDB/MonetDB/issues/1972 | 753,341,567 | 1,972 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-24 02:48:49 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-28 08:02:26 +0100
## Comment 11100
Date: 2009-02-24 14:48:49 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Niels: the attached SQL causes an exception
Stefan: please put view voc.q_sourceoverview_eur_kg permanently to our test data. Please put the SQL as autotest 91.
D:\MonetDB\MonetDB5>m5server --version
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11101
Date: 2009-02-24 17:22:42 +0100
From: @drstmane
Same column name ambiguity problem as
[ 2633544 ] String constant in view converted to uppercase
https://sourceforge.net/tracker/index.php?func=detail&aid=2633544&group_id=56967&atid=482468
Works fine with non-ambiguous column name in view:
sql>CREATE VIEW voc.q_sourceoverview_eur_kg_OK AS
more>SELECT t_base_sales.*
more>, 'EUR' AS DT_CURR
more>, 'kg' AS DT_UOM_V
more>FROM voc.t_base_sales
more>;
0 tuples
sql>SELECT DT_Country as key01
more>, DT_Customer_Attrib1 as key02
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_D00) as UD00_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_D00) as UD00_P2
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_VOLUME) as VV2_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_VOLUME) as VV2_P2
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_D01) as UD01_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_D01) as UD01_P2
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_VOLUME) as VV4_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_VOLUME) as VV4_P2
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_D05) as SD05_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_D05) as SD05_P2
more>, SUM( (CASE WHEN PostingYear=2005 THEN 1 ELSE 0 END) *DT_VOLUME) as volume1_P1
more>, SUM( (CASE WHEN PostingYear=2006 THEN 1 ELSE 0 END) *DT_VOLUME) as volume1_P2
more>, sum(DT_D00)/SUM(DT_VOLUME) as aField1
more>FROM voc.q_SourceOverview_eur_kg_OK
more>WHERE (DT_UOM_V='kg')
more> AND (DT_CURR='EUR')
more> AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
more>GROUP BY DT_Country, DT_Customer_Attrib1
more>HAVING sum (DT_VOLUME) <> 0
more>ORDER BY aField1 DESC
more>;
[...]
96 tuples
## Comment 11102
Date: 2009-02-24 17:50:13 +0100
From: @drstmane
added original query as test BatAppendUndefined.SF-2633634.sql
added modified query as test BatAppendUndefined.SF-2633634_OK.sql
## Comment 11103
Date: 2009-02-28 08:01:42 +0100
From: @drstmane
added autotest_91
## Comment 11104
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2633634 at http://sourceforge.net/support/tracker.php?aid=2633634
| !TypeException:user.s0_1[97]:'bat.append' undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/1971/comments | 0 | 2020-11-30T10:10:54Z | 2024-06-28T13:26:57Z | https://github.com/MonetDB/MonetDB/issues/1971 | 753,341,536 | 1,971 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-24 02:23:44 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-27 07:36:09 +0100
## Comment 11096
Date: 2009-02-24 14:23:44 +0100
From: Jens Oehlschlägel <<jens_oehl>>
'kg' in view finally becomes 'KG' which messes up all sorts of things.
D:\MonetDB\MonetDB5>m5server --version
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11097
Date: 2009-02-24 17:13:37 +0100
From: @drstmane
The problem with this one is an ambiguous column name: the view creates a column "DT_UOM", while a columns with the same name already exists in the undelying t_base_sales table.
Niels will add a check that detects and reports such ambiguity.
Renaming the respective column in the view to, say, "DT_UOM_V" yields the expected result:
sql>CREATE VIEW voc.q_sourceoverview_eur_kg_test AS
more>SELECT t_base_sales.*
more>, 'EUR' AS DT_CURR
more>, 'kg' AS DT_UOM_V
more>FROM voc.t_base_sales
more>;
0 tuples
sql>select dt_curr, dt_uom_v from voc.q_sourceoverview_eur_kg_test limit 1;
+---------+----------+
| dt_curr | dt_uom_v |
+=========+==========+
| EUR | kg |
+---------+----------+
1 tuple
sql>select dt_curr, dt_uom_v from voc.q_sourceoverview_eur_kg_test where dt_uom_v='kg' limit 1;
+---------+----------+
| dt_curr | dt_uom_v |
+=========+==========+
| EUR | kg |
+---------+----------+
1 tuple
sql>select dt_curr, dt_uom_v from voc.q_sourceoverview_eur_kg_test where dt_uom_v='KG' limit 1;
0 tuples
sql>DROP VIEW voc.q_sourceoverview_eur_kg_test;
0 tuples
## Comment 11098
Date: 2009-02-24 17:48:32 +0100
From: @drstmane
added original query as test StringConstantToUppercase.SF-2633544.sql
added modified query as test StringConstantToUppercase.SF-2633544_OK.sql
## Comment 11099
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2633544 at http://sourceforge.net/support/tracker.php?aid=2633544
| String constant in view converted to uppercase | https://api.github.com/repos/MonetDB/MonetDB/issues/1970/comments | 0 | 2020-11-30T10:10:51Z | 2024-06-28T13:26:56Z | https://github.com/MonetDB/MonetDB/issues/1970 | 753,341,498 | 1,970 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-23 06:32:07 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-24 05:02:49 +0100
## Comment 11090
Date: 2009-02-23 18:32:07 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Niels: replication attached
Stefan: please put first SQL into autotest cases as 90
Observed with 150k rows under Win32:
MonetDB server v5.10.0 (32-bit), based on kernel v1.28.0 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: C:\Documents and Settings\sjoerd\My Documents\src\stable\vs32\NT32
Libraries:
libpcre: 7.7 2008-05-07
libxml2: 2.6.32
Compiled by: sjoerd@GANS
Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox
## Comment 11091
Date: 2009-02-23 19:14:53 +0100
From: @drstmane
added test as IN_CASE_ZERO_TUPLES.SF-2630881.*
SQL compiler fails with
"
could not find L6.L5
q_sourceoverview.dt_country
q_sourceoverview.dt_customer_attrib1
q_sourceoverview.dt_product_attrib2
q_sourceoverview.dt_customer_group
q_sourceoverview.postingyear
q_sourceoverview.postingquarter
q_sourceoverview.dt_d00
q_sourceoverview.dt_d01
q_sourceoverview.dt_volume
q_sourceoverview.dt_price_categ
q_sourceoverview.dt_uom
q_sourceoverview.dt_curr
tbl_uom.%TID%
t_base_sales.%TID%
tbl_exchange_rates.%TID%
q_sourceoverview.dt_country
q_sourceoverview.dt_customer_attrib1
q_sourceoverview.dt_customer_group
q_sourceoverview.dt_product_attrib2
q_sourceoverview.dt_price_categ
q_sourceoverview.L1
q_sourceoverview.L2
q_sourceoverview.L3
q_sourceoverview.L4
"
detailed analysis pending
## Comment 11092
Date: 2009-02-23 19:46:29 +0100
From: @drstmane
Also this one triggers an assertion:
could not find L6.L5
q_sourceoverview.dt_country
q_sourceoverview.dt_customer_attrib1
q_sourceoverview.dt_product_attrib2
q_sourceoverview.dt_customer_group
q_sourceoverview.postingyear
q_sourceoverview.postingquarter
q_sourceoverview.dt_d00
q_sourceoverview.dt_d01
q_sourceoverview.dt_volume
q_sourceoverview.dt_price_categ
q_sourceoverview.dt_uom
q_sourceoverview.dt_curr
tbl_uom.%TID%
t_base_sales.%TID%
tbl_exchange_rates.%TID%
q_sourceoverview.dt_country
q_sourceoverview.dt_customer_attrib1
q_sourceoverview.dt_customer_group
q_sourceoverview.dt_product_attrib2
q_sourceoverview.dt_price_categ
q_sourceoverview.L1
q_sourceoverview.L2
q_sourceoverview.L3
q_sourceoverview.L4
mserver5: /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:1538: rel2bin_groupby: Assertion `0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe1c93950 (LWP 19838)]
0x0000003675232f05 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.3-2.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb) up
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
(gdb)
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
(gdb)
3 0x00007fffe276095f in rel2bin_groupby (sql=0x13c92f8, rel=0x14af798, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:1538
1538 assert(0);
(gdb) li
1533 therefor we pass the group by columns too
1534 */
1535 if (!aggrstmt)
1536 aggrstmt = exp_bin(sql, aggrexp, sub, cursub, groupby, NULL);
1537 if (!aggrstmt) {
1538 assert(0);
1539 stmt_destroy(cursub);
1540 stmt_destroy(sub);
1541 if (groupby) grp_destroy(groupby);
1542 return NULL;
(gdb) bt
0 0x0000003675232f05 in raise () from /lib64/libc.so.6
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
3 0x00007fffe276095f in rel2bin_groupby (sql=0x13c92f8, rel=0x14af798, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:1538
4 0x00007fffe276644d in subrel_bin (sql=0x13c92f8, rel=0x14af798, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:3230
5 0x00007fffe2760374 in rel2bin_select (sql=0x13c92f8, rel=0x14b2948, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:1395
6 0x00007fffe2766425 in subrel_bin (sql=0x13c92f8, rel=0x14b2948, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:3226
7 0x00007fffe275fd7a in rel2bin_project (sql=0x13c92f8, rel=0x14af958, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:1279
8 0x00007fffe27663fd in subrel_bin (sql=0x13c92f8, rel=0x14af958, refs=0x1404648) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:3222
9 0x00007fffe27665f9 in output_rel_bin (sql=0x13c92f8, rel=0x14af958) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/rel_bin.mx:3275
10 0x00007fffe26b9275 in sql_symbol2stmt (c=0x13c92f8, sym=0x13ce158) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/backends/monet5/sql.mx:1102
11 0x00007fffe26f3f42 in SQLparser (c=0x604a00) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/backends/monet5/sql_scenario.mx:1013
12 0x00007ffff7d336cb in runPhase (c=0x604a00, phase=1) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:591
13 0x00007ffff7d337c2 in runScenarioBody (c=0x604a00) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:627
14 0x00007ffff7d339ef in runScenario (c=0x604a00) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:661
15 0x00007ffff7cf15aa in MSserveClient (dummy=0x604a00) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_session.mx:460
16 0x0000003675e073da in start_thread () from /lib64/libpthread.so.0
17 0x00000036752e62bd in clone () from /lib64/libc.so.6
(gdb)
## Comment 11093
Date: 2009-02-24 17:02:49 +0100
From: @drstmane
Fixed in Feb2009 branch by Niels.
## Comment 11094
Date: 2009-02-24 18:19:45 +0100
From: @drstmane
added test autotest_90
## Comment 11095
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2630881 at http://sourceforge.net/support/tracker.php?aid=2630881
| SELECT expression with IN in CASE statement causes '0 tuples | https://api.github.com/repos/MonetDB/MonetDB/issues/1969/comments | 0 | 2020-11-30T10:10:47Z | 2024-06-27T11:35:00Z | https://github.com/MonetDB/MonetDB/issues/1969 | 753,341,457 | 1,969 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-23 03:25:42 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-24 05:02:22 +0100
## Comment 11084
Date: 2009-02-23 15:25:42 +0100
From: Jens Oehlschlägel <<jens_oehl>>
observed under Win32 with MonetDB5-SQL-Installer-i386-20090220.msi with 150k or 1.5M rows
Adding a WHERE clause to an on-the-fly view definition using WITH crashes the server. In addition WITH can slow-down execution by factor 7.
Replication code attached
## Comment 11085
Date: 2009-02-23 19:01:51 +0100
From: @drstmane
test added in WITH_Crash.SF-2630278.*
server crashes with segfault
detailed analysis pending
## Comment 11086
Date: 2009-02-23 19:04:39 +0100
From: @drstmane
the query triggers an assertion:
mserver5: /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1057: rel2bin: Assertion `list_length(l)' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe1492950 (LWP 16164)]
0x0000003675232f05 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.3-2.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb) up
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
(gdb)
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
(gdb)
3 0x00007fffe1f1d2c0 in rel2bin (c=0x13cc858, s=0x175d8b8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1057
1057 assert(list_length(l));
(gdb) li
1052 node *n;
1053
1054 list *ol, *l = s->op1.lval;
1055
1056 ol = l;
1057 assert(list_length(l));
1058 if (list_length(l) == 1) {
1059 res = rel2bin(c, l->h->data);
1060 } else {
1061 stmt *sel;
(gdb) bt
0 0x0000003675232f05 in raise () from /lib64/libc.so.6
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
3 0x00007fffe1f1d2c0 in rel2bin (c=0x13cc858, s=0x175d8b8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1057
4 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x175d7b8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
5 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x17dfd98) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
6 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x17dfba8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
7 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x17dfc98) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
8 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x17f4818) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
9 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x18f74f8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
10 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x19050b8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
11 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190b358) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
12 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190b558) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
13 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190b408) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
14 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190b948) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
15 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190ba78) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
16 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x1907078) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
17 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x1910b98) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
18 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x1910cf8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
19 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x1910da8) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
20 0x00007fffe1f1d4bb in rel2bin (c=0x13cc858, s=0x190b608) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_rel2bin.mx:1161
21 0x00007fffe1eb828d in sql_symbol2stmt (c=0x13cc858, sym=0x172af78) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/backends/monet5/sql.mx:1107
22 0x00007fffe1ef2f42 in SQLparser (c=0x604c40) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/backends/monet5/sql_scenario.mx:1013
23 0x00007ffff7d336cb in runPhase (c=0x604c40, phase=1) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:591
24 0x00007ffff7d337c2 in runScenarioBody (c=0x604c40) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:627
25 0x00007ffff7d339ef in runScenario (c=0x604c40) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_scenario.mx:661
26 0x00007ffff7cf15aa in MSserveClient (dummy=0x604c40) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/MonetDB5/src/mal/mal_session.mx:460
27 0x0000003675e073da in start_thread () from /lib64/libpthread.so.0
28 0x00000036752e62bd in clone () from /lib64/libc.so.6
(gdb) print l
$1 = (list *) 0x17b0eb8
(gdb) print *l
$2 = {destroy = 0x7fffe1f09105 <stmt_destroy>, h = 0x0, t = 0x0, cnt = 0}
(gdb)
## Comment 11087
Date: 2009-02-24 17:02:22 +0100
From: @drstmane
Fixed in Feb2009 branch by Niels.
## Comment 11088
Date: 2009-02-24 18:24:34 +0100
From: @drstmane
Niels also fixed the performance of the WITH variant:
sql>SELECT dt_curr, postingyear, COUNT(*) AS cc
more>, SUM(dt_d00) AS dt_d00
more>, SUM(dt_d01) AS dt_d01
more>, SUM(dt_d02) AS dt_d02
more>, SUM(dt_d03) AS dt_d03
more>, SUM(dt_d04) AS dt_d04
more>, SUM(dt_d05) AS dt_d05
more>FROM voc.q_local_Source_currency
more>WHERE dt_curr = 'USD'
more> AND dt_uom = 'kg'
more>GROUP BY dt_curr, postingyear
more>ORDER BY dt_curr, postingyear
more>;
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
| dt_curr | postingyear | cc | dt_d00 | dt_d01 | dt_d02 | dt_d03 | dt_d04 | dt_d05 |
+=========+=============+=======+========================+========================+========================+========================+========================+========================+
| USD | 2005 | 77071 | 893317923.54067528 | 890043738.04487252 | 766314385.69348729 | 341006606.34187269 | 236727569.96897939 | 118503157.67650178 |
| USD | 2006 | 72929 | 936231548.33830655 | 934097209.92310703 | 796742903.4459691 | 331508542.05018795 | 236810711.61478955 | 112686518.11059061 |
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
2 tuples
Timer 81.964 msec 2 rows
^^^^^^
sql>WITH my_currency AS (SELECT * FROM voc.q_local_Source_currency)
more>SELECT dt_curr, postingyear, COUNT(*) AS cc
more>, SUM(dt_d00) AS dt_d00
more>, SUM(dt_d01) AS dt_d01
more>, SUM(dt_d02) AS dt_d02
more>, SUM(dt_d03) AS dt_d03
more>, SUM(dt_d04) AS dt_d04
more>, SUM(dt_d05) AS dt_d05
more>FROM my_currency
more>WHERE dt_curr = 'USD'
more> AND dt_uom = 'kg'
more>GROUP BY dt_curr, postingyear
more>ORDER BY dt_curr, postingyear
more>;
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
| dt_curr | postingyear | cc | dt_d00 | dt_d01 | dt_d02 | dt_d03 | dt_d04 | dt_d05 |
+=========+=============+=======+========================+========================+========================+========================+========================+========================+
| USD | 2005 | 77071 | 893317923.54067528 | 890043738.04487252 | 766314385.69348729 | 341006606.34187269 | 236727569.96897939 | 118503157.67650178 |
| USD | 2006 | 72929 | 936231548.33830655 | 934097209.92310703 | 796742903.4459691 | 331508542.05018795 | 236810711.61478955 | 112686518.11059061 |
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
2 tuples
Timer 81.909 msec 2 rows
^^^^^^
sql>WITH my_currency AS (
more> SELECT *
more> FROM voc.q_local_Source_currency
more> WHERE dt_curr = 'USD'
more> AND dt_uom = 'kg'
more> )
more>SELECT dt_curr, postingyear, COUNT(*) AS cc
more>, SUM(dt_d00) AS dt_d00
more>, SUM(dt_d01) AS dt_d01
more>, SUM(dt_d02) AS dt_d02
more>, SUM(dt_d03) AS dt_d03
more>, SUM(dt_d04) AS dt_d04
more>, SUM(dt_d05) AS dt_d05
more>FROM my_currency
more>GROUP BY dt_curr, postingyear
more>ORDER BY dt_curr, postingyear
more>;
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
| dt_curr | postingyear | cc | dt_d00 | dt_d01 | dt_d02 | dt_d03 | dt_d04 | dt_d05 |
+=========+=============+=======+========================+========================+========================+========================+========================+========================+
| USD | 2005 | 77071 | 893317923.54067528 | 890043738.04487252 | 766314385.69348729 | 341006606.34187269 | 236727569.96897939 | 118503157.67650178 |
| USD | 2006 | 72929 | 936231548.33830655 | 934097209.92310703 | 796742903.4459691 | 331508542.05018795 | 236810711.61478955 | 112686518.11059061 |
+---------+-------------+-------+------------------------+------------------------+------------------------+------------------------+------------------------+------------------------+
2 tuples
Timer 78.615 msec 2 rows
^^^^^^
## Comment 11089
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2630278 at http://sourceforge.net/support/tracker.php?aid=2630278
| WHERE in WITH crashes the server | https://api.github.com/repos/MonetDB/MonetDB/issues/1968/comments | 0 | 2020-11-30T10:10:43Z | 2024-06-27T11:34:59Z | https://github.com/MonetDB/MonetDB/issues/1968 | 753,341,412 | 1,968 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-23 01:24:35 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-24 05:01:44 +0100
## Comment 11080
Date: 2009-02-23 13:24:35 +0100
From: Jens Oehlschlägel <<jens_oehl>>
possibly related to report 2629960
observed under Win32 with MonetDB5-SQL-Installer-i386-20090220.msi
WHERE condition OR condition
returns wrong number of rows
SQL statements and output attached
## Comment 11081
Date: 2009-02-23 18:53:48 +0100
From: @drstmane
test added as BrokenOR.SF-2629987.*
fails as reported
detailed analysis pending
## Comment 11082
Date: 2009-02-24 17:01:44 +0100
From: @drstmane
Fixed in Feb2009 branch by Niels.
## Comment 11083
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2629987 at http://sourceforge.net/support/tracker.php?aid=2629987
| WHERE with OR completely broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1967/comments | 0 | 2020-11-30T10:10:40Z | 2024-06-27T11:34:58Z | https://github.com/MonetDB/MonetDB/issues/1967 | 753,341,371 | 1,967 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-23 01:16:36 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1965
Last updated: 2010-07-09 15:10:39 +0200
## Comment 11077
Date: 2009-02-23 13:16:36 +0100
From: Jens Oehlschlägel <<jens_oehl>>
-- this statement gives 150000 rows
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM voc.q_SourceOverview
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
-- since q_SourceOverview is defined to be same as q_local_Source_currency
-- we also get 150000 rows
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM voc.q_local_Source_currency
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
-- now replacing the viewname with the vew definition in the a subquery
-- gives only 35883 rows !??
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM (
SELECT
T_BASE_SALES.DT_Region,
T_BASE_SALES.DT_Country,
T_BASE_SALES.DT_PG_Region,
T_BASE_SALES.DT_PG_Customer,
T_BASE_SALES.DT_PG_Key_product,
T_BASE_SALES.DT_PG_zipcode,
T_BASE_SALES.DT_Customer_Number,
T_BASE_SALES.DT_Customer_NameCode,
T_BASE_SALES.DT_Customer_Name,
T_BASE_SALES.DT_Customer_Attrib1,
T_BASE_SALES.DT_Customer_Attrib2Code,
T_BASE_SALES.DT_Customer_Attrib2,
T_BASE_SALES.DT_Customer_Attrib3,
T_BASE_SALES.DT_Product_Line,
T_BASE_SALES.DT_Product_Attrib1,
T_BASE_SALES.DT_Product_Attrib2,
T_BASE_SALES.DT_Product_Attrib3,
T_BASE_SALES.DT_Product_Name,
T_BASE_SALES.DT_Customer_Group,
T_BASE_SALES.DT_Product_Number,
T_BASE_SALES.DT_Product_Attrib1_Number,
T_BASE_SALES.ImportedDate,
T_BASE_SALES.PostingDate,
T_BASE_SALES.PostingYear,
T_BASE_SALES.PostingSemi,
T_BASE_SALES.PostingMonth,
T_BASE_SALES.PostingWeek,
T_BASE_SALES.PostingQuarter,
T_BASE_SALES.InputIndex,
T_BASE_SALES.ImportedTypeTransac,
T_BASE_SALES.TypeTransac,
T_BASE_SALES.PostingDate_Text,
T_BASE_SALES.DT_D00*TBL_EXCHANGE_RATES.Exchrate AS DT_D00,
T_BASE_SALES.DT_D01*TBL_EXCHANGE_RATES.Exchrate AS DT_D01,
T_BASE_SALES.DT_D02*TBL_EXCHANGE_RATES.Exchrate AS DT_D02,
T_BASE_SALES.DT_D03*TBL_EXCHANGE_RATES.Exchrate AS DT_D03,
T_BASE_SALES.DT_D04*TBL_EXCHANGE_RATES.Exchrate AS DT_D04,
T_BASE_SALES.DT_D05*TBL_EXCHANGE_RATES.Exchrate AS DT_D05,
T_BASE_SALES.DT_VOLUME*xRate AS DT_VOLUME,
T_BASE_SALES.DT_C00*TBL_EXCHANGE_RATES.Exchrate AS DT_C00,
T_BASE_SALES.DT_C01_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C01_01,
T_BASE_SALES.DT_C02_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C02_01,
T_BASE_SALES.DT_C03_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C03_01,
T_BASE_SALES.DT_C04_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C04_01,
T_BASE_SALES.DT_C05_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C05_01,
T_BASE_SALES.DT_D01_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_01,
T_BASE_SALES.DT_D01_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_02,
T_BASE_SALES.DT_D01_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_03,
T_BASE_SALES.DT_D01_04*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_04,
T_BASE_SALES.DT_D02_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_01,
T_BASE_SALES.DT_D02_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_02,
T_BASE_SALES.DT_D02_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_03,
T_BASE_SALES.DT_D02_04*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_04,
T_BASE_SALES.DT_D02_05*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_05,
T_BASE_SALES.DT_D02_06*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_06,
T_BASE_SALES.DT_D02_90*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_90,
T_BASE_SALES.DT_D02_91*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_91,
T_BASE_SALES.DT_D03_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D03_01,
T_BASE_SALES.DT_D04_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D04_01,
T_BASE_SALES.DT_D05_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_01,
T_BASE_SALES.DT_D05_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_02,
T_BASE_SALES.DT_D05_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_03,
T_BASE_SALES.DT_Sales*TBL_EXCHANGE_RATES.Exchrate AS DT_Sales,
T_BASE_SALES.DT_Revenues*TBL_EXCHANGE_RATES.Exchrate AS DT_Revenues,
T_BASE_SALES.DT_PRICE_CATEG,
T_BASE_SALES.DT_PRICE_CLASS,
T_BASE_SALES.DT_CTR_DURATION_CATEG,
T_BASE_SALES.DT_ShareFix,
T_BASE_SALES.DT_ShareVar,
T_BASE_SALES.DT_PLANT,
TBL_UOM.UnitUOM AS DT_UOM,
T_BASE_SALES.DT_ORIG_CURR,
T_BASE_SALES.DT_ORIG_XRATE,
TBL_EXCHANGE_RATES.DT_CURR
FROM voc.TBL_UOM, voc.T_BASE_SALES INNER JOIN voc.TBL_EXCHANGE_RATES
ON (T_BASE_SALES.PostingYear=TBL_EXCHANGE_RATES."year")
AND (T_BASE_SALES.PostingMonth=TBL_EXCHANGE_RATES.MonthNumber)
) sub1
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
## Comment 11078
Date: 2009-02-23 15:09:57 +0100
From: @drstmane
accidental duplicate of
[ 2629897 ] View and subquery don't give same results
https://sourceforge.net/tracker/index.php?func=detail&aid=2629897&group_id=56967&atid=482468
## Comment 11079
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2629960 at http://sourceforge.net/support/tracker.php?aid=2629960
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14323
Date: 2010-07-09 15:10:39 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1965 ***
| View and subquery don't give same results | https://api.github.com/repos/MonetDB/MonetDB/issues/1966/comments | 0 | 2020-11-30T10:10:36Z | 2024-06-28T13:26:56Z | https://github.com/MonetDB/MonetDB/issues/1966 | 753,341,341 | 1,966 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-23 12:43:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2010-07-09 15:10:39 +0200
## Comment 11073
Date: 2009-02-23 12:43:20 +0100
From: Jens Oehlschlägel <<jens_oehl>>
-- this statement gives 150000 rows
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM voc.q_SourceOverview
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
-- since q_SourceOverview is defined to be same as q_local_Source_currency
-- we also get 150000 rows
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM voc.q_local_Source_currency
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
-- now replacing the viewname with the vew definition in the a subquery
-- gives only 35883 rows !??
SELECT count(*) FROM (
SELECT postingYear, postingMonth, DT_Country, DT_Customer_Attrib1, DT_Customer_Group, DT_Customer_Attrib2, DT_Customer_Name, DT_Region, DT_Product_Attrib2, DT_Product_Line, DT_PRICE_CATEG, DT_CTR_DURATION_CATEG, DT_VOLUME, DT_D00, DT_D01, DT_D02, DT_D03, DT_D04, DT_D05, TYPETRANSAC
FROM (
SELECT
T_BASE_SALES.DT_Region,
T_BASE_SALES.DT_Country,
T_BASE_SALES.DT_PG_Region,
T_BASE_SALES.DT_PG_Customer,
T_BASE_SALES.DT_PG_Key_product,
T_BASE_SALES.DT_PG_zipcode,
T_BASE_SALES.DT_Customer_Number,
T_BASE_SALES.DT_Customer_NameCode,
T_BASE_SALES.DT_Customer_Name,
T_BASE_SALES.DT_Customer_Attrib1,
T_BASE_SALES.DT_Customer_Attrib2Code,
T_BASE_SALES.DT_Customer_Attrib2,
T_BASE_SALES.DT_Customer_Attrib3,
T_BASE_SALES.DT_Product_Line,
T_BASE_SALES.DT_Product_Attrib1,
T_BASE_SALES.DT_Product_Attrib2,
T_BASE_SALES.DT_Product_Attrib3,
T_BASE_SALES.DT_Product_Name,
T_BASE_SALES.DT_Customer_Group,
T_BASE_SALES.DT_Product_Number,
T_BASE_SALES.DT_Product_Attrib1_Number,
T_BASE_SALES.ImportedDate,
T_BASE_SALES.PostingDate,
T_BASE_SALES.PostingYear,
T_BASE_SALES.PostingSemi,
T_BASE_SALES.PostingMonth,
T_BASE_SALES.PostingWeek,
T_BASE_SALES.PostingQuarter,
T_BASE_SALES.InputIndex,
T_BASE_SALES.ImportedTypeTransac,
T_BASE_SALES.TypeTransac,
T_BASE_SALES.PostingDate_Text,
T_BASE_SALES.DT_D00*TBL_EXCHANGE_RATES.Exchrate AS DT_D00,
T_BASE_SALES.DT_D01*TBL_EXCHANGE_RATES.Exchrate AS DT_D01,
T_BASE_SALES.DT_D02*TBL_EXCHANGE_RATES.Exchrate AS DT_D02,
T_BASE_SALES.DT_D03*TBL_EXCHANGE_RATES.Exchrate AS DT_D03,
T_BASE_SALES.DT_D04*TBL_EXCHANGE_RATES.Exchrate AS DT_D04,
T_BASE_SALES.DT_D05*TBL_EXCHANGE_RATES.Exchrate AS DT_D05,
T_BASE_SALES.DT_VOLUME*xRate AS DT_VOLUME,
T_BASE_SALES.DT_C00*TBL_EXCHANGE_RATES.Exchrate AS DT_C00,
T_BASE_SALES.DT_C01_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C01_01,
T_BASE_SALES.DT_C02_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C02_01,
T_BASE_SALES.DT_C03_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C03_01,
T_BASE_SALES.DT_C04_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C04_01,
T_BASE_SALES.DT_C05_01*TBL_EXCHANGE_RATES.Exchrate AS DT_C05_01,
T_BASE_SALES.DT_D01_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_01,
T_BASE_SALES.DT_D01_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_02,
T_BASE_SALES.DT_D01_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_03,
T_BASE_SALES.DT_D01_04*TBL_EXCHANGE_RATES.Exchrate AS DT_D01_04,
T_BASE_SALES.DT_D02_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_01,
T_BASE_SALES.DT_D02_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_02,
T_BASE_SALES.DT_D02_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_03,
T_BASE_SALES.DT_D02_04*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_04,
T_BASE_SALES.DT_D02_05*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_05,
T_BASE_SALES.DT_D02_06*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_06,
T_BASE_SALES.DT_D02_90*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_90,
T_BASE_SALES.DT_D02_91*TBL_EXCHANGE_RATES.Exchrate AS DT_D02_91,
T_BASE_SALES.DT_D03_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D03_01,
T_BASE_SALES.DT_D04_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D04_01,
T_BASE_SALES.DT_D05_01*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_01,
T_BASE_SALES.DT_D05_02*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_02,
T_BASE_SALES.DT_D05_03*TBL_EXCHANGE_RATES.Exchrate AS DT_D05_03,
T_BASE_SALES.DT_Sales*TBL_EXCHANGE_RATES.Exchrate AS DT_Sales,
T_BASE_SALES.DT_Revenues*TBL_EXCHANGE_RATES.Exchrate AS DT_Revenues,
T_BASE_SALES.DT_PRICE_CATEG,
T_BASE_SALES.DT_PRICE_CLASS,
T_BASE_SALES.DT_CTR_DURATION_CATEG,
T_BASE_SALES.DT_ShareFix,
T_BASE_SALES.DT_ShareVar,
T_BASE_SALES.DT_PLANT,
TBL_UOM.UnitUOM AS DT_UOM,
T_BASE_SALES.DT_ORIG_CURR,
T_BASE_SALES.DT_ORIG_XRATE,
TBL_EXCHANGE_RATES.DT_CURR
FROM voc.TBL_UOM, voc.T_BASE_SALES INNER JOIN voc.TBL_EXCHANGE_RATES
ON (T_BASE_SALES.PostingYear=TBL_EXCHANGE_RATES."year")
AND (T_BASE_SALES.PostingMonth=TBL_EXCHANGE_RATES.MonthNumber)
) sub1
WHERE (DT_UOM='kg')
AND (DT_CURR='EUR')
AND (( (PostingYear=2005)) or ( (PostingYear=2006)))
) sub
;
## Comment 11074
Date: 2009-02-23 18:44:04 +0100
From: @drstmane
added test as view_vs_subquery.SF-2629897*
fails as reported
detailed analysis pending
## Comment 11075
Date: 2009-02-24 17:01:13 +0100
From: @drstmane
Fixed in Feb2009 branch by Niels.
## Comment 11076
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2629897 at http://sourceforge.net/support/tracker.php?aid=2629897
## Comment 14324
Date: 2010-07-09 15:10:39 +0200
From: @sjoerdmullender
*** Bug #1966 has been marked as a duplicate of this bug. ***
| View and subquery don't give same results | https://api.github.com/repos/MonetDB/MonetDB/issues/1965/comments | 0 | 2020-11-30T10:10:33Z | 2024-06-27T11:34:56Z | https://github.com/MonetDB/MonetDB/issues/1965 | 753,341,308 | 1,965 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-22 09:56:09 +0100
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2009-03-04 06:34:17 +0100
## Comment 11070
Date: 2009-02-22 09:56:09 +0100
From: @drstmane
sql/src/test/bugs/Tests/rangejoin_optimize_bug.sql:
!~BATpropcheck: BAT tmpr_3162(-1650)[dbl,void] with 49 tuples was incorrectly marked nonil!
!~BATpropcheck: BAT tmpr_3207(-1671)[dbl,void] with 49 tuples was incorrectly marked nonil!
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora8/src_test_bugs/rangejoin_optimize_bug.out.00.html
## Comment 11071
Date: 2009-03-04 18:34:17 +0100
From: @njnes
The batcalc module didn't correctly set the nonil incase of accumulator versions.
## Comment 11072
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2627138 at http://sourceforge.net/support/tracker.php?aid=2627138
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: test fails with BATpropcheck error | https://api.github.com/repos/MonetDB/MonetDB/issues/1964/comments | 0 | 2020-11-30T10:10:29Z | 2024-06-27T11:34:55Z | https://github.com/MonetDB/MonetDB/issues/1964 | 753,341,268 | 1,964 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-22 09:56:06 +0100
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-12 10:18:27 +0100
## Comment 11065
Date: 2009-02-22 09:56:06 +0100
From: @drstmane
ALG & MPS:
pathfinder/tests/BugTracker/Tests/Parse_error_with_pf_collection.SF-2020631.xq
!~BATpropcheck: BAT tmpr_32560(-13680)[oid,void] with 2 tuples was incorrectly marked keyed!
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.out.00.html
MPS:
pathfinder/tests/BugTracker/Tests/pf-O0_produces_wrong_MIL.SF-1771532.py
!~BATpropcheck: BAT tmpr_20743(-8675)[oid,void] with 4 tuples was incorrectly marked nonil!
!~BATpropcheck: BAT tmpr_20723(-8659)[oid,void] with 4 tuples was incorrectly marked nonil!
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/pf-O0_produces_wrong_MIL.SF-1771532.out.00.html
## Comment 11066
Date: 2009-06-05 13:25:51 +0200
From: @drstmane
updated TestWeb URLs:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_BugTracker/pf-O0_produces_wrong_MIL.SF-1771532.out.00.html
## Comment 11067
Date: 2009-09-25 12:00:57 +0200
From: @drstmane
updated TestWeb URLs:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Parse_error_with_pf_collection.SF-2020631.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_BugTracker/pf-O0_produces_wrong_MIL.SF-1771532.out.00.html
## Comment 11068
Date: 2009-11-12 10:18:27 +0100
From: @peterboncz
this was fixed yesterday in Nov2009
## Comment 11069
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2627137 at http://sourceforge.net/support/tracker.php?aid=2627137
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: tests fail with BATpropcheck error | https://api.github.com/repos/MonetDB/MonetDB/issues/1963/comments | 0 | 2020-11-30T10:10:26Z | 2024-06-27T11:34:54Z | https://github.com/MonetDB/MonetDB/issues/1963 | 753,341,237 | 1,963 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-21 06:44:19 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-02-21 06:50:15 +0100
## Comment 11062
Date: 2009-02-21 18:44:19 +0100
From: @drstmane
.../MonetDB5/src/optimizer/opt_joinpath.mx(109): error 593: variable "slimit" was set but never used
int limit,slimit, *used;
^
... since I'm not sure, whether the variable is just a copy&paste left-over and could hence simply be remove, I rather file this bug report and assign it to the author.
## Comment 11063
Date: 2009-02-21 18:50:14 +0100
From: @mlkersten
commit pending update
## Comment 11064
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2624697 at http://sourceforge.net/support/tracker.php?aid=2624697
| M5: src/optimizer/opt_joinpath.mx fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1962/comments | 0 | 2020-11-30T10:10:23Z | 2024-06-27T11:34:53Z | https://github.com/MonetDB/MonetDB/issues/1962 | 753,341,188 | 1,962 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-21 01:29:47 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-03-26 03:46:52 +0100
## Comment 11059
Date: 2009-02-21 13:29:47 +0100
From: @grobian
merovingian seems to get stuck in its shutdown sequence on Linux. I looks related to locking, but does not occur on Solaris for some reason.
## Comment 11060
Date: 2009-02-23 12:58:08 +0100
From: @grobian
under Linux a select isn't interrupted upon a signal, like on Solaris causing merovingian to hang.
## Comment 11061
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2623838 at http://sourceforge.net/support/tracker.php?aid=2623838
| merovingian sometimes hangs under linux when stopping | https://api.github.com/repos/MonetDB/MonetDB/issues/1961/comments | 0 | 2020-11-30T10:10:20Z | 2024-06-27T11:34:52Z | https://github.com/MonetDB/MonetDB/issues/1961 | 753,341,153 | 1,961 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-20 05:14:49 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-24 11:37:29 +0100
## Comment 11055
Date: 2009-02-20 17:14:49 +0100
From: @romulogoncalves
the Folgewirkung query crashes the mserver:
select id from tables where id not in (select id from columns limit 10);
mserver debug:
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe181f950 (LWP 12655)]
0x0000003830832f05 in raise () from /lib64/libc.so.6
(gdb) up
1 0x0000003830834a73 in abort () from /lib64/libc.so.6
(gdb) up
2 0x000000383082bef9 in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00007fffe26283db in exp_bin (sql=0x7fffe20ac138, e=0x7fffe2108818, left=0x7fffe0f3d208, right=0x7fffe0f6d048, grp=0x0, sel=0x0) at /ufs/goncalve/MonetDB/current/sql/src/server/rel_bin.mx:411
411 assert(0);
(gdb) l
406 is_select = 1;
407 }
408 if (re2)
409 r2 = exp_bin(sql, e->f, left, right, grp, sel);
410 if (!l || !r || (re2 && !r2)) {
411 assert(0);
412 if (l) stmt_destroy(l);
413 if (r) stmt_destroy(r);
414 if (r2) stmt_destroy(r2);
415 return NULL;
(gdb)
## Comment 11056
Date: 2009-02-20 20:38:03 +0100
From: @njnes
the query is not allowed. This is now better enforced in the parser.
Added test to src/test/BugTracker-2009/Tests/limit_in_subquery.SF-2620437.sql
## Comment 11057
Date: 2009-02-24 11:37:29 +0100
From: @njnes
closing
## Comment 11058
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2620437 at http://sourceforge.net/support/tracker.php?aid=2620437
| limit in the subquery | https://api.github.com/repos/MonetDB/MonetDB/issues/1960/comments | 0 | 2020-11-30T10:10:17Z | 2024-06-27T11:34:51Z | https://github.com/MonetDB/MonetDB/issues/1960 | 753,341,120 | 1,960 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-20 12:45:47 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-03-18 02:38:27 +0100
## Comment 11049
Date: 2009-02-20 12:45:47 +0100
From: Jens Oehlschlägel <<jens_oehl>>
This is testing our first 'private' bugreport:
With 600k rows, these are the two most critical statements in the series of 1207 SQLs provided to Stefan and Sjoerd.
859 (20 sec with 600k)
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT MIN(1) as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D02) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReports WHERE ((PostingYear>=2005) AND (PostingYear <= 2006)) GROUP BY PostingYear) as sSub3 GROUP BY KX, PostingYear, PostingStep;
983 (point of crash with 600k, works with freshly restarted server)
SELECT KX, PostingYear, PostingStep, SUM(num1) as sNum1, SUM(den1) as sDen1 FROM ( SELECT Postingsemi as PostingStep, PostingYear, Min('X') as KX, SUM(DT_D02) as num1, MIN(0) as den1 FROM voc.q_SourceKPIReports WHERE (((PostingYear>2005 AND PostingYear<2006) OR (PostingYear=2005 AND Postingsemi>=1) OR (PostingYear=2006 AND Postingsemi<=2))) GROUP BY PostingYear, Postingsemi) as sSub3 GROUP BY KX, PostingYear, PostingStep;
## Comment 11050
Date: 2009-02-24 17:49:41 +0100
From: @drstmane
added original query as test BatAppendUndefined.SF-2633634.sql
added modified query as test BatAppendUndefined.SF-2633634_OK.sql
## Comment 11051
Date: 2009-02-24 17:51:02 +0100
From: @drstmane
please ignore my previous accidental comment
## Comment 11052
Date: 2009-02-24 17:54:32 +0100
From: @drstmane
tests added as
Win32_painpoint_859.SF-2619622.sql
Win32_painpoint_983.SF-2619622.sql
## Comment 11053
Date: 2009-03-18 14:38:27 +0100
From: @drstmane
With the 1.5M test set on our 32-bit Windows XP machine (2.4 GHz Athlon 64 3800+ with 2 GB RAM), query 859 (now) runs in just under 10 secs.
For query 983 see email communication and
[ 2644925 ] crash-points with 1.5M
https://sourceforge.net/tracker/index.php?func=detail&aid=2644925&group_id=56967&atid=482468
## Comment 11054
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2619622 at http://sourceforge.net/support/tracker.php?aid=2619622
| Painpoints under Win32 | https://api.github.com/repos/MonetDB/MonetDB/issues/1959/comments | 0 | 2020-11-30T10:10:14Z | 2024-06-27T11:34:50Z | https://github.com/MonetDB/MonetDB/issues/1959 | 753,341,083 | 1,959 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-17 10:48:33 +0100
From: @drstmane
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2009-02-17 12:11:39 +0100
## Comment 11045
Date: 2009-02-17 10:48:33 +0100
From: @drstmane
year-from-date() & month-from-date() seem to omit leading zeros; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_W3C_use_cases_XQ_R/Q09.out.00.html
In case this is the correct and desired behavior, we should approve the stable output of this test accordingly.
## Comment 11046
Date: 2009-02-17 11:36:42 +0100
From: @lsidir
The return type of these functions is an xs:integer, so I don't see why there should be a leading zero when serialized. So I would have to say that this is the desired and correct behavior.
## Comment 11047
Date: 2009-02-17 12:11:39 +0100
From: @drstmane
Thanks.
approved stable output accoridngly.
## Comment 11048
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2608701 at http://sourceforge.net/support/tracker.php?aid=2608701
| XQ: year-from-date() & month-from-date() omit leading zeros | https://api.github.com/repos/MonetDB/MonetDB/issues/1958/comments | 0 | 2020-11-30T10:10:11Z | 2024-06-28T13:26:55Z | https://github.com/MonetDB/MonetDB/issues/1958 | 753,341,042 | 1,958 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-17 12:26:20 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-20 08:56:44 +0100
## Comment 11040
Date: 2009-02-17 00:26:20 +0100
From: @romulogoncalves
The following sql code in M5-SQL:
create table get_results (schem string, clust string, real_time bigint);
create procedure save_times (schem string, clust string)
BEGIN
insert into get_results select
schem ,
clust ,
id as real_time
from columns order by id limit 1;
delete from callhistory;
END;
call save_times('triples', 'pso');
select * from get_results;
drop ALL procedure save_times;
drop table get_results;
gives the following result:
the result of this code is:
[goncalve@alviss sql]$ mclient stable debug no_algebra sql < test.sql
% sys.get_results, sys.get_results, sys.get_results table_name
% schem, clust, real_time name
% clob, clob, bigint type
% 7, 7, 4 length
[ "triples", "triples", 1063 ]
[goncalve@alviss sql]$
and it should be:
[goncalve@alviss sql]$ mclient stable debug no_algebra sql < test.sql
% sys.get_results, sys.get_results, sys.get_results table_name
% schem, clust, real_time name
% clob, clob, bigint type
% 7, 7, 4 length
[ "triples", "pso", 1063 ]
[goncalve@alviss sql]$
## Comment 11041
Date: 2009-02-17 00:37:05 +0100
From: @romulogoncalves
Test added:
sql/src/test/BugTracker-2009/Tests/insert_into_done_by_procedure.SF-2607293.sql
Note: The delete statement inside the create procedure can be removed, if not you need to load history.sql from sql/src/sql
## Comment 11042
Date: 2009-02-20 20:56:44 +0100
From: @njnes
fixed (test works now)
## Comment 11043
Date: 2009-02-20 20:57:21 +0100
From: @njnes
problem was in the naming of the columns (ie triples and pso both had single_value as name)
## Comment 11044
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2607293 at http://sourceforge.net/support/tracker.php?aid=2607293
| insert into done by procedure | https://api.github.com/repos/MonetDB/MonetDB/issues/1957/comments | 0 | 2020-11-30T10:10:07Z | 2024-06-27T11:34:48Z | https://github.com/MonetDB/MonetDB/issues/1957 | 753,341,002 | 1,957 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-17 12:13:05 +0100
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes
Last updated: 2011-04-28 16:25:35 +0200
## Comment 11032
Date: 2009-02-17 00:13:05 +0100
From: @drstmane
Many geom tests fail;
see overview at
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/index.html
Details:
intended(?) output changes to be approved(?):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/BugTracker/X_crash.SF-1971632.out.00.html
"*** glibc detected *** mserver5: free(): invalid pointer: 0x00007f546d415878 ***"
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/BugTracker/copy_into_crash.SF-1975402.err.00.html
!TypeException:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/basic.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/relation.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/spatial.err.00.html
intended(?) error message changes:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/geom_mbr.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/geom_mbr.err.00.html
## Comment 11033
Date: 2009-02-17 01:16:34 +0100
From: @skinkie
Basically usage of geom in general degraded. For example the example on the website with mbr doesn't work anymore too.
## Comment 11034
Date: 2009-02-17 09:57:24 +0100
From: @drstmane
The we should also consider turning the web site examples into test (in case this has not yet been done).
Stefan,
could you please check, whether tests in geom's CVS tree alrady cover the website example(s), and if so report here, or otherwise share your respective scripts (attached to this bug report or by private mail)?
Thanks!
## Comment 11035
Date: 2009-07-31 14:07:35 +0200
From: @drstmane
Update (1/2):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/BugTracker/X_crash.SF-1971632.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/BugTracker/copy_into_crash.SF-1975402.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/spatial.err.00.html
have been fixed and seem to work fine, again.
## Comment 11036
Date: 2009-07-31 14:08:38 +0200
From: @drstmane
Update (1.5/2):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/geom_mbr.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/geom_mbr.err.00.html
have been fixed and seem to work fine, again.
## Comment 11037
Date: 2009-07-31 14:13:38 +0200
From: @drstmane
Update (2/2):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.64.64.d.1-Fedora10/src_sql/basic.err.00.html
now triggers the additional error message
QUERY = SELECT Dimension(g), GeometryTypeId(g), SRID(g), Envelope(g) FROM geoms where g is not NULL;
ERROR = !MALException:geom.SRID:Failed
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/geom/.mTests103/GNU.6
4.64.d.1-Fedora10/src_sql/relation.err.00.html
now triggers the additional error message
QUERY = SELECT a.g, b.g, Relate(a.g,b.g,'Touches') FROM geoms a, geoms b where a.g is not NULL and b.g is not NULL;
ERROR = !MALException:(unknown):(null)
## Comment 11038
Date: 2009-08-14 14:00:10 +0200
From: @drstmane
tagged subject
## Comment 11039
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2607258 at http://sourceforge.net/support/tracker.php?aid=2607258
Unknown Product GEOM
Using default product set in Parameters
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb4@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 15419
Date: 2011-01-25 14:39:58 +0100
From: @grobian
I actually get this error:
ERROR = !MALException:!ERROR: IllegalArgumentException: IllegalArgumentException: Should be length 9, is [h4.X. ] instead
## Comment 15676
Date: 2011-03-28 17:36:27 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15738
Date: 2011-04-20 14:51:51 +0200
From: @njnes
fixed (properly use string argument)0
## Comment 15747
Date: 2011-04-28 16:25:35 +0200
From: @sjoerdmullender
The Apr2011 release has been uploaded.
| Geom: relation and spatial tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1956/comments | 0 | 2020-11-30T10:10:04Z | 2024-06-27T11:34:47Z | https://github.com/MonetDB/MonetDB/issues/1956 | 753,340,952 | 1,956 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-17 12:02:59 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-08-11 11:08:12 +0200
## Comment 11017
Date: 2009-02-17 00:02:59 +0100
From: @drstmane
Since this checkin
===================================================================
2008/10/25 - mlkersten: MonetDB/src/gdk/gdk_bat.mx,1.204
Most of the changes are related to moving GDKwarning into proper
debugging statements.
The major change is in gdk_utils, where the failure to vtrim does not
lead to a system crash anymore. It is properly retained in the errbuf
for the upper layers to consume.
===================================================================
(cf.,
`cd .../MonetDB &&
cvs diff -r1.20{3,4} src/gdk/gdk_bat.mx`)
BATpropcheck no longer reports incorrect BAT properties as ('!'-prefixed) GDKwarning, but rather as simple ''-prefixed comments.
Since the latter are (for good reasons) ignored by testing (Mdiff), testing does no longer report incorrect BAT properties as detected by BATpropcheck.
Consequently, property errors can silently sneak into tests unnoticed, and have indeed done so, e.g., look for "BATprocheck:" at
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora8/src_test_bugs/rangejoin_optimize_bug.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/pf-O0_produces_wrong_MIL.SF-1771532.out.00.html
## Comment 11018
Date: 2009-02-21 20:12:07 +0100
From: @drstmane
Since correct handling of properties is not that unimportant for MonetDB, I made testing treat property inconsistencies as reported by BATpropcheck as errors, again, regardless of whether BATpropcheck reports them as errors or as comments.
Details to be seen as of tomorrows' testing results.
## Comment 11019
Date: 2009-02-22 09:57:31 +0100
From: @drstmane
see also
[ 2627138 ] SQL: test fails with BATpropcheck error
https://sourceforge.net/tracker/index.php?func=detail&aid=2627138&group_id=56967&atid=482468
and
[ 2627137 ] PF: tests fail with BATpropcheck error
https://sourceforge.net/tracker/index.php?func=detail&aid=2627137&group_id=56967&atid=482468
## Comment 11020
Date: 2009-07-31 21:39:47 +0200
From: @mlkersten
Would it be a solution to mark them as !, which means that the test analysis scripts look a little further.
## Comment 11021
Date: 2009-07-31 22:15:13 +0200
From: @drstmane
Mtest.py / Mfilter.py now recognize BATpropcheck messages in any case and treats them as error.
IMHO, incorrectly set properties are errors, and should hence also be reported as such, in case they are detected, i.e., when property checking is explicitly enabled (e.g., during testing and debugging) ...
## Comment 11022
Date: 2009-07-31 22:59:37 +0200
From: @mlkersten
So, if the Mtest recognizes them and reports them, then this bugreport can be closed.
## Comment 11023
Date: 2009-08-01 06:39:01 +0200
From: @drstmane
What was the actual reason to turn crucial property errors/warning into "harmless" purely informative debug messages?
## Comment 11024
Date: 2009-08-01 08:59:24 +0200
From: @mlkersten
The current source turns all messages into a GDKerror, which is handled like any other error. In particular it means that it is converted into a MALexception. If there is a case where this is not properly done, or not shown properly on the prevalent output stream, we have to investigate it.
## Comment 11025
Date: 2009-08-01 09:38:48 +0200
From: @drstmane
$ grep --color -n 'GDKerror.*BATpropcheck:' MonetDB/src/gdk/gdk_bat.mx
2985: GDKerror("BATpropcheck: BAT %s(%d) set inconsistent hseqbase: " OIDFMT " != " OIDFMT " => " OIDFMT "\n", BATgetId(b), b->batCacheid, b->hseqbase, bm->tseqbase, o);
3014: GDKerror("BATpropcheck: BAT %s(%d) has inconsistent accrefs\n", BATgetId(b), b->batCacheid);
3019: GDKerror("BATpropcheck: BAT %s(%d) recovered hkey\n", BATgetId(b), b->batCacheid);
3023: GDKerror("BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples is dense but not key!?\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3035: GDKerror("BATpropcheck: BAT %s(%d) with "BUNFMT" tuples seqbase of dense oid bat is wrong! " OIDFMT " != " OIDFMT "\n",
BUT:
$ grep --color -n 'THRprintf.*BATpropcheck:' MonetDB/src/gdk/gdk_bat.mx | grep -v 'DEBUG THRprintf'
3282: THRprintf(GDKout, "BATpropcheck: BAT %s(%d): could not allocate hash table for key test\n", BATgetId(b), b->batCacheid);
3369: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was incorrectly marked sorted!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3371: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples remains marked radix-clustered on %d bits; not checked!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b), BAThordered(b) >> 1);
3374: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was incorrectly marked keyed!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3376: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was incorrectly marked nonil!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3379: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was incorrectly marked dense!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3381: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples had incorrect seqbase!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3385: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was not marked sorted!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3387: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was not marked keyed!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
3390: THRprintf(GDKout,"BATpropcheck: BAT %s(%d)[%s,%s] with "BUNFMT" tuples was not marked dense!\n", BATgetId(b), b->batCacheid, ATOMname(b->htype), ATOMname(b->ttype), BATcount(b));
This report (see initial comment) refers to the latter.
## Comment 11026
Date: 2009-08-01 09:44:20 +0200
From: @drstmane
Ok, the last three (lines 3385, 3387, 3390 in revision 1.221 of MonetDB/src/gdk/gdk_bat.mx) are fine as mrerely informative debug messages.
But the others (lines 3282, 3369, 3374, 3376, 3379, 3381 in revision 1.221 of MonetDB/src/gdk/gdk_bat.mx) indicate real error and should IMHO hence be reported/treated as such (again).
## Comment 11027
Date: 2009-08-01 09:49:33 +0200
From: @mlkersten
Propcheck error reporting was/is a mess.
They appear both as
GDKerror("BATpropcheck: BAT %s(....
GDKfatal("BATpropcheck: BAT %s(%d) ...
XPROPDEBUG THRprintf(GDKout,"BATpropcheck: BAT %s
THRprintf(GDKout, "BATpropcheck: BAT ....
I would like to know what is the real semantics.
Mixing debugging information with real error reporting
is/was not a good design.
All debugging statements are marked by which
should be ignored in non-raw mode of the front-ends.
All errors should be marked ! and handled within the
context of their respective interpreters properly.
If the consensus is that propchecks are errors, then
they should all go through GDKerror.
## Comment 11028
Date: 2009-08-01 10:16:21 +0200
From: @grobian
lines starting with are warnings and stored by clients in the warning stack
lines starting with ! are errors and may not be followed by other content (e.g. an error is fatal)
## Comment 11029
Date: 2009-08-01 10:33:44 +0200
From: @drstmane
Ok, I'm slowly getting the rational of the original changes --- I guess ...
(i.e., in case the client indeed considers all errors as fatal and does/can not distinguish between debugging messages and warnings ...)
... let's analyse and fix this in detail "live" on Monday.
## Comment 11030
Date: 2009-08-11 11:08:12 +0200
From: @drstmane
Thanks to Martin, incorrectly set properties are now reported as errors, again.
## Comment 11031
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2607229 at http://sourceforge.net/support/tracker.php?aid=2607229
| testing does not report detected property errors | https://api.github.com/repos/MonetDB/MonetDB/issues/1955/comments | 0 | 2020-11-30T10:10:00Z | 2024-06-27T11:34:46Z | https://github.com/MonetDB/MonetDB/issues/1955 | 753,340,906 | 1,955 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 10:54:36 +0100
From: @romulogoncalves
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2009-08-17 02:18:16 +0200
## Comment 11010
Date: 2009-02-16 22:54:36 +0100
From: @romulogoncalves
The following SQL code crashes M5-SQL
set history='true';
select id from tables where id > 0;
create table t1 (id int);
drop table t1;
mserver debug info:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe0f05950 (LWP 5796)]
0x00000038308830b3 in memset () from /lib64/libc.so.6
(gdb) up
1 0x00007ffff771eea1 in GDKfree (blk=0x7fffe5600ca4)
at /ufs/goncalve/MonetDB/stable/MonetDB/src/gdk/gdk_utils.mx:1135
1135 DEADBEEFCHK memset(s, 0xDB, size - (8 + (size & 1))); /* 0xDeadBeef */
(gdb) p size
$1 = 28549272340070512
(gdb) p s
$2 = (ssize_t *) 0x7fffe5600ca4
(gdb) p 0xDB
$3 = 219
(gdb) up
2 0x0000000000c8ace4 in clearVariable (mb=0x7fffe0664fa8, varid=98)
at /ufs/goncalve/MonetDB/stable/MonetDB5/src/mal/mal_instruction.mx:1557
1557 GDKfree(v->name);
(gdb) p v->name
$4 = 0x7fffe5600ca4 "ctime"
(gdb)
## Comment 11011
Date: 2009-02-16 23:38:47 +0100
From: @romulogoncalves
test added to
sql/src/tests/BugTracker-2009/Tests/set_history_and_drop_table.SF-2607045.SQL.py
with additional files:
sql/src/tests/BugTracker-2009/set_history_and_drop_table.SF-2607045.sql
sql/src/tests/BugTracker-2009/drop_history.sql
## Comment 11012
Date: 2009-02-20 23:38:22 +0100
From: @njnes
works now. was a bug in m5 opt_history. variable names need to be allocated
## Comment 11013
Date: 2009-08-13 19:20:25 +0200
From: @drstmane
re-opened since the test produces different output since checkins on 2009/07/25 and/or 2009/07/26 on the CVS HEAD;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/set_history_and_drop_table.SF-2607045.out.00.html
## Comment 11014
Date: 2009-08-14 13:55:57 +0200
From: @drstmane
tagged subject
## Comment 11015
Date: 2009-08-17 14:18:16 +0200
From: @drstmane
new output has been approved by Niels.
## Comment 11016
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2607045 at http://sourceforge.net/support/tracker.php?aid=2607045
| SQL: set history and drop table | https://api.github.com/repos/MonetDB/MonetDB/issues/1954/comments | 0 | 2020-11-30T10:09:56Z | 2024-06-27T11:34:45Z | https://github.com/MonetDB/MonetDB/issues/1954 | 753,340,857 | 1,954 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 04:59:12 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-07 03:34:09 +0200
## Comment 10999
Date: 2009-02-16 16:59:12 +0100
From: @skinkie
In order to let BenchmarkSQL to work, I had to modify the test from Decimal(4,4) to Float in the create table statements. When running the loadSQL.sh code with the following configuration:
monetdb-jdbc.properties:
driver=nl.cwi.monetdb.jdbc.MonetDriver
conn=jdbc:monetdb://localhost/demo?user=monetdb&password=monetdb&debug=true
user=monetdb
password=monetdb
At a certain moment when executing EXEC with its PREPARE statement, ROLLBACK warnings occur.
PREPARE INSERT INTO item (i_id, i_name, i_price, i_data, i_im_id) VALUES (?, ?, ?, ?, ?);
TX 1234798982371: sexec 2(22001, 'jvrRZibeQvUYlNcsAZ', 50.689998626708984, 'pYeGnMiVfmWoUBbVjgoPiPueMBVTxnImYXHbBNkyVBmI', 8936);
....
RD 1234798982597: read final block: 3950 bytes
RX 1234798982597: !current transaction is aborted (please ROLLBACK)
I have ran valgrind on the mserver5 process which resulted in:
>==16992== Thread 5:
==16992== Syscall param write(buf) points to uninitialised byte(s)
==16992== at 0x6AF37FB: (within /lib64/libpthread-2.9.so)
==16992== by 0x5DA716E: GDKsave (gdk_storage.mx:284)
==16992== by 0x5B55694: HEAPsave (gdk_heap.mx:383)
==16992== by 0x5DA93D9: BATsave (gdk_storage.mx:559)
==16992== by 0x5B52DBD: BBPsync (gdk_bbp.mx:3133)
==16992== by 0x5B3C78F: TMsubcommit (gdk_tm.mx:189)
==16992== by 0x5EC467D: bm_subcommit (gdk_logger.mx:1011)
==16992== by 0x5EC772B: bm_commit (gdk_logger.mx:1735)
==16992== by 0x5EC3A24: logger_commit (gdk_logger.mx:949)
==16992== by 0x5EC5405: logger_exit (gdk_logger.mx:1226)
==16992== by 0x5EC551A: logger_restart (gdk_logger.mx:1253)
==16992== by 0x18C1F193: bl_restart (bat_logger.mx:64)
==16992== Address 0x1c1e4441 is 8,353 bytes inside a block of size 20,504 alloc'd
==16992== at 0x4C2467E: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==16992== by 0x5C1710D: GDKmallocmax (gdk_utils.mx:1062)
==16992== by 0x5C172AA: GDKmalloc (gdk_utils.mx:1085)
==16992== by 0x5DA73EE: GDKload (gdk_storage.mx:330)
==16992== by 0x5B5550B: HEAPload (gdk_heap.mx:341)
==16992== by 0x5DA9AE0: BATload_intern (gdk_storage.mx:643)
==16992== by 0x5B4B849: BBPdescriptor (gdk_bbp.mx:1864)
==16992== by 0x18C1F812: BATdescriptor (gdk.h:1324)
==16992== by 0x18C1F786: temp_descriptor (bat_utils.mx:123)
==16992== by 0x18C1EC76: tr_snapshot_bat (bat_storage.mx:1405)
==16992== by 0x18C1EDB8: snapshot_table (bat_storage.mx:1434)
==16992== by 0x18C11EE5: rollforward_update_table (store.mx:2289)
## Comment 11000
Date: 2009-02-16 17:55:52 +0100
From: @grobian
Please post enough information such that others can reproduce your problem. What makes you think this is a GDK issue? Why not just "When batch executing prepared statements, the server reports current transaction is aborted after a random amount of statements with no previous error message"?
## Comment 11001
Date: 2009-02-16 19:28:00 +0100
From: @skinkie
Who) Me
What) BenchmarkSQL on Java 1.5 fails
When) When running loadSQL code
Where) AMD64
Why) Because there is a memory problem in GDK
How) Running the loadSQL.sh program
I think all these questions were answered in the report. Because your summery does not describe the section where the issue is present. Thus your summary related to the actual knowledge that was gathered is incomplete.
## Comment 11002
Date: 2009-02-16 19:31:08 +0100
From: @grobian
I think someone else will still be in the neighbourhood of clueless with your given instructions on how to reproduce your problem.
## Comment 11003
Date: 2009-02-16 19:34:12 +0100
From: @mlkersten
Valgrind only reports about accessing non-initialized information here.
And this access to non-initialized buffer space is known and safe.
To detect and claim memory leaks in GDK you have to run
valgrind --leak-check=full --show-reachable=yes --num-callers=20 mserver5 --dbfarm=$DBFARM --dbname=$DBNAME
## Comment 11004
Date: 2009-02-16 19:48:54 +0100
From: @skinkie
Elasped Time(ms): 4.089 Writing record 41000 of 100000
Error(s) occurred while executing the batch, see next SQLExceptions for details
Start District Data for 10 Dists @ Mon Feb 16 19:45:22 CET 2009 ...
current transaction is aborted (please ROLLBACK)
Start Cust-Hist Load for 60000 Cust-Hists @ Mon Feb 16 19:45:22 CET 2009 ...
Elasped Time(ms): 2.78 Writing record 1000 of 60000
Error(s) occurred while executing the batch, see next SQLExceptions for details
whse=1, dist=10, cust=3000
Start Order-Line-New Load for approx 340000 rows @ Mon Feb 16 19:45:24 CET 2009
...
Elasped Time(ms): 1.461 Writing record 2000 of 340000
java.sql.BatchUpdateException: Error(s) occurred while executing the batch, see
next SQLExceptions for details
at nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(MonetStatement.java:2
06)
at LoadData.loadOrder(LoadData.java:1072)
at LoadData.main(LoadData.java:113)
>==17410== Thread 5:
==17410== Syscall param msync(start) points to uninitialised byte(s)
==17410== at 0x6AF410B: (within /lib64/libpthread-2.9.so)
==17410== by 0x5EC0BD7: MT_msync (gdk_posix.mx:1101)
==17410== by 0x5DA70A2: GDKsave (gdk_storage.mx:274)
==17410== by 0x5B55694: HEAPsave (gdk_heap.mx:383)
==17410== by 0x5B54963: HEAPextend (gdk_heap.mx:157)
==17410== by 0x5C20E68: strPut (gdk_atoms.mx:2075)
==17410== by 0x5AF12FC: BATappend (gdk_batop.mx:371)
==17410== by 0x18C1DFE3: tr_update_delta (bat_storage.mx:1189)
==17410== by 0x18C1E572: update_table (bat_storage.mx:1277)
==17410== by 0x18C11FD5: rollforward_update_table (store.mx:2299)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C123B3: rollforward_update_schema (store.mx:2372)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C12551: rollforward_trans (store.mx:2394)
==17410== by 0x18C13669: sql_trans_commit (store.mx:2768)
==17410== by 0x18BD693B: mvc_commit (sql_mvc.mx:443)
==17410== by 0x18BAEC67: transactions (sql_trans.mx:65)
==17410== by 0x18BBAC3E: semantic (sql_semantic.mx:1005)
==17410== by 0x18BBAD89: output_semantic (sql_semantic.mx:1094)
==17410== by 0x18B579F5: sql_symbol2stmt (sql.mx:1094)
==17410== Address 0x1c254fe6 is 2,490,342 bytes inside a block of size 3,276,800 alloc'd
==17410== at 0x5C17B16: GDKmmap (gdk_utils.mx:1266)
==17410== by 0x5DA7668: GDKload (gdk_storage.mx:376)
==17410== by 0x5B5550B: HEAPload (gdk_heap.mx:341)
==17410== by 0x5B54D19: HEAPextend (gdk_heap.mx:199)
==17410== by 0x5C20E68: strPut (gdk_atoms.mx:2075)
==17410== by 0x5AF12FC: BATappend (gdk_batop.mx:371)
==17410== by 0x18C1DFE3: tr_update_delta (bat_storage.mx:1189)
==17410== by 0x18C1E572: update_table (bat_storage.mx:1277)
==17410== by 0x18C11FD5: rollforward_update_table (store.mx:2299)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C123B3: rollforward_update_schema (store.mx:2372)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C12551: rollforward_trans (store.mx:2394)
==17410== by 0x18C13669: sql_trans_commit (store.mx:2768)
==17410== by 0x18BD693B: mvc_commit (sql_mvc.mx:443)
==17410== by 0x18BAEC67: transactions (sql_trans.mx:65)
==17410== by 0x18BBAC3E: semantic (sql_semantic.mx:1005)
==17410== by 0x18BBAD89: output_semantic (sql_semantic.mx:1094)
==17410== by 0x18B579F5: sql_symbol2stmt (sql.mx:1094)
==17410== by 0x18B9323A: SQLparser (sql_scenario.mx:1013)
>==17410==
==17410== Thread 4:
==17410== Syscall param write(buf) points to uninitialised byte(s)
==17410== at 0x6AF37FB: (within /lib64/libpthread-2.9.so)
==17410== by 0x5DA716E: GDKsave (gdk_storage.mx:284)
==17410== by 0x5B55694: HEAPsave (gdk_heap.mx:383)
==17410== by 0x5DA93D9: BATsave (gdk_storage.mx:559)
==17410== by 0x5B52DBD: BBPsync (gdk_bbp.mx:3133)
==17410== by 0x5B3C78F: TMsubcommit (gdk_tm.mx:189)
==17410== by 0x5EC467D: bm_subcommit (gdk_logger.mx:1011)
==17410== by 0x5EC772B: bm_commit (gdk_logger.mx:1735)
==17410== by 0x5EC3A24: logger_commit (gdk_logger.mx:949)
==17410== by 0x5EC5405: logger_exit (gdk_logger.mx:1226)
==17410== by 0x5EC551A: logger_restart (gdk_logger.mx:1253)
==17410== by 0x18C1F193: bl_restart (bat_logger.mx:64)
==17410== by 0x18C0F5AF: store_manager (store.mx:1435)
==17410== by 0x18BD64D5: mvc_logmanager (sql_mvc.mx:342)
==17410== by 0x5EC05E7: wrapper_routine (gdk_posix.mx:940)
==17410== by 0x6AED006: start_thread (in /lib64/libpthread-2.9.so)
==17410== by 0x7A1938C: clone (in /lib64/libc-2.9.so)
==17410== Address 0x16295119 is 8,377 bytes inside a block of size 20,504 alloc'd
==17410== at 0x4C2467E: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==17410== by 0x5C1710D: GDKmallocmax (gdk_utils.mx:1062)
==17410== by 0x5C172AA: GDKmalloc (gdk_utils.mx:1085)
==17410== by 0x5DA73EE: GDKload (gdk_storage.mx:330)
==17410== by 0x5B5550B: HEAPload (gdk_heap.mx:341)
==17410== by 0x5DA9AE0: BATload_intern (gdk_storage.mx:643)
==17410== by 0x5B4B849: BBPdescriptor (gdk_bbp.mx:1864)
==17410== by 0x18C1F812: BATdescriptor (gdk.h:1324)
==17410== by 0x18C1F786: temp_descriptor (bat_utils.mx:123)
==17410== by 0x18C1EC76: tr_snapshot_bat (bat_storage.mx:1405)
==17410== by 0x18C1EDB8: snapshot_table (bat_storage.mx:1434)
==17410== by 0x18C11EE5: rollforward_update_table (store.mx:2289)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C123B3: rollforward_update_schema (store.mx:2372)
==17410== by 0x18C10FB6: rollforward_changeset_updates (store.mx:1941)
==17410== by 0x18C12551: rollforward_trans (store.mx:2394)
==17410== by 0x18C135AE: sql_trans_commit (store.mx:2751)
==17410== by 0x18BD693B: mvc_commit (sql_mvc.mx:443)
==17410== by 0x18BAEC67: transactions (sql_trans.mx:65)
==17410== by 0x18BBAC3E: semantic (sql_semantic.mx:1005)
>
## Comment 11005
Date: 2009-02-16 23:10:40 +0100
From: @skinkie
For everyone (from cwi) that would like to reproduce this thing; on loki in /tmp/benchmark.tar.bz2 can be found.
- create a demo database
- extract this file
- cd run
- sh runSQL.sh sqlTableCreates (some expected trunkcate fails)
- sh loadData.sh monetdb-jdbc.properties
Be VERY sure you run this code with Java 1.5; 1.6 fails.
--
Something that I found out too...
==17410== 31,896 (11,752 direct, 20,144 indirect) bytes in 242 blocks are definitely lost in loss record 28 of 33
==17410== at 0x4C2467E: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==17410== by 0x5C1710D: GDKmallocmax (gdk_utils.mx:1062)
==17410== by 0x5C172AA: GDKmalloc (gdk_utils.mx:1085)
==17410== by 0x5C17864: GDKstrdup (gdk_utils.mx:1235)
==17410== by 0x5E873E8: VALcopy (gdk_value.mx:162)
==17410== by 0x4E49D30: callMAL (mal_interpreter.mx:221)
==17410== by 0x18B93A9A: SQLexecutePrepared (sql_scenario.mx:1185)
==17410== by 0x18B93D0F: SQLengineIntern (sql_scenario.mx:1238)
==17410== by 0x18B941E2: SQLengine (sql_scenario.mx:1348)
==17410== by 0x4E83ACB: runPhase (mal_scenario.mx:591)
==17410== by 0x4E83C5E: runScenarioBody (mal_scenario.mx:636)
==17410== by 0x4E83DF8: runScenario (mal_scenario.mx:661)
==17410== by 0x4E47CCA: MSserveClient (mal_session.mx:459)
==17410== by 0x5EC05E7: wrapper_routine (gdk_posix.mx:940)
==17410== by 0x6AED006: start_thread (in /lib64/libpthread-2.9.so)
==17410== by 0x7A1938C: clone (in /lib64/libc-2.9.so)
--
I have also created a different test build from the queries that are actually inserted. This can be found as /tmp/prepare-exec.tar.bz2 on loki. This creates a list with:
MAPI = monetdb@localhost:50000
QUERY = exec 1(4640, 'HQiudJRsmjTrvpyVnOym', 41.880001068115234, 'dwkXYLpgwwZxSuCGDWMoqiCLegJfKXUykvkRvevmfEt', 9335)
ERROR = !no prepared statement with the given id
(exec 0..8 were defined)
The thing is, that these inserts in mclient do not create the previously issued valgrind traces. Then again, they do not rollback...
## Comment 11006
Date: 2009-02-20 23:36:34 +0100
From: @njnes
the problem is that monetdb drops prepare statements after a commit. The benchmark script uses commits, but expects the prepares to still exist.
## Comment 11007
Date: 2009-03-04 03:16:23 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: cimballi@users.sourceforge.net ----
Hi,
I confirm we have the same problem. We try to bulk import 100 000 items in the database using the JDBC driver (and iBatis), and nearly everytime I have this error :
java.sql.SQLException: current transaction is aborted (please ROLLBACK)
Cimballi
## Comment 11008
Date: 2009-08-07 15:34:09 +0200
From: @njnes
added test prepare_commit_execute.SF-2606020
Fixed by introducing a query cache just for prepares/execute queries
## Comment 11009
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2606020 at http://sourceforge.net/support/tracker.php?aid=2606020
| BenchmarkSQL fails loading due to sudden transaction abort | https://api.github.com/repos/MonetDB/MonetDB/issues/1953/comments | 0 | 2020-11-30T10:09:52Z | 2024-06-27T11:34:44Z | https://github.com/MonetDB/MonetDB/issues/1953 | 753,340,793 | 1,953 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 03:15:39 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-03-26 03:47:16 +0100
## Comment 10996
Date: 2009-02-16 15:15:39 +0100
From: @grobian
When using monetdb(1) to stop a running database under Merovingian, the latter may segfault. Race conditions due to multiple threads working on shared linked lists may cause the lists go foobared. The solution is to properly regulate access to the shared structures.
## Comment 10997
Date: 2009-02-16 15:18:57 +0100
From: @grobian
merovingian now uses proper locking around access/modification to shared structures.
## Comment 10998
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2605706 at http://sourceforge.net/support/tracker.php?aid=2605706
| Merovingian: random crash when stopping database | https://api.github.com/repos/MonetDB/MonetDB/issues/1952/comments | 0 | 2020-11-30T10:09:49Z | 2024-06-27T11:34:43Z | https://github.com/MonetDB/MonetDB/issues/1952 | 753,340,753 | 1,952 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 03:08:34 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-02-16 11:08:59 +0100
## Comment 10993
Date: 2009-02-16 15:08:34 +0100
From: @skinkie
create table test(test decimal(4,4));
!scale (4) should be less than precision (4) in: "create table test(test decimal(4,4)"
!syntax error, unexpected ')' in: ")"
Not known if this is an SQL bug.
----------
create table test(test decimal(5,4));
insert into test values (0.12345);
select * from test;
---> 0.1235 (as expected)
(restart mclient)
PREPARE INSERT INTO test (test) values (?);
exec 2(0.12345);
!SQLException:sql.prepare:wrong argument for prepared statement (expected decimal instead of decimal)
## Comment 10994
Date: 2009-02-16 23:08:59 +0100
From: @njnes
fixed handling of decimal2decimal casting in atom_cast, it now truncates. Added a test decimal_needs_truncation.SF-2605686.sql
## Comment 10995
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2605686 at http://sourceforge.net/support/tracker.php?aid=2605686
| decimals / exec doesn't truncate decimals | https://api.github.com/repos/MonetDB/MonetDB/issues/1951/comments | 0 | 2020-11-30T10:09:46Z | 2024-06-27T11:34:42Z | https://github.com/MonetDB/MonetDB/issues/1951 | 753,340,713 | 1,951 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 11:52:21 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-03-26 03:47:44 +0100
## Comment 10991
Date: 2009-02-16 11:52:21 +0100
From: @grobian
stopping a database that is already stopped causes monetdb(1) to crash:
(pegasus:~/files/release) fabian% $INSTALL_DIR/bin/monetdb stop octopus_one
Segmentation fault
## Comment 10992
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2605105 at http://sourceforge.net/support/tracker.php?aid=2605105
| monetdb: crash when stopping stopped database | https://api.github.com/repos/MonetDB/MonetDB/issues/1950/comments | 0 | 2020-11-30T10:09:43Z | 2024-06-27T11:34:41Z | https://github.com/MonetDB/MonetDB/issues/1950 | 753,340,681 | 1,950 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 07:35:53 +0100
From: z lh <<zlh>>
To: @njnes
Version: -- development
Last updated: 2009-02-20 11:32:21 +0100
## Comment 10984
Date: 2009-02-16 07:35:53 +0100
From: z lh <<zlh>>
--the count() return null while expect 0
create table t1( a int , b int ) ;
insert into t1 values ( 3, 1 ) , ( 4, 2 ) , ( 5, 3 ) , ( 6, 4 ) , ( 7, 5 ) ;
select * from t1;
select ( select count( * )+1
from t1 as tt3
where tt3.b < tt2.b )
from t1 as tt2 ;
---------------------------------
--the result : the last SQL should returns 1,2,3,4,5 , not null,2,3,4,5
sql>create table t1( a int , b int ) ;
0 tuples
sql>insert into t1 values ( 3, 1 ) , ( 4, 2 ) , ( 5, 3 ) , ( 6, 4 ) , ( 7, 5 ) ;
Rows affected 5
sql>
0 tuples
sql>select * from t1;
+---+---+
| a | b |
+===+===+
| 3 | 1 |
| 4 | 2 |
| 5 | 3 |
| 6 | 4 |
| 7 | 5 |
+---+---+
5 tuples
sql>select ( select count( * )+1
more> from t1 as tt3
more> where tt3.b < tt2.b )
more>from t1 as tt2 ;
+-----------------+
| sql_add_count_b |
+=================+
| null |
| 2 |
| 3 |
| 4 |
| 5 |
+-----------------+
5 tuples
## Comment 10985
Date: 2009-02-16 08:08:41 +0100
From: @drstmane
zlh,
could you please indicate, which version of MonetDB you are using,
e.g., by selecting either 'SQL CVS Head' or 'SQL "stable"' as 'Group" for this bug report,
and providing the output of `mserver5 --version`.
Thanks!
## Comment 10986
Date: 2009-02-16 14:29:52 +0100
From: z lh <<zlh>>
the version Nov-SP2, and there is also the bug before the version
[zlh@localhost ~]$ /home/zlh/MonetDB_nov_sp2/MonetDB/bin/mserver5 --dbinit
'include sql;' --dbname test
MonetDB server v5.8.4, based on kernel v1.26.4
Serving database 'test', using 2 threads
Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008- MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /home/zlh/MonetDB_nov_sp2/MonetDB/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.26.4 loaded
>
## Comment 10987
Date: 2009-02-16 22:09:57 +0100
From: @njnes
on the current stable the results are different (2,2,3,4,5). The first 2 seems wrong (not sure though).
When we change the count(*) into a count(tt3.b), we get the correct (1,2,3,4,5).
## Comment 10988
Date: 2009-02-17 13:48:20 +0100
From: @njnes
Added test count_bug.SF-2604583. Fixed we properly count the expressions result (sql sub-execute-semantics)
## Comment 10989
Date: 2009-02-20 23:32:21 +0100
From: @njnes
test works fine now
## Comment 10990
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2604583 at http://sourceforge.net/support/tracker.php?aid=2604583
| the count() return null while expect 0 | https://api.github.com/repos/MonetDB/MonetDB/issues/1949/comments | 0 | 2020-11-30T10:09:39Z | 2024-06-27T11:34:40Z | https://github.com/MonetDB/MonetDB/issues/1949 | 753,340,641 | 1,949 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 07:31:28 +0100
From: z lh <<zlh>>
To: @njnes
Version: -- development
Last updated: 2009-02-20 11:34:49 +0100
## Comment 10978
Date: 2009-02-16 07:31:28 +0100
From: z lh <<zlh>>
--error while drop the function which returns table_type ,
--test case: create a new database , then run the SQLs
create function test_002() returns table(i int)
begin
create table tbl(i int);
insert into tbl values(110);
insert into tbl values(210);
return tbl;
end;
select * from test_002();
drop function test_002;
create function test_002() returns table( j char(20) )
begin
create table tbl( j char(20) );
insert into tbl values( 'aaa' );
insert into tbl values( 'bbb' );
return tbl;
end;
select * from test_002();
-------------------------------------
the result : after drop the function test_002, can't create/use the funtion test_002
sql>--create a new database
0 tuples
sql>create function test_002() returns table(i int)
more>begin
more>create table tbl(i int);
more>insert into tbl values(110);
more>insert into tbl values(210);
more>return tbl;
more>end;
0 tuples
sql>select * from test_002();
Rows affected 1
Rows affected 1
+-----+
| i |
+=====+
| 110 |
| 210 |
+-----+
2 tuples
sql>
0 tuples
sql>drop function test_002;
0 tuples
sql>create function test_002() returns table( j char(20) )
more>begin
more>create table tbl( j char(20) );
more>insert into tbl values( 'aaa' );
more>insert into tbl values( 'bbb' );
more>return tbl;
more>end;
0 tuples
sql>select * from test_002();
Rows affected 1
Rows affected 1
!SQLException:int:conversion of string 'aaa' failed
0 tuples
## Comment 10979
Date: 2009-02-16 08:09:05 +0100
From: @drstmane
zlh,
could you please indicate, which version of MonetDB you are using,
e.g., by selecting either 'SQL CVS Head' or 'SQL "stable"' as 'Group" for this bug report,
and providing the output of `mserver5 --version`.
Thanks!
## Comment 10980
Date: 2009-02-16 12:06:58 +0100
From: z lh <<zlh>>
the version Nov-SP2, and there is also the bug before the version
[zlh@localhost ~]$ /home/zlh/MonetDB_nov_sp2/MonetDB/bin/mserver5 --dbinit 'include sql;' --dbname test
MonetDB server v5.8.4, based on kernel v1.26.4
Serving database 'test', using 2 threads
Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008- MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /home/zlh/MonetDB_nov_sp2/MonetDB/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.26.4 loaded
>
## Comment 10981
Date: 2009-02-17 00:55:39 +0100
From: @romulogoncalves
test added at:
sql/src/test/BugTracker-2009/Tests/error_while_drop_func_returns_table_type.SF-2604573.sql
## Comment 10982
Date: 2009-02-20 23:34:49 +0100
From: @njnes
fixed, the return type should be removed from the catalogs too.
## Comment 10983
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2604573 at http://sourceforge.net/support/tracker.php?aid=2604573
| error while drop the function which returns table_type | https://api.github.com/repos/MonetDB/MonetDB/issues/1948/comments | 0 | 2020-11-30T10:09:35Z | 2024-06-27T11:34:39Z | https://github.com/MonetDB/MonetDB/issues/1948 | 753,340,588 | 1,948 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-16 01:00:00 +0100
From: @drstmane
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2009-06-16 10:38:28 +0200
## Comment 10971
Date: 2009-02-16 01:00:00 +0100
From: @drstmane
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/put_to_tmp.SF-1718066.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/interleave_PUT_GET_crashes_Mserver.SF-1676443.err.00.html
## Comment 10972
Date: 2009-02-16 10:10:00 +0100
From: @lsidir
I fixed the seq. fault, but the implementation of fn:put is missing.
## Comment 10973
Date: 2009-02-17 10:07:45 +0100
From: @drstmane
[ in the Feb2009 release branch, only ]
Conditionally disabled tests in pathfinder/tests/BugTracker/Tests/All that require fn:put()
and are hence bound to fail with the Algebra back-end
as long as it does not yet support fn:put().
Please re-enable them in case fn:put() gets "fixed" in the Feb2009 release branch.
## Comment 10974
Date: 2009-04-07 14:56:17 +0200
From: @peterboncz
hi lefteris, any progress with fn:put()? thx
## Comment 10975
Date: 2009-06-16 10:38:27 +0200
From: @lsidir
I am closing this bug since it is not the case any more, fn:put does not produces segmentation fault.
## Comment 10976
Date: 2009-06-16 11:07:30 +0200
From: @drstmane
Fine with me.
Just for completeness, it now triggers an error message, saying that fn:put is not (yet?) avialable with the Algebra back-end:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/put_to_tmp.SF-1718066.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/interleave_PUT_GET_crashes_Mserver.SF-1676443.err.00.html
## Comment 10977
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2603876 at http://sourceforge.net/support/tracker.php?aid=2603876
| XQ: fn:put() tests segfault with ALG back-end | https://api.github.com/repos/MonetDB/MonetDB/issues/1947/comments | 0 | 2020-11-30T10:09:33Z | 2024-06-27T11:34:38Z | https://github.com/MonetDB/MonetDB/issues/1947 | 753,340,549 | 1,947 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-15 01:33:47 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2009-08-06 09:42:25 +0200
## Comment 10967
Date: 2009-02-15 13:33:47 +0100
From: @mlkersten
The stress test for the release involves running the
TPC-H tests. It turns out that in the current code
there are intermittent errors when you alter the
database after bulk loading.
## Comment 10968
Date: 2009-02-15 22:14:44 +0100
From: @mlkersten
The problems seem to occur when you perform some batched queries directly against the mserver5 console. It may be a thread interference, which causes the environment of the main thread to be reset before all are done.
## Comment 10969
Date: 2009-08-06 21:42:25 +0200
From: @njnes
fixed by data corruption fix. Test for this data corruption will be done later. We can already close this bug
## Comment 10970
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2602550 at http://sourceforge.net/support/tracker.php?aid=2602550
| SQL: tpc-h sf-1 gives intermittent errors | https://api.github.com/repos/MonetDB/MonetDB/issues/1946/comments | 0 | 2020-11-30T10:09:30Z | 2024-06-27T11:34:37Z | https://github.com/MonetDB/MonetDB/issues/1946 | 753,340,518 | 1,946 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-13 03:32:28 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-04-02 11:06:53 +0200
## Comment 10961
Date: 2009-02-13 15:32:28 +0100
From: Jens Oehlschlägel <<jens_oehl>>
POWER does not recognize tuning opportunities with certain constant integer exponents.
Oberved under Win32 Feb2009Alpha
Replication and demonstration of speed potential attached.
## Comment 10962
Date: 2009-02-13 17:14:10 +0100
From: @mlkersten
Indeed, power(x,2) is not replaced by x *x, which is btw often down within the function itself
and you only safe the functionc all overhead.
The real issue is that power(:bat[:oid,:flt],:flt):bat[:oid,:dbl]
is missing in batmath.mx
Fix pending.
## Comment 10963
Date: 2009-02-14 06:22:23 +0100
From: @mlkersten
The naming convention for the multiplex variants [bat]mmath
where not obeyed. This made the remap optimizer not aware
of the existence of fast math function implementations.
no test needed.
## Comment 10964
Date: 2009-02-14 10:46:35 +0100
From: @drstmane
re-opened to remind me that I want to add a test after all ...
## Comment 10965
Date: 2009-04-02 23:06:53 +0200
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.*
## Comment 10966
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2596114 at http://sourceforge.net/support/tracker.php?aid=2596114
| POWER(x,2) by factor 100 slower than x*x; | https://api.github.com/repos/MonetDB/MonetDB/issues/1945/comments | 0 | 2020-11-30T10:09:27Z | 2024-06-27T11:34:36Z | https://github.com/MonetDB/MonetDB/issues/1945 | 753,340,490 | 1,945 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-13 03:23:38 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-13 09:58:42 +0100
## Comment 10958
Date: 2009-02-13 15:23:38 +0100
From: Jens Oehlschlägel <<jens_oehl>>
AVG does not return records when combined with certain other aggregation fucntions. Context: tried to calculate a 2-pass standard deviation where AVG and COUNT are determined in a subquery.
Under Feb2009Alpha Win32
Replication and some suggestions for test automation attached.
## Comment 10959
Date: 2009-02-13 21:58:42 +0100
From: @njnes
fixed a bug in rel_name (caused the avg rewrite to fail). Test added to BugTracker-2009
## Comment 10960
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2596084 at http://sourceforge.net/support/tracker.php?aid=2596084
| AVG returns no lines | https://api.github.com/repos/MonetDB/MonetDB/issues/1944/comments | 0 | 2020-11-30T10:09:24Z | 2024-06-27T11:34:35Z | https://github.com/MonetDB/MonetDB/issues/1944 | 753,340,453 | 1,944 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-12 04:53:26 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-12 10:59:22 +0100
## Comment 10955
Date: 2009-02-12 16:53:26 +0100
From: Jens Oehlschlägel <<jens_oehl>>
-- scary in Feb2009Alpha Win32
CREATE TABLE div0 (
x DOUBLE
, y DOUBLE
)
;
INSERT INTO div0 VALUES (1,0);
INSERT INTO div0 VALUES (1,0);
INSERT INTO div0 VALUES (2,1);
INSERT INTO div0 VALUES (2,1);
SELECT MIN(x2) AS x3, SUM(y2) AS y3
FROM (
SELECT x as x2, SUM(y) as y2
FROM div0
GROUP BY x
HAVING SUM(y)>0 -- now y2 should always >0
) as Sub
WHERE y2/y2 < 0 -- but here we get a division by zero
GROUP BY x2
;
-- gives erroneously
-- !ArithmeticException:batcalc./:Division by zero
-- also from a performance perspective
-- we want to filter HAVING as soon as possible
## Comment 10956
Date: 2009-02-12 22:59:22 +0100
From: @njnes
test added to BugTracker-2009.
Optimizer pushed the select y2/y2 to the same level as the having and executed even earlier. Fix now by disallowing push down of selects with 'unsafe' functions.
## Comment 10957
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2593341 at http://sourceforge.net/support/tracker.php?aid=2593341
| HAVING filters too late => division by zero | https://api.github.com/repos/MonetDB/MonetDB/issues/1943/comments | 0 | 2020-11-30T10:09:21Z | 2024-06-27T11:34:34Z | https://github.com/MonetDB/MonetDB/issues/1943 | 753,340,419 | 1,943 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-10 07:47:00 +0100
From: Wouter Alink <<alink>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2009-03-24 12:13:25 +0100
## Comment 10928
Date: 2009-02-10 19:47:00 +0100
From: Wouter Alink <<alink>>
(monetdb nov2008 sp2 on Linux)
The following occurred:
walink@ldc:~/tmp> xmlwf tmp.xml content is well-formed
walink@ldc:~/tmp> cat tmp.xml | mclient -lxq -I oops5.xml
MAPI = monetdb@localhost:50000
ACTION= mapi_stream_into
ERROR = !ERROR: Detected an entity reference loop
!ERROR: shredder_parse: XML input not well-formed.
!ERROR: CMDshred_stream: operation failed.
walink@ldc:~/tmp>
What happened is that there is a text-node in tmp.xml which contains more than 8M characters.
In shred_characters() in shredder.mx the maximum text content buffer size is set at 8M (1<<23). It ignores everything after the 8Mth character. If the 8Mth character is in the middle of an entity (like """), then the error above is returned.
I was able to reproduce a document with the features described above using the following python script:
walink@ldc:~/tmp> cat createLargeTextField.py
i=0
print "<aap>"
while i < 10000000:
print '"'
i+=1
print "</aap>"
walink@ldc:~/tmp> python createLargeTextField.py > tmp.xml
p.s. another issue, not really a bug, is that for each (small) portion after the 8Mth character of a text-node a warning is issued. I would expect only 1 warning to be issued for each text-node that is too large. different bug-report?
## Comment 10929
Date: 2009-02-20 09:24:22 +0100
From: Jan Flokstra <<jflokstra>>
I fixed the problem by making the character buffer dynamic. So whenever a larger text node is used than any previous I realloc() the character buffer to fit the larger text. I still use the initial value of 1<<23 so for normal cases the change has no effect (in speed or size). For larger sizes I think we now support up to MAXINT or whatever the max is that libxml2 can handle.
## Comment 10930
Date: 2009-02-20 09:31:45 +0100
From: Jan Flokstra <<jflokstra>>
Update: I could not check in the fix in Stable because of sticky bit so you have to wait a little bit longer for the fix.
## Comment 10931
Date: 2009-02-20 09:39:50 +0100
From: @drstmane
Jan,
sticky *bit* --- is there some SF/CVS problem?
If so, please report (both to the SF admins and to us).
Thanks!
Stefan
## Comment 10932
Date: 2009-02-20 10:10:39 +0100
From: Jan Flokstra <<jflokstra>>
Sticky date was my own mistake, fix is now checked in. When Wouter is content we can close the bug.
## Comment 10933
Date: 2009-02-20 10:31:53 +0100
From: @drstmane
Thanks!
... don't for get to add a test before closing ...
Stefan
## Comment 10934
Date: 2009-02-26 14:51:24 +0100
From: Wouter Alink <<alink>>
With yesterdays latest stable the bug still persists, see details below.
(installed MonetDB using: ./monetdb_install.sh --nightly=stable --enable-xquery --enable-sql)
walink@ldc:~/opt/MonetDB-Feb2009> ./bin/Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for ia64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50021/admin
MonetDB-Feb2009-Stable>
walink@ldc:~/projects/bugs_monetdb> cat createLargeTextField.py
i=0
print "<aap>"
while i < 10000000:
print '"'
i+=1;
print "</aap>"
walink@ldc:~/projects/bugs_monetdb> python createLargeTextField.py | mclient -lxq -p50020 -I test.xml
MAPI = monetdb@localhost:50020
ACTION= mapi_stream_into
ERROR = !ERROR: Detected an entity reference loop
!ERROR: shredder_parse: XML input not well-formed.
!ERROR: CMDshred_stream: operation failed.
walink@ldc:~/projects/bugs_monetdb>
## Comment 10935
Date: 2009-02-26 15:49:29 +0100
From: Jan Flokstra <<jflokstra>>
Very strange. I tested it and did exactly the same you did and for me it worked fine. I just checked it on my HEAD version again (MonetDB/XQuery v0.29.0 and !not! v0.28.0)) and it still works. So it could be the fix is just not in your Stable version.
Furthermore I have been looking at the changelog for libxml2 and saw something which maybe also could explain it when you use a very very new libxml.
URL: http://www.xmlsoft.org/ChangeLog.html
Daniel Veillard Sun Jan 18 15:06:05 CET
* include/libxml/parserInternals.h SAX2.c: add a new define XML_MAX_TEXT_LENGHT limiting the maximum size of a single text node, the defaultis 10MB and can be removed with the HUGE parsing option
So as of 18/1/2009 they changed something with the maximum text size of a single text node. I could not find anything about this in the 'current' versions. This also means we should adapt for this in future versions.
I will also soon be checking in a better buffer increment stragegy which makes large node handling much faster, the performance is pretty crappy because of the small realloc increments.
JanF.
## Comment 10936
Date: 2009-02-26 16:49:40 +0100
From: Jan Flokstra <<jflokstra>>
I just checked in the buffer increment update in Stable. When your test was finished < 10 seconds you used the unfixed version because after the first fix it should take several minutes for the shred to complete, I went for a coffe the first time because I thought libxml2 was slow. Now with the additional fix it is back to seconds again.
## Comment 10937
Date: 2009-02-26 17:10:33 +0100
From: Wouter Alink <<alink>>
i thought you mentioned that the fix was applied to the 'stable' branch. Therefore I only tried the stable version.
What I now understand is that the fix has not been applied to the stable branch? If so, please let me know, because then I will start using the head.
## Comment 10938
Date: 2009-02-26 17:45:01 +0100
From: Jan Flokstra <<jflokstra>>
Yes, it is confusing. The current Stable is containing all the fixes. The first fix was already propagated to the HEAD so I could also check there. There is a chance you are using the Nov2008 release like in your original error posting. This version for sure does not contain the fix. I also do not know if the fix is in the Feb2009 Stable because the moment I checked the fix in Sjoerd was busy creating the Feb2008 release and I screwed up this proces so he might have left the fix out of the Feb2009 release. But the current untagged Stable Stable contains all te fixes now. The HEAD is correct but slow because it misses the last buffer fix which will be propgated in the next days I think.
JanF
## Comment 10939
Date: 2009-02-26 21:58:27 +0100
From: Wouter Alink <<alink>>
I just installed MonetDB from cvs (the very latest head version), but still get the same error. (it is not really slow either; python takes about 30 seconds to produce the document, but monetdb produces the error within a second).
When i use 'pf:add-doc("/tmp/largetext.xml","test.xml")' where largetext.xml is the output of the python script, it does not complete (waited for more than 2 hours), nor does it produce an error (cpu-use remains at 100%).
Is it possible that you forgot to check in some code?
walink@ldc:~/opt/MonetDB-current> bin/Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.29.0
based on GDK v1.29.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for ia64-suse-linux/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.29.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50031/admin
MonetDB>
walink@ldc:~/projects/bugs_monetdb> python createLargeTextField.py | mclient -lxq -p50030 -I test.xml
MAPI = monetdb@localhost:50030
ACTION= mapi_stream_into
ERROR = !ERROR: Detected an entity reference loop
!ERROR: shredder_parse: XML input not well-formed.
!ERROR: CMDshred_stream: operation failed.
## Comment 10940
Date: 2009-02-27 08:48:39 +0100
From: Jan Flokstra <<jflokstra>>
This is weird, looks like you missed the latest fix. Lets do an experiment which doe not take a lot of time. You should edit the file $PATHFINDER/runtime/shredder.mx and replace the function shred_characters() by:
/**
* SAX callback invoked whenever text node content is seen,
* simply buffer the content here
*/
static void
shred_characters(void *xmlCtx,
const xmlChar *cs,
int n)
{
shredCtxStruct *shredCtx = (shredCtxStruct*) xmlCtx;
if ( (shredCtx->content + n + 1) > shredCtx->content_max) {
shredCtx->content_max = MAX(shredCtx->content + n + 1, 2*shredCtx->content_max);
shredCtx->content_buf = GDKrealloc(shredCtx->content_buf, shredCtx->content_max);
if (shredCtx->content_buf == NULL) {
GDKerror("shred_characters: GDKrealloc() failed.\n");
BAILOUT(shredCtx);
}
}
memcpy(&(shredCtx->content_buf[shredCtx->content]), cs, n);
shredCtx->content += n;
}
Now we are sure you have the latest version of the crucial function. Then recompile and check what pf:add-doc("/tmp/largetext.xml","test.xml") does. It should return within 10 seconds (or 20:)
JanF.
## Comment 10941
Date: 2009-02-27 08:54:18 +0100
From: @drstmane
Wouter, JanF,
For your benefit and efficiency, you might want to consider adding a test to out test suite & system, that as a common reference enabled convenient monitoring of the status of this bug.
... just an idea ...
Stefan
## Comment 10942
Date: 2009-02-27 12:00:45 +0100
From: Jan Flokstra <<jflokstra>>
Added number of tests in "BugTracker/XML_large_text_nodes.SF-2586088-{create|shred_doc|remove}". These tests create an XML document with a 12M text node, shreds the document end does a string-length() on the text. Then it removes the xml document again.
The tests works fine on my notebook on the Feb2009 release but when running the same on a 64 bit system with a newer SuSe it ran into a timeout. So I think this bug may be a p.i.t.a running on some combinations of OS/libmxml2 and failing on others.
## Comment 10943
Date: 2009-02-27 18:30:39 +0100
From: @drstmane
Jan,
thanks for the test(s) --- if necessary, I'll increase the timeout(s) for the test(s) tomorrow, i.e., after tonight's testing run ...
On question, though: your test loads the document from file using mil command shred_doc() on the Mserver MIL console, while Wouter reports the bug for piping the document in to `mclient -lx -I<docname>` --- do you think there might be a difference in the behavour?
Stefan
## Comment 10944
Date: 2009-02-27 19:18:59 +0100
From: Jan Flokstra <<jflokstra>>
For the shredder there is absolutely no difference between the file shred and the piped shred. I concentrated first on making the file shred work. When this works correctly and the piped example still fails we should look at the way we initialize libxml2 (and maybe the mapi interface).
Wouter also tried an add-doc() but this failed because of a timeout. Lets first see what the tests tonight do. On my notebook the shred_doc test took only 8 seconds.
JanF.
## Comment 10945
Date: 2009-02-27 19:56:04 +0100
From: Wouter Alink <<alink>>
actually, i observed different behavior between "pf:add-doc()" and piping the data through mclient (with -I option). (see my previous message). The first one never returned, the latter returned with an error. I just tried using shred_doc() on the mil command line. This does not seem to finish (waited 3 minutes), so it seem to exhibit similar behavior as the pf:add-doc().
p.s. Stefan, you were absolutely right in that the test-web is the proper answer. Jan, thanks for adding the tests.
## Comment 10946
Date: 2009-02-28 10:21:40 +0100
From: Jan Flokstra <<jflokstra>>
The test shows a positive result on all systems except on Windows5.1 with a "too deep recursion" error. This error is not exclusively caused by this test because I saw it with other tests too.
Now his works I will have a look monday what happens when the document is piped though mclient.
## Comment 10947
Date: 2009-03-02 10:23:58 +0100
From: Jan Flokstra <<jflokstra>>
I cannot test the 'mclient -I' version because it fails on my machine. I had the same problem last week and thought it was due to other problems and did not check any further. The mclient seems to malfunction, sometimes it adds extra characters and sometimes it even says a document is empty when is works perfectly through add-doc(). For example:
ewi865 SCRIPTS/DATA> cat ./small.xml
<small>
</small>
ewi865 SCRIPTS/DATA> mclient -lxq -I small.xml
[HERE IS PRESS ^D]
MAPI = monetdb@localhost:50000
ACTION= mapi_stream_into
ERROR = !ERROR: Extra content at the end of the document
!ERROR: shredder_parse: XML input not well-formed.
!ERROR: CMDshred_stream: operation failed.
ewi865 SCRIPTS/DATA> mclient -lxq -I small.xml
1+1
[HERE I PRESS ^D^D]
MAPI = monetdb@localhost:50000
ACTION= mapi_stream_into
ERROR = !ERROR: Document is empty
!ERROR: shredder_parse: XML input not well-formed.
!ERROR: CMDshred_stream: operation failed.
ewi865 SCRIPTS/DATA> mclient -lx
xquery>pf:add-doc("/local/flokstra/software/SCRIPTS/DATA/small.xml","small.xml")
more>xquery>
ewi865 SCRIPTS/DATA>
When it also fails with you we should open a new bugreport and close this one because I think the tests this weekend shows this problem has been solved.
JanF.
## Comment 10948
Date: 2009-03-02 10:31:56 +0100
From: Jan Flokstra <<jflokstra>>
OK, sorry. The moment I pressed sent I knew what was wrong. I should have piped the file. I did the test again, eg.
mclient -lxq -I large_text_node.xml < large_text_node.xml
and it takes a loooooooooonngggg time, several minutes now, continuing,
JanF.
## Comment 10949
Date: 2009-03-02 10:39:49 +0100
From: Jan Flokstra <<jflokstra>>
It returns. I still have a very bad performance on my SuSe 64 bit machine, I think I need to make a fresh installation here. On my notebook it returns within 10 second, so it is only a little bit slower than the add-doc() version.
## Comment 10950
Date: 2009-03-24 12:13:25 +0100
From: Wouter Alink <<alink>>
I upgraded the libxml2 library to version 2.7.3 (latest version), and this resolved the problem on the Itanium machine. I guess the bug report can be closed, as JanF already added a test, and the original issue has been resolved.
## Comment 10951
Date: 2009-03-24 14:29:43 +0100
From: Wouter Alink <<alink>>
To clarify my previous message:
On a Itanium (IA64) machine with libxml2 version 2.6.23: the "detected entity reference loop" bug still occurs with the Feb2009 release with the specific document.
With a newer version of libxml2 (2.7.3), the bug disappears.
Question: Should we change the requirements (during ./configure) of MonetDB for libxml2? (or should (this) documentation be enough?)
## Comment 10952
Date: 2009-03-24 14:33:34 +0100
From: @grobian
configure is your friend
## Comment 10953
Date: 2009-03-24 14:37:52 +0100
From: Jan Flokstra <<jflokstra>>
I think this will be a difficult configuration check because I use libxml version 2.6.17 and it works fine on my notebook and the 64 bit SuSe servers we use. I propose to just keep it this way.
## Comment 10954
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2586088 at http://sourceforge.net/support/tracker.php?aid=2586088
| XQ: large text nodes | https://api.github.com/repos/MonetDB/MonetDB/issues/1942/comments | 0 | 2020-11-30T10:09:17Z | 2024-06-28T13:26:54Z | https://github.com/MonetDB/MonetDB/issues/1942 | 753,340,380 | 1,942 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-10 05:10:25 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-11 08:42:29 +0100
## Comment 10925
Date: 2009-02-10 17:10:25 +0100
From: @romulogoncalves
Look to the following example:
create table t1 (num int, age int);
create table t2 (id serial, num int, age int);
insert into t1 values(1,3);
insert into t1 values(1,4);
insert into t1 values(3,3);
insert into t1 values(6,3);
insert into t1 values(2,3);
insert into t1 values(2,2);
insert into t1 values(5,1);
insert into t1 values(1,1);
insert into t2(num, age) select num, age from t1 order by num, age;
select * from t2;
drop table t1;
drop table t2;
The selection result is:
% sys.t2, sys.t2, sys.t2 table_name
% id, num, age name
% int, int, int type
% 1, 1, 1 length
[ 8, 1, 1 ]
[ 1, 1, 3 ]
[ 2, 1, 4 ]
[ 6, 2, 2 ]
[ 5, 2, 3 ]
[ 3, 3, 3 ]
[ 7, 5, 1 ]
[ 4, 6, 3 ]
I think it is not right and the right one is:
The selection result is:
% sys.t2, sys.t2, sys.t2 table_name
% id, num, age name
% int, int, int type
% 1, 1, 1 length
[ 1, 1, 1 ]
[ 2, 1, 3 ]
[ 3, 1, 4 ]
[ 4, 2, 2 ]
[ 5, 2, 3 ]
[ 6, 3, 3 ]
[ 7, 5, 1 ]
[ 8, 6, 3 ]
I think the query should create a clustered temp table on num, age (from the select clause) and then do the insertion into t2 using the serial. The sort is applied over the temp table, but it should not be done over the final table t2.
## Comment 10926
Date: 2009-02-11 20:42:29 +0100
From: @njnes
First order then project, added check for project with order)
Test was added already to BugTracker-2009
## Comment 10927
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2585592 at http://sourceforge.net/support/tracker.php?aid=2585592
| Serial with order by is not working properly | https://api.github.com/repos/MonetDB/MonetDB/issues/1941/comments | 0 | 2020-11-30T10:09:14Z | 2024-06-27T11:34:32Z | https://github.com/MonetDB/MonetDB/issues/1941 | 753,340,354 | 1,941 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-09 07:57:08 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-11 08:43:26 +0100
## Comment 10921
Date: 2009-02-09 19:57:08 +0100
From: @romulogoncalves
I if run the following code:
create table t2(id int, inst float);
insert into t2 values(1, 0.2);
insert into t2 values(1, 0.4);
select l.id, r.inst, l.inst, (r.inst - l.inst) as diff from t2 l, t2 r where r.id = l.id order by inst limit 2;
drop table t2;
I get:
MAPI = monetdb@localhost:50000
QUERY = select l.id, r.inst, l.inst, (r.inst - l.inst) as diff from t2 l, t2 r where r.id = l.id order by inst limit 2;
ERROR = !MALException:batcalc.CMDbatSUB:requires bats of identical size
If I remove order by clause it works.
To complete the report I also detected a crash similar to the one reported on bug:
2581617 cardinality of expression is wrong
To see the crash just run the following query:
select l.id, (r.inst - l.inst) as diff from t2 l, t2 r where r.id = l.id order by inst limit 2;
## Comment 10922
Date: 2009-02-09 21:50:42 +0100
From: @romulogoncalves
Test added at:
sql/src/test/BugTracker-2009/Tests/subtraction_between_two_columns.SF-2582389.sql
## Comment 10923
Date: 2009-02-11 20:43:26 +0100
From: @njnes
Disabled pushing sort down, this causes problems when the sorted
column is used in other selection/projection results)
## Comment 10924
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2582389 at http://sourceforge.net/support/tracker.php?aid=2582389
| subtraction between two columns | https://api.github.com/repos/MonetDB/MonetDB/issues/1940/comments | 0 | 2020-11-30T10:09:11Z | 2024-06-27T11:34:31Z | https://github.com/MonetDB/MonetDB/issues/1940 | 753,340,324 | 1,940 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-09 03:14:17 +0100
From: @skinkie
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-23 13:15:11 +0200
## Comment 10911
Date: 2009-02-09 15:14:17 +0100
From: @skinkie
/opt/monetdb/bin/mserver5
MonetDB server v5.11.0, based on kernel v1.29.0
Serving database 'demo', using 2 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008- MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>
nemesis Linux /opt/monetdb/bin/mclient -lmal
mal>b := "bla";
mal>b := "bla";
nemesis Linux /opt/monetdb/bin/mclient -lmal
mal>b := 5;
MAPI = monetdb@localhost:50000
QUERY = b := 5;
ERROR = !TypeException:user.main[1]:type mismatch str := int
mal>nemesis Linux /opt/monetdb/bin/mclient -lmal
mal>io.print(b);
[ nil ]
When closing the client it would be expected that the variable would not be maintained. This seems not to be true anymore. Thanks to Fabian for helping me with this bug report.
## Comment 10912
Date: 2009-02-09 18:40:29 +0100
From: @mlkersten
Fixed by cleaning out the context on MALexit.
No test requires/
## Comment 10913
Date: 2009-02-16 11:50:43 +0100
From: @drstmane
added test in MonetDB5/tests/BugTracker/Tests/mal_var_persistent_over_sessions.SF-2581675.*
still (again?) fails as reported!
## Comment 10914
Date: 2009-02-17 10:10:36 +0100
From: @drstmane
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/mal_var_persistent_over_sessions.SF-2581675.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/mal_var_persistent_over_sessions.SF-2581675.out.00.html
## Comment 10915
Date: 2009-03-14 08:42:14 +0100
From: @mlkersten
The stable Feb 2009 of march 13 is worse, it removed the global stack,
which results in all variables being reset for the second mclient session
against the same server.
Fix checkedin
## Comment 10916
Date: 2009-03-15 10:12:10 +0100
From: @drstmane
Fixed by Martin.
Test now works fine.
## Comment 10917
Date: 2009-04-20 09:45:31 +0200
From: @mlkersten
This problem also appeared in the SQL scenario.
The issue is not covered by a test script.
## Comment 10918
Date: 2009-04-22 16:26:29 +0200
From: @drstmane
re-opened to remind us that the test still/again fails
## Comment 10919
Date: 2009-05-09 23:14:40 +0200
From: @mlkersten
It finally seems fixed.
## Comment 10920
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2581675 at http://sourceforge.net/support/tracker.php?aid=2581675
## Comment 14873
Date: 2010-09-03 15:31:50 +0200
From: @grobian
Changeset [f2ceaaf24796](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f2ceaaf24796) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2ceaaf24796](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2ceaaf24796)
Changeset description:
bugzie says that bug #1939 is fixed, so disable the guard
## Comment 16320
Date: 2011-09-23 11:47:47 +0200
From: @grobian
removal of guards undone by:
changeset: 35341:f6fe92fcd289
branch: Feb2010
parent: 35337:bdd345fbc7c2
user: Sjoerd Mullender <sjoerd@acm.org>
date: Wed Mar 17 12:51:57 2010 +0000
files: MonetDB5/src/mal/mal_session.mx
description:
Fix a serious race condition:
MALexitClient is called from runScenarioBody which in turn is called
from runScenario which is called from MSserveClient. In the old
situation, MALexitClient called (indirectly) freeClient which set the
mode of the client record to FREECLIENT. Immediately after setting
the mode, the client record can be grabbed by another thread that
calls MCnewClient, after which this other thread reinitializes the
client record. However, after runScenario returns, MSserveClient
looks at the client record, not expecting it to have been taken away
from it and to have been reinitialized, resulting ultimately in
crashes.
The problem is fixed by not calling MCcloseClient in MALexitClient,
but by instead setting the mode flag to FINISHING.
However, this leads to another problem surfacing:
After the mode was set to FINISHING, MSserveClient calls MCwait which
sets the mode to AWAITING to signal that the thread with client record
can be reused by another incoming client. Unfortunately, the client
record does not get reinitialized properly, resulting in variables
sticking around from one session to the next (SF bug #2581675). This
problem is avoided by not reusing the thread, i.e. by not calling
MCwait.
In other words, this checkin fixes two seemingly unrelated problems.
## Comment 16321
Date: 2011-09-23 13:12:06 +0200
From: @grobian
Changeset [089189da222b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=089189da222b) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=089189da222b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=089189da222b)
Changeset description:
clients: remove code related to client reuse, bug #1939
The client reuse code has caused numerous bugs sofar, and as effect it
has been disabled since long, so to avoid confusing more people at times
bugs pop up, remove the code.
## Comment 16322
Date: 2011-09-23 13:15:11 +0200
From: @grobian
Instead of fixing, the entire code path has been removed, which sort of makes this problem go away. End-user result is close to FIXED.
| mal variable type is persistent over sessions | https://api.github.com/repos/MonetDB/MonetDB/issues/1939/comments | 0 | 2020-11-30T10:09:08Z | 2024-06-28T13:26:53Z | https://github.com/MonetDB/MonetDB/issues/1939 | 753,340,282 | 1,939 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-09 02:51:28 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-11 08:45:55 +0100
## Comment 10907
Date: 2009-02-09 14:51:28 +0100
From: @romulogoncalves
The following sql crashes M5-SQL
create table t1 (id int, age int);
insert into t1 values(1, 1);
insert into t1 values(1, 1);
insert into t1 values(2, 1);
insert into t1 values(3, 1);
insert into t1 values(4, 1);
create view v2 as (select id, age from t1 group by id, age);
select id from v2 where id = 2;
drop view v2;
drop table t1;
mserver debug:
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe1728950 (LWP 13769)]
0x0000003830832f05 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.3-2.fc10.x86_64
glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64
krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64
ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64
pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64
zlib-1.2.3-18.fc9.x86_64
(gdb) up
1 0x0000003830834a73 in abort () from /lib64/libc.so.6
(gdb) up
2 0x000000383082bef9 in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00007fffe2816472 in rel_project (l=0x7fffd41d1d98,
e=0x7fffe0ce7cb8) at
/ufs/goncalve/MonetDB/current/sql/src/server/rel_select.mx:556
556 assert (exps_card(rel->exps) <= rel->card);
(gdb) p rel
$1 = (sql_rel *) 0x7fffec155f58
(gdb) p rel->exps
$2 = (list *) 0x7fffe0ce7cb8
(gdb) p rel->card
$3 = 2 '\002'
The bug is the card of rel isn't really 2(aggr) but 3 (relation).
## Comment 10908
Date: 2009-02-09 15:56:25 +0100
From: @romulogoncalves
Test added at:
sql/src/test/BugTracker-2009/Tests/Attic/cardinality_of_expression_is_wrong.SF-2581617.sql
## Comment 10909
Date: 2009-02-11 20:45:55 +0100
From: @njnes
When optimizing we sometimes have to fixup the cardinality of
expressions
## Comment 10910
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2581617 at http://sourceforge.net/support/tracker.php?aid=2581617
| cardinality of expression is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1938/comments | 0 | 2020-11-30T10:09:02Z | 2024-06-27T11:34:29Z | https://github.com/MonetDB/MonetDB/issues/1938 | 753,340,239 | 1,938 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-06 05:03:44 +0100
From: @peterboncz
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-02-16 03:41:52 +0100
## Comment 10897
Date: 2009-02-06 17:03:44 +0100
From: @peterboncz
maybe it is my version of libxml2 (2.7.2), but I get loads of errors when shredding DBLP.xml with dtd
external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document without external subsetxmlAddDtdEntity: document
(a newline in the error message would maybe be an idea)
shredding nevertheless proceeds.
reproduction:
- download DBLP.xml and dblp.xml from the web
- shred DBLP.xml
## Comment 10898
Date: 2009-02-06 19:54:13 +0100
From: Jan Flokstra <<jflokstra>>
I only have a very slow internet connection here so I cannot check but isn't this the same bug as the entities_DTD.SFxxxx bug which went failing when you (Peter Boncz:-) were experimenting with freeiing dtd's because they were duplicate. I had a look at this problem but did not understand what you were accomplish. I remember this was between version 1.146 and 1.147.
## Comment 10899
Date: 2009-02-06 20:51:37 +0100
From: @peterboncz
Jan, what I was trying to accomplish back then, just like now, close to a deadline, was to fix a crash that I stumbled on.
In my recollection, it also concerned dblp
I have no wish to implement anything, I just try to get mqx to shred this quite well know dataset. Apparently and indeed without understanding of the dtd functionality of libxml, in a wrong way
That is independent of the base_dir problem that you created, where I mentioned your name
So help is appreciated
## Comment 10900
Date: 2009-02-06 21:23:14 +0100
From: Jan Rittinger <<jan.rittinger>>
Just for cross reference: see https://sourceforge.net/tracker2/?func=detail&aid=2553868&group_id=56967&atid=482468
tests/BugTracker/entities_dtd.SF-1642665 (shredder.mx 1.146 -> 1.147)
tests/W3C_use_cases/XQ/SGML/shred_doc (shredder.mx 1.146 -> 1.147)
## Comment 10901
Date: 2009-02-06 23:55:30 +0100
From: Jan Rittinger <<jan.rittinger>>
The problem arises in the call to externalSubset (namely in function xmlAddDtdEntity). The problem is that ctx->myDoc->extSubset is NULL which triggers the error messages.
I checked in a fix. Let's see whether everything now works.
In the first place I would have prohibited a mix of internal and external DTDs all together!
@Peter: Could you please check all your scenarios.
## Comment 10902
Date: 2009-02-07 00:05:16 +0100
From: @peterboncz
Hi Jan^2
This works, dblp.xml is shreddable again, without dtd errors!
thanks!
Peter
## Comment 10903
Date: 2009-02-09 10:15:25 +0100
From: Jan Rittinger <<jan.rittinger>>
Shredding now works without errors again. Closing.
## Comment 10904
Date: 2009-02-16 11:58:57 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 10905
Date: 2009-02-16 15:41:52 +0100
From: Jan Rittinger <<jan.rittinger>>
Test not needed. The following two tests check for the same functionality:
tests/BugTracker/entities_dtd.SF-1642665
tests/W3C_use_cases/XQ/SGML/shred_doc
## Comment 10906
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2573123 at http://sourceforge.net/support/tracker.php?aid=2573123
| dblp.xml with DTD broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1937/comments | 0 | 2020-11-30T10:08:59Z | 2024-06-27T11:34:28Z | https://github.com/MonetDB/MonetDB/issues/1937 | 753,340,198 | 1,937 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-05 09:05:48 +0100
From: Floris Ouwendijk <<floris233>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 03:40:54 +0200
## Comment 10887
Date: 2009-02-05 09:05:48 +0100
From: Floris Ouwendijk <<floris233>>
After a few days of testing the server terminates with a segfault. This happened more than once. This time I was able to capture a stack trace of the moment the problem occurs.
The system is a 64bit Fedora Core 6 machine. Monet is adaily build from 2008-12-11
The following is the stack, plus per stack element a listing:
...
[New Thread 47195725654336 (LWP 406)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47195725654336 (LWP 406)]
0x00002aaab876c549 in CMDmposjoin (res=0x2aec9c757510, pre=0x2ac1f33e65d0, cont=0x2ac202654b88, ws_item=0x2ad0a15f34d8) at pf_support.c:9886
9886 fake_item = is_fake_project(batlist[ii]);
(gdb) bt
0 0x00002aaab876c549 in CMDmposjoin (res=0x2aec9c757510, pre=0x2ac1f33e65d0, cont=0x2ac202654b88, ws_item=0x2ad0a15f34d8) at pf_support.c:9886
1 0x00002aaab873d097 in CMDmposjoin_unpack2001592764 (argc=4, argv=0x2aec9c757510) at pf_support.glue.c:318
2 0x00002aaaabbfed97 in interpret (stk=2458, lt=0x2ac66766a6f8, res=0x2aec9c757a20) at monet_interpreter.c:1070
3 0x00002aaaabbfb8a7 in interpret_params (stk=2458, lt=0x2ac66766a698, params=0x2aec9c757c50, fcn_nme=0x8f61b8 "mposjoin") at monet_interpreter.c:282
4 0x00002aaaabbfddd3 in interpret (stk=2458, lt=0x2ac66766a678, res=0x2aec9c764e10) at monet_interpreter.c:884
5 0x00002aaaabc095cf in interpret_assignment (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:2152
6 0x00002aaaabbfc900 in interpret (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:638
7 0x00002aaaabc098ce in interpret_seqblock (stk=2458, lt=0x2ac66766a5d8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
8 0x00002aaaabbfc991 in interpret (stk=832, lt=0x2ac66766a5d8, res=0x2aec9c764e10) at monet_interpreter.c:654
9 0x00002aaaabbfcb15 in interpret (stk=832, lt=0x2ac66766a4b8, res=0x2aec9c764e10) at monet_interpreter.c:683
10 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac2013d8748, res=0x2aec9c764e10) at monet_interpreter.c:696
11 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac66767cd08, res=0x2aec9c764e10) at monet_interpreter.c:696
12 0x00002aaaabc098ce in interpret_seqblock (stk=832, lt=0x2ac66785f8c8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
13 0x00002aaaabbfc991 in interpret (stk=3658, lt=0x2ac66785f8c8, res=0x2aec9c764e10) at monet_interpreter.c:654
14 0x00002aaaabbfcb15 in interpret (stk=3658, lt=0x2ac66785f7a0, res=0x2aec9c764e10) at monet_interpreter.c:683
15 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2abad4ba18f8, res=0x2aec9c764e10) at monet_interpreter.c:696
16 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac6672d4248, res=0x2aec9c764e10) at monet_interpreter.c:696
17 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac34d4b9328, res=0x2aec9c764e10) at monet_interpreter.c:696
18 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad085319508, res=0x2aec9c764e10) at monet_interpreter.c:696
19 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2017071f8, res=0x2aec9c764e10) at monet_interpreter.c:696
20 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2022fd538, res=0x2aec9c764e10) at monet_interpreter.c:696
21 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d84e28, res=0x2aec9c764e10) at monet_interpreter.c:696
22 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad500d348e8, res=0x2aec9c764e10) at monet_interpreter.c:696
23 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2024e21c8, res=0x2aec9c764e10) at monet_interpreter.c:696
24 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad7b66f07c8, res=0x2aec9c764e10) at monet_interpreter.c:696
25 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d80e38, res=0x2aec9c764e10) at monet_interpreter.c:696
26 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac65e984a68, res=0x2aec9c764e10) at monet_interpreter.c:696
27 0x00002aaaabc098ce in interpret_seqblock (stk=3658, lt=0x341b7788, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
28 0x00002aaaabbfc991 in interpret (stk=3613, lt=0x341b7788, res=0x2aec9c764e10) at monet_interpreter.c:654
29 0x00002aaaabc098ce in interpret_seqblock (stk=3613, lt=0x2ad08507f598, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
30 0x00002aaaabbfc991 in interpret (stk=1573, lt=0x2ad08507f598, res=0x2aec9c764e10) at monet_interpreter.c:654
31 0x00002aaaabbfe72c in interpret (stk=1573, lt=0x2ad0a0d283d8, res=0x2aec9c764e10) at monet_interpreter.c:1044
32 0x00002aaaabc095cf in interpret_assignment (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:2152
33 0x00002aaaabbfc900 in interpret (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:638
34 0x00002aaaabc098ce in interpret_seqblock (stk=1573, lt=0x2ac201b44288, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
35 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2abad4c284d0, res=0x2aec9c764e10) at monet_interpreter.c:654
36 0x00002aaaab1a276b in CMDcatch (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at builtin.c:1065
37 0x00002aaaabbfd551 in interpret (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at monet_interpreter.c:808
38 0x00002aaaabc095cf in interpret_assignment (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:2152
39 0x00002aaaabbfc900 in interpret (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:638
40 0x00002aaaabc098ce in interpret_seqblock (stk=19, lt=0x2ad05e51af58, res=0x2aec9c764e10, scope=0) at monet_interpreter.c:2200
41 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2ad083b04b48, res=0x2aec9c764e10) at monet_interpreter.c:654
42 0x00002aaab9babd35 in xquery_tree_exec (ctx=0x2ab6378f5ea8, t=0x2ad083b04b48, repeat=0) at pathfinder.c:239
43 0x00002aaab9bac296 in xquery_mil_exec (ctx=0x2ab6378f5ea8,
buf=0x2ac31d5f4e40 "var tijah_scoreDB;\nvar tijah_ftiTape;\nvar xrpc_qid;\nvar xrpc_caller;\nvar xrpc_hdl;\nvar xrpc_seqnr;\nvar xrpc_timeout;\nvar xrpc_mode;\nvar xrpc_module;\nvar xrpc_method;\nxrpc_qid := \"\";\nxrpc_caller := \"\";"...) at pathfinder.c:297
44 0x00002aaab9bacbe7 in xquery_compile_exec (ctx=0x2ab6378f5ea8, options=2,
xquery=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"..., is_url=0, prologue=0x2aec9c765330, query=0x2aec9c765328,
epilogue=0x2aec9c765320, module=0x0) at pathfinder.c:445
45 0x00002aaab9bb2cf0 in xquery_prepare (ctx=0x2ab6378f5ea8, usec=659415161738,
query=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"...) at pathfinder.c:2258
46 0x00002aaab9bb3326 in xquery_client_engine (mc=0x2aaaba3177f8) at pathfinder.c:2405
47 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3177f8) at mapi.c:316
48 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
49 0x00000036638ce86d in clone () from /lib64/libc.so.6
50 0x0000000000000000 in ?? ()
(gdb) list
9881
9882 {
9883 bit fake_item = FALSE;
9884 bat bid = *(bat*)Tloc(ws_item, pw);
9885 batlist[ii] = BATdescriptor(bid);
9886 fake_item = is_fake_project(batlist[ii]);
9887 fake_ws_item |= fake_item;
9888 if (!(fake_item || BAThdense(batlist[ii]))) {
9889 GDKerror("mposjoin: all BATs in the tail of the third input BAT (ws_item) must have a dense head.\n");
9890 ii++;
(gdb) up
1 0x00002aaab873d097 in CMDmposjoin_unpack2001592764 (argc=4, argv=0x2aec9c757510) at pf_support.glue.c:318
318 if (!CMDmposjoin(
(gdb) list
313 }
314 argv[0].vtype = TYPE_bat;
315 argv[0].len = 0;
316 argv[0].val.bval = 0;
317
318 if (!CMDmposjoin(
319 &argv[0].val.Bval,
320 BBPdescriptor(argv[1].val.bval),
321 BBPdescriptor(argv[2].val.bval),
322 BBPdescriptor(argv[3].val.bval))
(gdb) up
2 0x00002aaaabbfed97 in interpret (stk=2458, lt=0x2ac66766a6f8, res=0x2aec9c757a20) at monet_interpreter.c:1070
1070 i = (*sig->pack_fcn) (argc, argv);
(gdb) list
1065 }
1066 if (!interpret_params_pin(argc, argv, fcn_nme)) {
1067 return -1;
1068 }
1069 if (sig->token == TOK_COMMAND) {
1070 i = (*sig->pack_fcn) (argc, argv);
1071 *res = argv[0];
1072 CATCHVAL(stk, opcache, res);
1073 CATCHERR(stk, opcache, res, i, ((YYSTREE) sig->pack_fcn));
1074
(gdb) up
3 0x00002aaaabbfb8a7 in interpret_params (stk=2458, lt=0x2ac66766a698, params=0x2aec9c757c50, fcn_nme=0x8f61b8 "mposjoin") at monet_interpreter.c:282
282 if (interpret(stk, tt, &res) < 0) {
(gdb) list
277 }
278 if (tt->token == TOK_RANGETEMP) {
279 tt = tt->yysons[0];
280 param_range = 1;
281 }
282 if (interpret(stk, tt, &res) < 0) {
283 GDKerror("interpret_params: %s(param %d): evaluation error.\n", fcn_nme, j + 1);
284 return -argc;
285 }
286 if (param_range) {
(gdb) up
4 0x00002aaaabbfddd3 in interpret (stk=2458, lt=0x2ac66766a678, res=0x2aec9c764e10) at monet_interpreter.c:884
884 argc = interpret_params(stk, lt->yysons[0], argv, fcn_nme);
(gdb) list
879
880 /* PROCs attach the argv storage to the tree so they can keep pointing to it across iterations */
881 if (opcache->yyval.vtype == TYPE_str) {
882 argv = opcache->yyval.val.pval;
883 }
884 argc = interpret_params(stk, lt->yysons[0], argv, fcn_nme);
885 res->vtype = TYPE_void;
886 res->val.oval = void_nil;
887 if (argc < 0)
888 return -1;
(gdb) up
5 0x00002aaaabc095cf in interpret_assignment (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:2152
2152 i = interpret(stk, arg(lt, 1), res);
(gdb) list
2147 }
2148
2149
2150
2151
2152 i = interpret(stk, arg(lt, 1), res);
2153
2154
2155 if (act && act->frozen && value->vtype != res->vtype) {
2156 GDKerror("interpret_assignment: cannot change type of frozen variable '%s'\n", act->name);
(gdb) up
6 0x00002aaaabbfc900 in interpret (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:638
638 r = interpret_assignment(stk, lt, res);
(gdb) list
633
634
635
636 return 0;
637 case TOK_ASSIGNMENT:
638 r = interpret_assignment(stk, lt, res);
639
640 ifdef HAVE_TIMES
641 if (profilemode) {
642 lng nc = GDKusec();
(gdb) up
7 0x00002aaaabc098ce in interpret_seqblock (stk=2458, lt=0x2ac66766a5d8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
8 0x00002aaaabbfc991 in interpret (stk=832, lt=0x2ac66766a5d8, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
9 0x00002aaaabbfcb15 in interpret (stk=832, lt=0x2ac66766a4b8, res=0x2aec9c764e10) at monet_interpreter.c:683
683 r = interpret(stk, arg(lt, 1), res);
(gdb) list
678 } else if (res->val.cval[0] == bit_nil) {
679 GDKerror("interpret: if bit(nil): don't know what to do!\n");
680 return -1;
681 }
682 if (res->val.cval[0]) {
683 r = interpret(stk, arg(lt, 1), res);
684
685 ifdef HAVE_TIMES
686 if (profilemode) {
687 lng nc = GDKusec();
(gdb) up
10 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac2013d8748, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
11 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac66767cd08, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
12 0x00002aaaabc098ce in interpret_seqblock (stk=832, lt=0x2ac66785f8c8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
13 0x00002aaaabbfc991 in interpret (stk=3658, lt=0x2ac66785f8c8, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
14 0x00002aaaabbfcb15 in interpret (stk=3658, lt=0x2ac66785f7a0, res=0x2aec9c764e10) at monet_interpreter.c:683
683 r = interpret(stk, arg(lt, 1), res);
(gdb) list
678 } else if (res->val.cval[0] == bit_nil) {
679 GDKerror("interpret: if bit(nil): don't know what to do!\n");
680 return -1;
681 }
682 if (res->val.cval[0]) {
683 r = interpret(stk, arg(lt, 1), res);
684
685 ifdef HAVE_TIMES
686 if (profilemode) {
687 lng nc = GDKusec();
(gdb) up
15 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2abad4ba18f8, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
16 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac6672d4248, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
17 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac34d4b9328, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
18 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad085319508, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
19 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2017071f8, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
20 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2022fd538, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
21 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d84e28, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
22 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad500d348e8, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
23 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2024e21c8, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
24 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad7b66f07c8, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
25 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d80e38, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb) up
26 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac65e984a68, res=0x2aec9c764e10) at monet_interpreter.c:696
696 r = interpret(stk, arg(lt, 2), res);
(gdb) list
691
692
693
694 return r;
695 } else if (lt->cnt == 3) {
696 r = interpret(stk, arg(lt, 2), res);
697
698 ifdef HAVE_TIMES
699 if (profilemode) {
700 lng nc = GDKusec();
(gdb)
(gdb) up
27 0x00002aaaabc098ce in interpret_seqblock (stk=3658, lt=0x341b7788, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
28 0x00002aaaabbfc991 in interpret (stk=3613, lt=0x341b7788, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
29 0x00002aaaabc098ce in interpret_seqblock (stk=3613, lt=0x2ad08507f598, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
30 0x00002aaaabbfc991 in interpret (stk=1573, lt=0x2ad08507f598, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
31 0x00002aaaabbfe72c in interpret (stk=1573, lt=0x2ad0a0d283d8, res=0x2aec9c764e10) at monet_interpreter.c:1044
1044 i = interpret(stk, op, res);
(gdb) list
1039
1040 exec:stamp = BBPcurstamp();
1041 if (sig->token == TOK_PROC) {
1042 YYSTREE proc = (YYSTREE) sig->pack_fcn;
1043
1044 i = interpret(stk, op, res);
1045 CATCHRET(stk, opcache, res, i);
1046 CATCHERR(stk, opcache, res, i, proc);
1047 if (i >= 0 && !TBL_procreturn(argc, argv, res, proc)) {
1048 if (proc->noyyval)
(gdb) up
32 0x00002aaaabc095cf in interpret_assignment (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:2152
2152 i = interpret(stk, arg(lt, 1), res);
(gdb) list
2147 }
2148
2149
2150
2151
2152 i = interpret(stk, arg(lt, 1), res);
2153
2154
2155 if (act && act->frozen && value->vtype != res->vtype) {
2156 GDKerror("interpret_assignment: cannot change type of frozen variable '%s'\n", act->name);
(gdb) up
33 0x00002aaaabbfc900 in interpret (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:638
638 r = interpret_assignment(stk, lt, res);
(gdb) list
633
634
635
636 return 0;
637 case TOK_ASSIGNMENT:
638 r = interpret_assignment(stk, lt, res);
639
640 ifdef HAVE_TIMES
641 if (profilemode) {
642 lng nc = GDKusec();
(gdb) up
34 0x00002aaaabc098ce in interpret_seqblock (stk=1573, lt=0x2ac201b44288, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
35 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2abad4c284d0, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
36 0x00002aaaab1a276b in CMDcatch (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at builtin.c:1065
1065 int i = interpret(stk, lt->yysons[0], res);
(gdb) list
1060
1061 /* execute the MIL expression while catching all errors and warnings */
1062 *errbuf = 0;
1063 GDKsetbuf(errbuf);
1064 if (lt->cnt >= 1) {
1065 int i = interpret(stk, lt->yysons[0], res);
1066
1067 CATCHRET(stk, lt, res, i);
1068 }
1069 GDKsetbuf(bak);
(gdb) up
37 0x00002aaaabbfd551 in interpret (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at monet_interpreter.c:808
808 i = (*imp) (stk, lt, res);
(gdb) list
803 int (*imp) (Cntxt, YYSTREE, ValPtr) = (int (*)(Cntxt, YYSTREE, ValPtr)) lt->yyval.val.pval;
804
805 res->vtype = TYPE_void;
806 res->val.oval = void_nil;
807 stamp = BBPcurstamp();
808 i = (*imp) (stk, lt, res);
809 if (i >= 0) {
810 CATCHREF(stk, lt, res);
811 }
812 CATCHERR(stk, lt, res, i, ((YYSTREE) imp));
(gdb) up
38 0x00002aaaabc095cf in interpret_assignment (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:2152
2152 i = interpret(stk, arg(lt, 1), res);
(gdb) list
2147 }
2148
2149
2150
2151
2152 i = interpret(stk, arg(lt, 1), res);
2153
2154
2155 if (act && act->frozen && value->vtype != res->vtype) {
2156 GDKerror("interpret_assignment: cannot change type of frozen variable '%s'\n", act->name);
(gdb) up
39 0x00002aaaabbfc900 in interpret (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:638
638 r = interpret_assignment(stk, lt, res);
(gdb) list
633
634
635
636 return 0;
637 case TOK_ASSIGNMENT:
638 r = interpret_assignment(stk, lt, res);
639
640 ifdef HAVE_TIMES
641 if (profilemode) {
642 lng nc = GDKusec();
(gdb) up
40 0x00002aaaabc098ce in interpret_seqblock (stk=19, lt=0x2ad05e51af58, res=0x2aec9c764e10, scope=0) at monet_interpreter.c:2200
2200 r = interpret(stk, lt->yysons[i], res);
(gdb) list
2195 CNTXTuse(stk);
2196 }
2197 for (; lt; lt = YYOVERFLOW(lt)) {
2198 for (i = 0; i < lt->cnt; i++)
2199 if (lt->yysons[i]) {
2200 r = interpret(stk, lt->yysons[i], res);
2201 CLEANUP(lt->yysons[i]);
2202 if (r < 0)
2203 goto xit;
2204 }
(gdb) up
41 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2ad083b04b48, res=0x2aec9c764e10) at monet_interpreter.c:654
654 return interpret_seqblock(stk, lt, res, i);
(gdb) list
649 return r;
650 case TOK_SEQBLOCK:
651 i = 1;
652 /* fall through */
653 case TOK_SEQ:
654 return interpret_seqblock(stk, lt, res, i);
655 case TOK_PARBLOCK:
656 return interpret_parblock(stk, lt, 1);
657 case TOK_PAREND:
658 return 0;
(gdb) up
42 0x00002aaab9babd35 in xquery_tree_exec (ctx=0x2ab6378f5ea8, t=0x2ad083b04b48, repeat=0) at pathfinder.c:239
239 int ret = interpret(repeat?ctx->repeat_stk:ctx->stk, t, &res);
(gdb) list
234 xquery_tree_exec(xquery_client *ctx,
235 YYSTREE t,
236 int repeat)
237 {
238 ValRecord res;
239 int ret = interpret(repeat?ctx->repeat_stk:ctx->stk, t, &res);
240 if (repeat) {
241 /* record the maxstk. recall we do not ever free stacks for the repeated execs */
242 ctx->repeat_max = monet_clients[ctx->stk].maxstk;
243 } else if (ctx->repeat_max) {
(gdb) up
43 0x00002aaab9bac296 in xquery_mil_exec (ctx=0x2ab6378f5ea8,
buf=0x2ac31d5f4e40 "var tijah_scoreDB;\nvar tijah_ftiTape;\nvar xrpc_qid;\nvar xrpc_caller;\nvar xrpc_hdl;\nvar xrpc_seqnr;\nvar xrpc_timeout;\nvar xrpc_mode;\nvar xrpc_module;\nvar xrpc_method;\nxrpc_qid := \"\";\nxrpc_caller := \"\";"...) at pathfinder.c:297
297 ret = xquery_tree_exec(ctx, t, 0);
(gdb) list
292 if (ctx->mode&XQ_DEBUG)
293 stream_write(ctx->fderr, buf, strlen(buf), 1);
294
295 t = xquery_mil2tree(ctx, buf);
296 if (t) {
297 ret = xquery_tree_exec(ctx, t, 0);
298 Myyfree(t);
299 }
300 return ret;
301 }
(gdb) up
44 0x00002aaab9bacbe7 in xquery_compile_exec (ctx=0x2ab6378f5ea8, options=2,
xquery=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"..., is_url=0, prologue=0x2aec9c765330, query=0x2aec9c765328,
epilogue=0x2aec9c765320, module=0x0) at pathfinder.c:445
445 ret = xquery_mil_exec(ctx, *query);
(gdb) list
440 if (ret && *prologue && **prologue)
441 ret = xquery_mil_exec(ctx, *prologue);
442
443 if (ret && query) {
444 if (*query && **query)
445 ret = xquery_mil_exec(ctx, *query);
446
447 if (ret && *epilogue && **epilogue)
448 ret = xquery_mil_exec(ctx, *epilogue);
449 }
(gdb) up
45 0x00002aaab9bb2cf0 in xquery_prepare (ctx=0x2ab6378f5ea8, usec=659415161738,
query=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"...) at pathfinder.c:2258
2258 if (xquery_compile_exec(ctx, options, query, 0, &sec1, &sec2, &sec3, NULL))
(gdb) list
2253 if (((ctx->mode & XQ_MILPRINT_SUMMER) == 0) && \
2254 (((ctx->mode & XQ_ALGEBRA) != 0) || \
2255 (GDKgetenv("xquery_backend") == NULL) || (strcmp(GDKgetenv("xquery_backend"),"milprint_summer") != 0)))
2256 options = COMPILE_OPTION_ALGEBRA;
2257 endif
2258 if (xquery_compile_exec(ctx, options, query, 0, &sec1, &sec2, &sec3, NULL))
2259 err = NULL;
2260 if (sec1) free(sec1);
2261 if (sec2) free(sec2);
2262 if (sec3) free(sec3);
(gdb) up
46 0x00002aaab9bb3326 in xquery_client_engine (mc=0x2aaaba3177f8) at pathfinder.c:2405
2405 err = xquery_prepare(ctx, usec, xquery);
(gdb) list
2400 if (p[1] == '4' && p[2] == '2' && p[3] == '\n' && p[4] == 0 && genType == buf && output[2] == 0) { /* use '42' as latency query test */
2401 stream_printf(GDKout, "42\n\nTrans 0.000 msec\nShred 0.000 msec\nQuery 0.000 msec\nPrint 0.000 msec\n");
2402 } else {
2403 err = xquery_change_genType(ctx, genType);
2404 if (err == NULL)
2405 err = xquery_prepare(ctx, usec, xquery);
2406 if (err && err != xquery_nondescriptive_error) {
2407 /* report errors back to client */
2408 stream_write(ctx->fderr, err, strlen(err), 1);
2409 }
(gdb) up
47 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3177f8) at mapi.c:316
316 fc->engine(fc);
(gdb) list
311 if (fc->inuse == 2)
312 break;
313
314 fc->thread->data[0] = fc->c->fdout;
315 fc->thread->data[1] = fc->c->fdin;
316 fc->engine(fc);
317 fc->c->mode = STARTING;
318
319 mapi_client_end(fc);
320 fc->thread->data[0] = NULL;
(gdb) up
48 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
(gdb) list
321 fc->thread->data[1] = NULL;
322 /* possible race condition, but net result is limited */
323 if (f->clients > f->cache_limit) {
324 break;
325 }
326 fc->inuse = 0;
327 }
328 fc->inuse = 2;
329 f->f_free(fc);
330 mapi_client_free(fc);
(gdb) up
49 0x00000036638ce86d in clone () from /lib64/libc.so.6
(gdb) list
331 }
332
333 mapi_client *MAPIclient(stream *fdin, stream *fdout, char *lang )
334 {
335 mapi_client *fc = NULL;
336 mapi_frontend *f = NULL;
337 Client c;
338
339 f = find_frontend(lang);
340
(gdb) up
50 0x0000000000000000 in ?? ()
(gdb) list
341 if (!f)
342 return NULL;
343
344 fc = mapi_client_find(f);
345 if (!fc) {
346 if (!(fc = mapi_client_alloc(f, monet_clients, 0, fdout)))
347 return NULL;
348 }
349 if (strcmp(lang, "xquery") == 0 &&
350 fc->t == ~(MT_Id) 0 &&
## Comment 10888
Date: 2009-02-05 09:15:12 +0100
From: @drstmane
Hoi Floris,
thanks for the detailed report.
You did not by any chance also print the content of variables in the vincinity of the code where the segfault occured?
E.g., "bid", "ii", "batlist[ii]"
Or do you still have your debugger with Mserver running (or have a core dump) and could hence still print these values?
Thanks!
Stefan
## Comment 10889
Date: 2009-02-05 12:49:54 +0100
From: Floris Ouwendijk <<floris233>>
It's still in the debugger, because I expected the question but had no idea of which values would be of interest. :-)
Here are some values (merged with requests from Peter):
Frame 0 CMDmposjoin:
(gdb) p ii
$4 = 1
(gdb) p bid
$5 = 9640
(gdb) p batlist[ii]
$6 = (BAT *) 0x0
(gdb) p BATprint(pre)
-------------------------
t h name
void oid type
-------------------------
[ 0@0, 1@0 ]
[ 1@0, 0@0 ]
[ 2@0, 7307@0 ]
[ 3@0, 7306@0 ]
[ 4@0, 7325@0 ]
[ 5@0, 7324@0 ]
[ 6@0, 15526@0 ]
[ 7@0, 15525@0 ]
[ 8@0, 23727@0 ]
[ 9@0, 23726@0 ]
[ 10@0, 23737@0 ]
[ 11@0, 23736@0 ]
[ 12@0, 31043@0 ]
[ 13@0, 31042@0 ]
[ 14@0, 39244@0 ]
[ 15@0, 39243@0 ]
[ 16@0, 46550@0 ]
[ 17@0, 46549@0 ]
[ 18@0, 54751@0 ]
[ 19@0, 54750@0 ]
[ 20@0, 62057@0 ]
[ 21@0, 62056@0 ]
[ 22@0, 64908@0 ]
[ 23@0, 64907@0 ]
[ 24@0, 67759@0 ]
[ 25@0, 67758@0 ]
[ 26@0, 70610@0 ]
[ 27@0, 70609@0 ]
$7 = 16843009
(gdb) p BATprint(cont)
-----------------
h t name
void oid type
-----------------
[ 0@0, 2@0 ]
[ 1@0, 2@0 ]
[ 2@0, 2@0 ]
[ 3@0, 2@0 ]
[ 4@0, 2@0 ]
[ 5@0, 2@0 ]
[ 6@0, 2@0 ]
[ 7@0, 2@0 ]
[ 8@0, 2@0 ]
[ 9@0, 2@0 ]
[ 10@0, 2@0 ]
[ 11@0, 2@0 ]
[ 12@0, 2@0 ]
[ 13@0, 2@0 ]
[ 14@0, 2@0 ]
[ 15@0, 2@0 ]
[ 16@0, 2@0 ]
[ 17@0, 2@0 ]
[ 18@0, 2@0 ]
[ 19@0, 2@0 ]
[ 20@0, 2@0 ]
[ 21@0, 2@0 ]
[ 22@0, 2@0 ]
[ 23@0, 2@0 ]
[ 24@0, 2@0 ]
[ 25@0, 2@0 ]
[ 26@0, 2@0 ]
[ 27@0, 2@0 ]
$8 = 16843009
stack 2:
(gdb) p VARfind(&stk, "loc")->binding.val.sval
$9 = 0x2ac1f6481668 "tool"
And finally:
(gdb) thr apply all bt
Thread 32464 (Thread 47195725654336 (LWP 406)):
0 0x00002aaab876c549 in CMDmposjoin (res=0x2aec9c757510, pre=0x2ac1f33e65d0, cont=0x2ac202654b88, ws_item=0x2ad0a15f34d8) at pf_support.c:9886
1 0x00002aaab873d097 in CMDmposjoin_unpack2001592764 (argc=4, argv=0x2aec9c757510) at pf_support.glue.c:318
2 0x00002aaaabbfed97 in interpret (stk=2458, lt=0x2ac66766a6f8, res=0x2aec9c757a20) at monet_interpreter.c:1070
3 0x00002aaaabbfb8a7 in interpret_params (stk=2458, lt=0x2ac66766a698, params=0x2aec9c757c50, fcn_nme=0x8f61b8 "mposjoin") at monet_interpreter.c:282
4 0x00002aaaabbfddd3 in interpret (stk=2458, lt=0x2ac66766a678, res=0x2aec9c764e10) at monet_interpreter.c:884
5 0x00002aaaabc095cf in interpret_assignment (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:2152
6 0x00002aaaabbfc900 in interpret (stk=2458, lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:638
7 0x00002aaaabc098ce in interpret_seqblock (stk=2458, lt=0x2ac66766a5d8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
8 0x00002aaaabbfc991 in interpret (stk=832, lt=0x2ac66766a5d8, res=0x2aec9c764e10) at monet_interpreter.c:654
9 0x00002aaaabbfcb15 in interpret (stk=832, lt=0x2ac66766a4b8, res=0x2aec9c764e10) at monet_interpreter.c:683
10 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac2013d8748, res=0x2aec9c764e10) at monet_interpreter.c:696
11 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac66767cd08, res=0x2aec9c764e10) at monet_interpreter.c:696
12 0x00002aaaabc098ce in interpret_seqblock (stk=832, lt=0x2ac66785f8c8, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
13 0x00002aaaabbfc991 in interpret (stk=3658, lt=0x2ac66785f8c8, res=0x2aec9c764e10) at monet_interpreter.c:654
14 0x00002aaaabbfcb15 in interpret (stk=3658, lt=0x2ac66785f7a0, res=0x2aec9c764e10) at monet_interpreter.c:683
15 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2abad4ba18f8, res=0x2aec9c764e10) at monet_interpreter.c:696
16 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac6672d4248, res=0x2aec9c764e10) at monet_interpreter.c:696
17 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac34d4b9328, res=0x2aec9c764e10) at monet_interpreter.c:696
18 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad085319508, res=0x2aec9c764e10) at monet_interpreter.c:696
19 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2017071f8, res=0x2aec9c764e10) at monet_interpreter.c:696
20 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2022fd538, res=0x2aec9c764e10) at monet_interpreter.c:696
21 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d84e28, res=0x2aec9c764e10) at monet_interpreter.c:696
22 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad500d348e8, res=0x2aec9c764e10) at monet_interpreter.c:696
23 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2024e21c8, res=0x2aec9c764e10) at monet_interpreter.c:696
24 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad7b66f07c8, res=0x2aec9c764e10) at monet_interpreter.c:696
25 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d80e38, res=0x2aec9c764e10) at monet_interpreter.c:696
26 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac65e984a68, res=0x2aec9c764e10) at monet_interpreter.c:696
27 0x00002aaaabc098ce in interpret_seqblock (stk=3658, lt=0x341b7788, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
28 0x00002aaaabbfc991 in interpret (stk=3613, lt=0x341b7788, res=0x2aec9c764e10) at monet_interpreter.c:654
29 0x00002aaaabc098ce in interpret_seqblock (stk=3613, lt=0x2ad08507f598, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
30 0x00002aaaabbfc991 in interpret (stk=1573, lt=0x2ad08507f598, res=0x2aec9c764e10) at monet_interpreter.c:654
31 0x00002aaaabbfe72c in interpret (stk=1573, lt=0x2ad0a0d283d8, res=0x2aec9c764e10) at monet_interpreter.c:1044
32 0x00002aaaabc095cf in interpret_assignment (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:2152
33 0x00002aaaabbfc900 in interpret (stk=1573, lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:638
34 0x00002aaaabc098ce in interpret_seqblock (stk=1573, lt=0x2ac201b44288, res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
35 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2abad4c284d0, res=0x2aec9c764e10) at monet_interpreter.c:654
36 0x00002aaaab1a276b in CMDcatch (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at builtin.c:1065
37 0x00002aaaabbfd551 in interpret (stk=19, lt=0x2abad4c284a8, res=0x2aec9c764e10) at monet_interpreter.c:808
38 0x00002aaaabc095cf in interpret_assignment (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:2152
39 0x00002aaaabbfc900 in interpret (stk=19, lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:638
40 0x00002aaaabc098ce in interpret_seqblock (stk=19, lt=0x2ad05e51af58, res=0x2aec9c764e10, scope=0) at monet_interpreter.c:2200
41 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2ad083b04b48, res=0x2aec9c764e10) at monet_interpreter.c:654
42 0x00002aaab9babd35 in xquery_tree_exec (ctx=0x2ab6378f5ea8, t=0x2ad083b04b48, repeat=0) at pathfinder.c:239
43 0x00002aaab9bac296 in xquery_mil_exec (ctx=0x2ab6378f5ea8,
buf=0x2ac31d5f4e40 "var tijah_scoreDB;\nvar tijah_ftiTape;\nvar xrpc_qid;\nvar xrpc_caller;\nvar xrpc_hdl;\nvar xrpc_seqnr;\nvar xrpc_timeout;\nvar xrpc_mode;\nvar xrpc_module;\nvar xrpc_method;\nxrpc_qid := \"\";\nxrpc_caller := \"\";"...) at pathfinder.c:297
44 0x00002aaab9bacbe7 in xquery_compile_exec (ctx=0x2ab6378f5ea8, options=2,
xquery=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"..., is_url=0, prologue=0x2aec9c765330, query=0x2aec9c765328,
epilogue=0x2aec9c765320, module=0x0) at pathfinder.c:445
45 0x00002aaab9bb2cf0 in xquery_prepare (ctx=0x2ab6378f5ea8, usec=659415161738,
query=0x2ab6345f7719 "element job {attribute tool {\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for $xirafNode in subsequence( for $xirafIter in (\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio"...) at pathfinder.c:2258
46 0x00002aaab9bb3326 in xquery_client_engine (mc=0x2aaaba3177f8) at pathfinder.c:2405
47 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3177f8) at mapi.c:316
48 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
49 0x00000036638ce86d in clone () from /lib64/libc.so.6
50 0x0000000000000000 in ?? ()
Thread 32129 (Thread 47192036505920 (LWP 32484)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac28aee40, buf=0x2aebc0926f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac28aee40, val=0x2aebc0926f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1304b20, buf=0x2ab634cf7608, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1304b20, buf=0x2ab634cf7608, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317790) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317790) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32128 (Thread 47192028113216 (LWP 32483)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae82e11470, buf=0x2aebc0125f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae82e11470, val=0x2aebc0125f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac2d6db50, buf=0x2ab6348fa7d8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac2d6db50, buf=0x2ab6348fa7d8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317728) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317728) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32127 (Thread 47192019720512 (LWP 32482)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae800839d0, buf=0x2aebbf924f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae800839d0, val=0x2aebbf924f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae83086af0, buf=0x2ab635e6c7e8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae83086af0, buf=0x2ab635e6c7e8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3176c0) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3176c0) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32126 (Thread 47192011327808 (LWP 32481)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae8037de00, buf=0x2aebbf123f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae8037de00, val=0x2aebbf123f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac087f160, buf=0x2ab63499c6b8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac087f160, buf=0x2ab63499c6b8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317658) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317658) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32125 (Thread 47192002935104 (LWP 32480)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac0bdeff0, buf=0x2aebbe922f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac0bdeff0, val=0x2aebbe922f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64d02d0, buf=0x2ab634e7c408, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64d02d0, buf=0x2ab634e7c408, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3175f0) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3175f0) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32124 (Thread 47152199379264 (LWP 32479)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab63405e190, buf=0x2ae27a181f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab63405e190, val=0x2ae27a181f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64cdb20, buf=0x2ab634803d28, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64cdb20, buf=0x2ab634803d28, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317588) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317588) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32123 (Thread 47152190986560 (LWP 32478)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab637827560, buf=0x2ae279980f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab637827560, val=0x2ae279980f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64e3c40, buf=0x2ab63601d1a8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64e3c40, buf=0x2ab63601d1a8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317520) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317520) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32122 (Thread 47152084199744 (LWP 32477)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab63400d870, buf=0x2ae2733a9f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab63400d870, val=0x2ae2733a9f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae81124140, buf=0x2aae81d4c458, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae81124140, buf=0x2aae81d4c458, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3174b8) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3174b8) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32121 (Thread 47152075807040 (LWP 32476)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac0b5a120, buf=0x2ae272ba8f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac0b5a120, val=0x2ae272ba8f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac26fb3f0, buf=0x2aae8189d988, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac26fb3f0, buf=0x2aae8189d988, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317450) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317450) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32120 (Thread 47152067414336 (LWP 32475)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab635b06760, buf=0x2ae2723a7f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab635b06760, val=0x2ae2723a7f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1ae3b00, buf=0x2aae81a91c18, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1ae3b00, buf=0x2aae81a91c18, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3173e8) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3173e8) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32119 (Thread 47152059021632 (LWP 32474)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab634917940, buf=0x2ae271ba6f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab634917940, val=0x2ae271ba6f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac267ee80, buf=0x2ab634a98f48, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac267ee80, buf=0x2ab634a98f48, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317380) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317380) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32118 (Thread 47152050628928 (LWP 32473)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac050fc10, buf=0x2ae2713a5f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac050fc10, val=0x2ae2713a5f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1f85560, buf=0x2ab6348d3098, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1f85560, buf=0x2ab6348d3098, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317318) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317318) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32117 (Thread 47151460723008 (LWP 32472)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab6361019b0, buf=0x2ae24e111f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab6361019b0, val=0x2ae24e111f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac05eb8c0, buf=0x2ab634795018, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac05eb8c0, buf=0x2ab634795018, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3172b0) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3172b0) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32116 (Thread 47151452330304 (LWP 32471)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac35d2d90, buf=0x2ae24d910f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac35d2d90, val=0x2ae24d910f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac652b720, buf=0x2ab63468fc18, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac652b720, buf=0x2ab63468fc18, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317248) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317248) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32115 (Thread 47151443937600 (LWP 32470)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac1712c10, buf=0x2ae24d10ff4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac1712c10, val=0x2ae24d10ff4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae834cec30, buf=0x2aae81d18858, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae834cec30, buf=0x2aae81d18858, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3170a8) at pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3170a8) at mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 5 (Thread 1107310912 (LWP 6853)):
0 OIDnew (inc=576618312) at gdk_atoms.c:2507
1 0x00002aaaac631d8f in ALIGNsetH (b1=0x225e7f70, b2=0x2ad0707dd560) at gdk_align.c:35
2 0x00002aaaac8a2eeb in BATcopy (b=0x2ad0707dd538, ht=0, tt=13, writable=0) at gdk_bat.c:739
3 0x00002aaaac705907 in BATkunion (l=0x2ad0707dd538, r=0x2ac200fd91f8) at gdk_setop.c:12995
4 0x00002aaaaaacee67 in CMDkunion (result=0x41ffcbe0, left=0x2ac200fd91f8, right=0x2ad0707dd538) at algebra.c:2128
5 0x00002aaaaaabeb6d in CMDkunion_unpack492838038 (argc=3, argv=0x41ffcbe0) at algebra.glue.c:1910
6 0x00002aaaabbfed97 in interpret (stk=548, lt=0x10329b0, res=0x41ffd0f0) at monet_interpreter.c:1070
7 0x00002aaaabbfb8a7 in interpret_params (stk=548, lt=0x1032988, params=0x41ffd1f0, fcn_nme=0x2aaaabc81d3c "batloop") at monet_interpreter.c:282
8 0x00002aaaabc26577 in interpret_iterator (stk=548, lt=0x1033bc8, parallel=1) at monet_interpreter.c:6567
9 0x00002aaaabbfd176 in interpret (stk=548, lt=0x1033bc8, res=0x420030e0) at monet_interpreter.c:736
10 0x00002aaaabc098ce in interpret_seqblock (stk=548, lt=0x15a24e8, res=0x420030e0, scope=1) at monet_interpreter.c:2200
11 0x00002aaaabbfc991 in interpret (stk=553, lt=0x15a24e8, res=0x420030e0) at monet_interpreter.c:654
12 0x00002aaaabbfe72c in interpret (stk=553, lt=0x1620418, res=0x420030e0) at monet_interpreter.c:1044
13 0x00002aaaab1a276b in CMDcatch (stk=553, lt=0x16203c0, res=0x420030e0) at builtin.c:1065
14 0x00002aaaabbfd551 in interpret (stk=553, lt=0x16203c0, res=0x420030e0) at monet_interpreter.c:808
15 0x00002aaaabc098ce in interpret_seqblock (stk=553, lt=0x668d28, res=0x420030e0, scope=1) at monet_interpreter.c:2200
16 0x00002aaaabbfc991 in interpret (stk=552, lt=0x668d28, res=0x420030e0) at monet_interpreter.c:654
17 0x00002aaaabc012ac in interpret_while (stk=552, lt=0x668cb0, res=0x420030e0) at monet_interpreter.c:1187
18 0x00002aaaabbfcc8b in interpret (stk=552, lt=0x668cb0, res=0x420030e0) at monet_interpreter.c:721
19 0x00002aaaabc098ce in interpret_seqblock (stk=552, lt=0x668ac8, res=0x420030e0, scope=1) at monet_interpreter.c:2200
20 0x00002aaaabbfc991 in interpret (stk=4, lt=0x668ac8, res=0x420030e0) at monet_interpreter.c:654
21 0x00002aaaabbfe72c in interpret (stk=4, lt=0x161e108, res=0x420030e0) at monet_interpreter.c:1044
22 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3d98, q=0x161e228, res=0x420030e0) at monet_queue.c:342
23 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3d98, preference=0x0) at monet_queue.c:368
24 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff4480ad14) at monet_process.c:45
25 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
26 0x00000036638ce86d in clone () from /lib64/libc.so.6
27 0x0000000000000000 in ?? ()
Thread 4 (Thread 1098918208 (LWP 6852)):
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba5277ba in shttpd_poll (ctx=0x41801920, milliseconds=200) at shttpd.c:2981
2 0x00002aaaba52ac14 in CMDrpcd_start (port=0x41801b80, open=0x41801b90 "\001", options=0x2aaabc001078 "") at xrpc_server.c:661
3 0x00002aaaba528a17 in CMDrpcd_start_unpack1282044456 (argc=4, argv=0x41801b70) at xrpc_server.glue.c:41
4 0x00002aaaabbfed97 in interpret (stk=3, lt=0x15e0298, res=0x418020e0) at monet_interpreter.c:1070
5 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3cf0, q=0x15e04f8, res=0x418020e0) at monet_queue.c:342
6 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3cf0, preference=0x0) at monet_queue.c:368
7 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff44809ff4) at monet_process.c:45
8 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
9 0x00000036638ce86d in clone () from /lib64/libc.so.6
10 0x0000000000000000 in ?? ()
Thread 3 (Thread 1090525504 (LWP 6851)):
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba113ec4 in MAPIlisten (stk=2, lt=0x1357818, res=0x410010e0) at mapi.c:729
2 0x00002aaaabbfd551 in interpret (stk=2, lt=0x1357818, res=0x410010e0) at monet_interpreter.c:808
3 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3c48, q=0x1357a58, res=0x410010e0) at monet_queue.c:342
4 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3c48, preference=0x0) at monet_queue.c:368
5 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff448093b4) at monet_process.c:45
6 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
7 0x00000036638ce86d in clone () from /lib64/libc.so.6
8 0x0000000000000000 in ?? ()
Thread 2 (Thread 1082132800 (LWP 6850)):
0 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaac9af135 in MT_sleep_ms (ms=500) at gdk_posix.c:1774
2 0x00002aaaac70c192 in GDKvmtrim (limit=0x2aaaaccdd660) at gdk_utils.c:1350
3 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
4 0x00000036638ce86d in clone () from /lib64/libc.so.6
5 0x0000000000000000 in ?? ()
Thread 1 (Thread 46912539207168 (LWP 6847)):
0 0x00000036638c0e1b in __read_nocancel () from /lib64/libc.so.6
1 0x000000366386a617 in _IO_new_file_underflow () from /lib64/libc.so.6
2 0x000000366386930e in _IO_file_xsgetn_internal () from /lib64/libc.so.6
3 0x000000366385f692 in fread () from /lib64/libc.so.6
4 0x00002aaaacfb5d32 in file_read (s=0x605d60, buf=0x66c7f8, elmsize=1, cnt=1) at stream.c:457
5 0x00002aaaacfb53f1 in stream_read (s=0x605d60, buf=0x66c7f8, elmsize=1, cnt=1) at stream.c:169
6 0x00002aaaabc31f17 in readClient (c=0x2aaaabe966c0) at monet_client.c:428
7 0x00002aaaabc32752 in serveClient (stk=0, lt=0x63cf48, res=0x7fff4480baa0) at monet_client.c:622
8 0x00002aaaabbfd551 in interpret (stk=0, lt=0x63cf48, res=0x7fff4480baa0) at monet_interpreter.c:808
9 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3ba0, q=0x12469f28, res=0x7fff4480baa0) at monet_queue.c:342
10 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3ba0, preference=0x0) at monet_queue.c:368
11 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff4480bba4) at monet_process.c:45
12 0x0000000000401f94 in main (argc=4, av=0x7fff4480bcc8) at Mserver.c:242
0x00002aaab876c549 9886 fake_item = is_fake_project(batlist[ii]);
## Comment 10890
Date: 2009-02-06 14:03:56 +0100
From: @peterboncz
Dit is de query:
element job {attribute tool {"carving/headerfinder-tool"},attribute
project { "fileset2"}, for $xirafNode in subsequence( for $xirafIter in
(
doc("fileset2.xml")//volume[not(.//filesystem)]
union
doc("fileset2.xml")//image[not(properties/type="LocalFolder") and
not(.//volume) and not(.//filesystem)]
)
where $xirafIter/@xid
and not($xirafIter/container/@tool[.="carving/headerfinder-tool"])and
not(some $x in (for $taskIter in
doc("02FF778C-312B-8F82-26E3-DD737721420F.xml")//run[@tool="carving/head
erfinder-tool"]//task/@xid return $taskIter cast as xs:integer)
satisfies $x = $xirafIter/@xid)
and $xirafIter/properties/stream/@xstart
return $xirafIter, 1, 16384)
return element { "item" } {$xirafNode/@xid,if
(exists($xirafNode/properties/point/@xpoint)) then
($xirafNode/properties/point/@xpoint,
$xirafNode/../../properties/stream/@xstart,
$xirafNode/../../properties/stream/@xend)
else
($xirafNode/properties/stream/@xstart,
$xirafNode/properties/stream/@xend)
,element properties { ()}
}}
fileset2.xml is een standaard groot document met data.
02FF778C-312B-8F82-26E3-DD737721420F.xml is een log document.
Er staan geen errors in de log tot een paar uur ervoor (begin van de
test).
(gdb) p BBP[bid]
$10 = {b = {0x0, 0x0}, nme = {0x17fbb268 "tmp_22650", 0x0}, bak =
{0x17fbb268 "tmp_22650", 0x0}, next = {8076, 7964}, cache =
0x2ae275fc27b8,
path = 0x2ac34deb8c58 "02/26/22650", refs = 1, lrefs = 1, lastused =
1117092157, status = 4}
Er zijn wel een paar updates (do insert), echter naar ik kan zien alleen
in het begin van het document, en 20 minuten voor het probleem optrad.
Query daarvan is:
for $i in doc("projinit29082.xml")/XIRAF/*
return do insert $i
into
doc("fileset2.xml")/project/device[properties/identifier="pc01"]
We draaien wel concurrent queries, maar zo te zien waren er op dat
moment geen andere queries actief. Vlak ervoor waren wel vergelijkbare
queries bezig.
Frame 0 CMDmposjoin:
(gdb) p ii
$4 = 1
(gdb) p bid
$5 = 9640
(gdb) p batlist[ii]
$6 = (BAT *) 0x0
(gdb) p BATprint(pre)
-------------------------
t h name
void oid type
-------------------------
[ 0@0, 1@0 ]
[ 1@0, 0@0 ]
[ 2@0, 7307@0 ]
[ 3@0, 7306@0 ]
[ 4@0, 7325@0 ]
[ 5@0, 7324@0 ]
[ 6@0, 15526@0 ]
[ 7@0, 15525@0 ]
[ 8@0, 23727@0 ]
[ 9@0, 23726@0 ]
[ 10@0, 23737@0 ]
[ 11@0, 23736@0 ]
[ 12@0, 31043@0 ]
[ 13@0, 31042@0 ]
[ 14@0, 39244@0 ]
[ 15@0, 39243@0 ]
[ 16@0, 46550@0 ]
[ 17@0, 46549@0 ]
[ 18@0, 54751@0 ]
[ 19@0, 54750@0 ]
[ 20@0, 62057@0 ]
[ 21@0, 62056@0 ]
[ 22@0, 64908@0 ]
[ 23@0, 64907@0 ]
[ 24@0, 67759@0 ]
[ 25@0, 67758@0 ]
[ 26@0, 70610@0 ]
[ 27@0, 70609@0 ]
$7 = 16843009
(gdb) p BATprint(cont)
-----------------
h t name
void oid type
-----------------
[ 0@0, 2@0 ]
[ 1@0, 2@0 ]
[ 2@0, 2@0 ]
[ 3@0, 2@0 ]
[ 4@0, 2@0 ]
[ 5@0, 2@0 ]
[ 6@0, 2@0 ]
[ 7@0, 2@0 ]
[ 8@0, 2@0 ]
[ 9@0, 2@0 ]
[ 10@0, 2@0 ]
[ 11@0, 2@0 ]
[ 12@0, 2@0 ]
[ 13@0, 2@0 ]
[ 14@0, 2@0 ]
[ 15@0, 2@0 ]
[ 16@0, 2@0 ]
[ 17@0, 2@0 ]
[ 18@0, 2@0 ]
[ 19@0, 2@0 ]
[ 20@0, 2@0 ]
[ 21@0, 2@0 ]
[ 22@0, 2@0 ]
[ 23@0, 2@0 ]
[ 24@0, 2@0 ]
[ 25@0, 2@0 ]
[ 26@0, 2@0 ]
[ 27@0, 2@0 ]
$8 = 16843009
stack 2:
(gdb) p VARfind(&stk, "loc")->binding.val.sval
$9 = 0x2ac1f6481668 "tool"
And finally:
(gdb) thr apply all bt
Thread 32464 (Thread 47195725654336 (LWP 406)):
0 0x00002aaab876c549 in CMDmposjoin (res=0x2aec9c757510,
pre=0x2ac1f33e65d0, cont=0x2ac202654b88, ws_item=0x2ad0a15f34d8) at
pf_support.c:9886
1 0x00002aaab873d097 in CMDmposjoin_unpack2001592764 (argc=4,
argv=0x2aec9c757510) at pf_support.glue.c:318
2 0x00002aaaabbfed97 in interpret (stk=2458, lt=0x2ac66766a6f8,
res=0x2aec9c757a20) at monet_interpreter.c:1070
3 0x00002aaaabbfb8a7 in interpret_params (stk=2458, lt=0x2ac66766a698,
params=0x2aec9c757c50, fcn_nme=0x8f61b8 "mposjoin") at
monet_interpreter.c:282
4 0x00002aaaabbfddd3 in interpret (stk=2458, lt=0x2ac66766a678,
res=0x2aec9c764e10) at monet_interpreter.c:884
5 0x00002aaaabc095cf in interpret_assignment (stk=2458,
lt=0x2ac66766a628, res=0x2aec9c764e10) at monet_interpreter.c:2152
6 0x00002aaaabbfc900 in interpret (stk=2458, lt=0x2ac66766a628,
res=0x2aec9c764e10) at monet_interpreter.c:638
7 0x00002aaaabc098ce in interpret_seqblock (stk=2458,
lt=0x2ac66766a5d8, res=0x2aec9c764e10, scope=1) at
monet_interpreter.c:2200
8 0x00002aaaabbfc991 in interpret (stk=832, lt=0x2ac66766a5d8,
res=0x2aec9c764e10) at monet_interpreter.c:654
9 0x00002aaaabbfcb15 in interpret (stk=832, lt=0x2ac66766a4b8,
res=0x2aec9c764e10) at monet_interpreter.c:683
10 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac2013d8748,
res=0x2aec9c764e10) at monet_interpreter.c:696
11 0x00002aaaabbfcbb0 in interpret (stk=832, lt=0x2ac66767cd08,
res=0x2aec9c764e10) at monet_interpreter.c:696
12 0x00002aaaabc098ce in interpret_seqblock (stk=832,
lt=0x2ac66785f8c8, res=0x2aec9c764e10, scope=1) at
monet_interpreter.c:2200
13 0x00002aaaabbfc991 in interpret (stk=3658, lt=0x2ac66785f8c8,
res=0x2aec9c764e10) at monet_interpreter.c:654
14 0x00002aaaabbfcb15 in interpret (stk=3658, lt=0x2ac66785f7a0,
res=0x2aec9c764e10) at monet_interpreter.c:683
15 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2abad4ba18f8,
res=0x2aec9c764e10) at monet_interpreter.c:696
16 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac6672d4248,
res=0x2aec9c764e10) at monet_interpreter.c:696
17 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac34d4b9328,
res=0x2aec9c764e10) at monet_interpreter.c:696
18 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad085319508,
res=0x2aec9c764e10) at monet_interpreter.c:696
19 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2017071f8,
res=0x2aec9c764e10) at monet_interpreter.c:696
20 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2022fd538,
res=0x2aec9c764e10) at monet_interpreter.c:696
21 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d84e28,
res=0x2aec9c764e10) at monet_interpreter.c:696
22 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad500d348e8,
res=0x2aec9c764e10) at monet_interpreter.c:696
23 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac2024e21c8,
res=0x2aec9c764e10) at monet_interpreter.c:696
24 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad7b66f07c8,
res=0x2aec9c764e10) at monet_interpreter.c:696
25 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ad0a0d80e38,
res=0x2aec9c764e10) at monet_interpreter.c:696
26 0x00002aaaabbfcbb0 in interpret (stk=3658, lt=0x2ac65e984a68,
res=0x2aec9c764e10) at monet_interpreter.c:696
27 0x00002aaaabc098ce in interpret_seqblock (stk=3658, lt=0x341b7788,
res=0x2aec9c764e10, scope=1) at monet_interpreter.c:2200
28 0x00002aaaabbfc991 in interpret (stk=3613, lt=0x341b7788,
res=0x2aec9c764e10) at monet_interpreter.c:654
29 0x00002aaaabc098ce in interpret_seqblock (stk=3613,
lt=0x2ad08507f598, res=0x2aec9c764e10, scope=1) at
monet_interpreter.c:2200
30 0x00002aaaabbfc991 in interpret (stk=1573, lt=0x2ad08507f598,
res=0x2aec9c764e10) at monet_interpreter.c:654
31 0x00002aaaabbfe72c in interpret (stk=1573, lt=0x2ad0a0d283d8,
res=0x2aec9c764e10) at monet_interpreter.c:1044
32 0x00002aaaabc095cf in interpret_assignment (stk=1573,
lt=0x2ac201b44308, res=0x2aec9c764e10) at monet_interpreter.c:2152
33 0x00002aaaabbfc900 in interpret (stk=1573, lt=0x2ac201b44308,
res=0x2aec9c764e10) at monet_interpreter.c:638
34 0x00002aaaabc098ce in interpret_seqblock (stk=1573,
lt=0x2ac201b44288, res=0x2aec9c764e10, scope=1) at
monet_interpreter.c:2200
35 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2abad4c284d0,
res=0x2aec9c764e10) at monet_interpreter.c:654
36 0x00002aaaab1a276b in CMDcatch (stk=19, lt=0x2abad4c284a8,
res=0x2aec9c764e10) at builtin.c:1065
37 0x00002aaaabbfd551 in interpret (stk=19, lt=0x2abad4c284a8,
res=0x2aec9c764e10) at monet_interpreter.c:808
38 0x00002aaaabc095cf in interpret_assignment (stk=19,
lt=0x2ac667509dc8, res=0x2aec9c764e10) at monet_interpreter.c:2152
39 0x00002aaaabbfc900 in interpret (stk=19, lt=0x2ac667509dc8,
res=0x2aec9c764e10) at monet_interpreter.c:638
40 0x00002aaaabc098ce in interpret_seqblock (stk=19, lt=0x2ad05e51af58,
res=0x2aec9c764e10, scope=0) at monet_interpreter.c:2200
41 0x00002aaaabbfc991 in interpret (stk=19, lt=0x2ad083b04b48,
res=0x2aec9c764e10) at monet_interpreter.c:654
42 0x00002aaab9babd35 in xquery_tree_exec (ctx=0x2ab6378f5ea8,
t=0x2ad083b04b48, repeat=0) at pathfinder.c:239
43 0x00002aaab9bac296 in xquery_mil_exec (ctx=0x2ab6378f5ea8,
buf=0x2ac31d5f4e40 "var tijah_scoreDB;\nvar tijah_ftiTape;\nvar
xrpc_qid;\nvar xrpc_caller;\nvar xrpc_hdl;\nvar xrpc_seqnr;\nvar
xrpc_timeout;\nvar xrpc_mode;\nvar xrpc_module;\nvar
xrpc_method;\nxrpc_qid := \"\";\nxrpc_caller := \"\";"...) at
pathfinder.c:297
44 0x00002aaab9bacbe7 in xquery_compile_exec (ctx=0x2ab6378f5ea8,
options=2,
xquery=0x2ab6345f7719 "element job {attribute tool
{\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for
$xirafNode in subsequence( for $xirafIter in
(\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio".
.., is_url=0, prologue=0x2aec9c765330, query=0x2aec9c765328,
epilogue=0x2aec9c765320, module=0x0) at pathfinder.c:445
45 0x00002aaab9bb2cf0 in xquery_prepare (ctx=0x2ab6378f5ea8,
usec=659415161738,
query=0x2ab6345f7719 "element job {attribute tool
{\"carving/headerfinder-tool\"},attribute project { \"fileset2\"}, for
$xirafNode in subsequence( for $xirafIter in
(\n\t\t\tdoc(\"fileset2.xml\")//volume[not(.//filesystem)]\n\t\t\tunio".
..) at pathfinder.c:2258
46 0x00002aaab9bb3326 in xquery_client_engine (mc=0x2aaaba3177f8) at
pathfinder.c:2405
47 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3177f8) at
mapi.c:316
48 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
49 0x00000036638ce86d in clone () from /lib64/libc.so.6
50 0x0000000000000000 in ?? ()
Thread 32129 (Thread 47192036505920 (LWP 32484)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac28aee40,
buf=0x2aebc0926f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac28aee40,
val=0x2aebc0926f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1304b20,
buf=0x2ab634cf7608, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1304b20,
buf=0x2ab634cf7608, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317790) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317790) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32128 (Thread 47192028113216 (LWP 32483)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae82e11470,
buf=0x2aebc0125f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae82e11470,
val=0x2aebc0125f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac2d6db50,
buf=0x2ab6348fa7d8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac2d6db50,
buf=0x2ab6348fa7d8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317728) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317728) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32127 (Thread 47192019720512 (LWP 32482)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae800839d0,
buf=0x2aebbf924f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae800839d0,
val=0x2aebbf924f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae83086af0,
buf=0x2ab635e6c7e8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae83086af0,
buf=0x2ab635e6c7e8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3176c0) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3176c0) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32126 (Thread 47192011327808 (LWP 32481)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aae8037de00,
buf=0x2aebbf123f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aae8037de00,
val=0x2aebbf123f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac087f160,
buf=0x2ab63499c6b8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac087f160,
buf=0x2ab63499c6b8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317658) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317658) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32125 (Thread 47192002935104 (LWP 32480)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac0bdeff0,
buf=0x2aebbe922f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac0bdeff0,
val=0x2aebbe922f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64d02d0,
buf=0x2ab634e7c408, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64d02d0,
buf=0x2ab634e7c408, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3175f0) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3175f0) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32124 (Thread 47152199379264 (LWP 32479)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab63405e190,
buf=0x2ae27a181f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab63405e190,
val=0x2ae27a181f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64cdb20,
buf=0x2ab634803d28, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64cdb20,
buf=0x2ab634803d28, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317588) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317588) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32123 (Thread 47152190986560 (LWP 32478)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab637827560,
buf=0x2ae279980f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab637827560,
val=0x2ae279980f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac64e3c40,
buf=0x2ab63601d1a8, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac64e3c40,
buf=0x2ab63601d1a8, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317520) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317520) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32122 (Thread 47152084199744 (LWP 32477)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab63400d870,
buf=0x2ae2733a9f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab63400d870,
val=0x2ae2733a9f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae81124140,
buf=0x2aae81d4c458, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae81124140,
buf=0x2aae81d4c458, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3174b8) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3174b8) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32121 (Thread 47152075807040 (LWP 32476)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac0b5a120,
buf=0x2ae272ba8f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac0b5a120,
val=0x2ae272ba8f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac26fb3f0,
buf=0x2aae8189d988, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac26fb3f0,
buf=0x2aae8189d988, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317450) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317450) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32120 (Thread 47152067414336 (LWP 32475)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab635b06760,
buf=0x2ae2723a7f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab635b06760,
val=0x2ae2723a7f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1ae3b00,
buf=0x2aae81a91c18, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1ae3b00,
buf=0x2aae81a91c18, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3173e8) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3173e8) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32119 (Thread 47152059021632 (LWP 32474)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab634917940,
buf=0x2ae271ba6f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab634917940,
val=0x2ae271ba6f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac267ee80,
buf=0x2ab634a98f48, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac267ee80,
buf=0x2ab634a98f48, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317380) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317380) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32118 (Thread 47152050628928 (LWP 32473)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac050fc10,
buf=0x2ae2713a5f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac050fc10,
val=0x2ae2713a5f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac1f85560,
buf=0x2ab6348d3098, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac1f85560,
buf=0x2ab6348d3098, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317318) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317318) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32117 (Thread 47151460723008 (LWP 32472)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2ab6361019b0,
buf=0x2ae24e111f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2ab6361019b0,
val=0x2ae24e111f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aaac05eb8c0,
buf=0x2ab634795018, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aaac05eb8c0,
buf=0x2ab634795018, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3172b0) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3172b0) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32116 (Thread 47151452330304 (LWP 32471)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac35d2d90,
buf=0x2ae24d910f4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac35d2d90,
val=0x2ae24d910f4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2abac652b720,
buf=0x2ab63468fc18, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2abac652b720,
buf=0x2ab63468fc18, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba317248) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba317248) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 32115 (Thread 47151443937600 (LWP 32470)):
0 0x000000366440cc8b in __read_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaacfb6c49 in socket_read (s=0x2aaac1712c10,
buf=0x2ae24d10ff4e, elmsize=2, cnt=1) at stream.c:1305
2 0x00002aaaacfb93fc in stream_readSht (s=0x2aaac1712c10,
val=0x2ae24d10ff4e) at stream.c:2917
3 0x00002aaaacfb8a71 in bs_read (ss=0x2aae834cec30,
buf=0x2aae81d18858, elmsize=1, cnt=16363) at stream.c:2612
4 0x00002aaaacfb53f1 in stream_read (s=0x2aae834cec30,
buf=0x2aae81d18858, elmsize=1, cnt=16363) at stream.c:169
5 0x00002aaab9bb2f05 in xquery_client_engine (mc=0x2aaaba3170a8) at
pathfinder.c:2318
6 0x00002aaaba112f6a in mapi_client_engine (FC=0x2aaaba3170a8) at
mapi.c:316
7 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
8 0x00000036638ce86d in clone () from /lib64/libc.so.6
9 0x0000000000000000 in ?? ()
Thread 5 (Thread 1107310912 (LWP 6853)):
0 OIDnew (inc=576618312) at gdk_atoms.c:2507
1 0x00002aaaac631d8f in ALIGNsetH (b1=0x225e7f70, b2=0x2ad0707dd560)
at gdk_align.c:35
2 0x00002aaaac8a2eeb in BATcopy (b=0x2ad0707dd538, ht=0, tt=13,
writable=0) at gdk_bat.c:739
3 0x00002aaaac705907 in BATkunion (l=0x2ad0707dd538, r=0x2ac200fd91f8)
at gdk_setop.c:12995
4 0x00002aaaaaacee67 in CMDkunion (result=0x41ffcbe0,
left=0x2ac200fd91f8, right=0x2ad0707dd538) at algebra.c:2128
5 0x00002aaaaaabeb6d in CMDkunion_unpack492838038 (argc=3,
argv=0x41ffcbe0) at algebra.glue.c:1910
6 0x00002aaaabbfed97 in interpret (stk=548, lt=0x10329b0,
res=0x41ffd0f0) at monet_interpreter.c:1070
7 0x00002aaaabbfb8a7 in interpret_params (stk=548, lt=0x1032988,
params=0x41ffd1f0, fcn_nme=0x2aaaabc81d3c "batloop") at
monet_interpreter.c:282
8 0x00002aaaabc26577 in interpret_iterator (stk=548, lt=0x1033bc8,
parallel=1) at monet_interpreter.c:6567
9 0x00002aaaabbfd176 in interpret (stk=548, lt=0x1033bc8,
res=0x420030e0) at monet_interpreter.c:736
10 0x00002aaaabc098ce in interpret_seqblock (stk=548, lt=0x15a24e8,
res=0x420030e0, scope=1) at monet_interpreter.c:2200
11 0x00002aaaabbfc991 in interpret (stk=553, lt=0x15a24e8,
res=0x420030e0) at monet_interpreter.c:654
12 0x00002aaaabbfe72c in interpret (stk=553, lt=0x1620418,
res=0x420030e0) at monet_interpreter.c:1044
13 0x00002aaaab1a276b in CMDcatch (stk=553, lt=0x16203c0,
res=0x420030e0) at builtin.c:1065
14 0x00002aaaabbfd551 in interpret (stk=553, lt=0x16203c0,
res=0x420030e0) at monet_interpreter.c:808
15 0x00002aaaabc098ce in interpret_seqblock (stk=553, lt=0x668d28,
res=0x420030e0, scope=1) at monet_interpreter.c:2200
16 0x00002aaaabbfc991 in interpret (stk=552, lt=0x668d28,
res=0x420030e0) at monet_interpreter.c:654
17 0x00002aaaabc012ac in interpret_while (stk=552, lt=0x668cb0,
res=0x420030e0) at monet_interpreter.c:1187
18 0x00002aaaabbfcc8b in interpret (stk=552, lt=0x668cb0,
res=0x420030e0) at monet_interpreter.c:721
19 0x00002aaaabc098ce in interpret_seqblock (stk=552, lt=0x668ac8,
res=0x420030e0, scope=1) at monet_interpreter.c:2200
20 0x00002aaaabbfc991 in interpret (stk=4, lt=0x668ac8, res=0x420030e0)
at monet_interpreter.c:654
21 0x00002aaaabbfe72c in interpret (stk=4, lt=0x161e108,
res=0x420030e0) at monet_interpreter.c:1044
22 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3d98, q=0x161e228,
res=0x420030e0) at monet_queue.c:342
23 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3d98, preference=0x0)
at monet_queue.c:368
24 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff4480ad14) at
monet_process.c:45
25 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
26 0x00000036638ce86d in clone () from /lib64/libc.so.6
27 0x0000000000000000 in ?? ()
Thread 4 (Thread 1098918208 (LWP 6852)):
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba5277ba in shttpd_poll (ctx=0x41801920, milliseconds=200)
at shttpd.c:2981
2 0x00002aaaba52ac14 in CMDrpcd_start (port=0x41801b80,
open=0x41801b90 "\001", options=0x2aaabc001078 "") at xrpc_server.c:661
3 0x00002aaaba528a17 in CMDrpcd_start_unpack1282044456 (argc=4,
argv=0x41801b70) at xrpc_server.glue.c:41
4 0x00002aaaabbfed97 in interpret (stk=3, lt=0x15e0298,
res=0x418020e0) at monet_interpreter.c:1070
5 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3cf0, q=0x15e04f8,
res=0x418020e0) at monet_queue.c:342
6 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3cf0, preference=0x0)
at monet_queue.c:368
7 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff44809ff4) at
monet_process.c:45
8 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
9 0x00000036638ce86d in clone () from /lib64/libc.so.6
10 0x0000000000000000 in ?? ()
Thread 3 (Thread 1090525504 (LWP 6851)):
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba113ec4 in MAPIlisten (stk=2, lt=0x1357818,
res=0x410010e0) at mapi.c:729
2 0x00002aaaabbfd551 in interpret (stk=2, lt=0x1357818,
res=0x410010e0) at monet_interpreter.c:808
3 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3c48, q=0x1357a58,
res=0x410010e0) at monet_queue.c:342
4 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3c48, preference=0x0)
at monet_queue.c:368
5 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff448093b4) at
monet_process.c:45
6 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
7 0x00000036638ce86d in clone () from /lib64/libc.so.6
8 0x0000000000000000 in ?? ()
Thread 2 (Thread 1082132800 (LWP 6850)):
0 0x000000366440d531 in __nanosleep_nocancel () from
/lib64/libpthread.so.0
1 0x00002aaaac9af135 in MT_sleep_ms (ms=500) at gdk_posix.c:1774
2 0x00002aaaac70c192 in GDKvmtrim (limit=0x2aaaaccdd660) at
gdk_utils.c:1350
3 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
4 0x00000036638ce86d in clone () from /lib64/libc.so.6
5 0x0000000000000000 in ?? ()
Thread 1 (Thread 46912539207168 (LWP 6847)):
0 0x00000036638c0e1b in __read_nocancel () from /lib64/libc.so.6
1 0x000000366386a617 in _IO_new_file_underflow () from
/lib64/libc.so.6
2 0x000000366386930e in _IO_file_xsgetn_internal () from
/lib64/libc.so.6
3 0x000000366385f692 in fread () from /lib64/libc.so.6
4 0x00002aaaacfb5d32 in file_read (s=0x605d60, buf=0x66c7f8,
elmsize=1, cnt=1) at stream.c:457
5 0x00002aaaacfb53f1 in stream_read (s=0x605d60, buf=0x66c7f8,
elmsize=1, cnt=1) at stream.c:169
6 0x00002aaaabc31f17 in readClient (c=0x2aaaabe966c0) at
monet_client.c:428
7 0x00002aaaabc32752 in serveClient (stk=0, lt=0x63cf48,
res=0x7fff4480baa0) at monet_client.c:622
8 0x00002aaaabbfd551 in interpret (stk=0, lt=0x63cf48,
res=0x7fff4480baa0) at monet_interpreter.c:808
9 0x00002aaaabc2d171 in handleRequest (t=0x2aaaacee3ba0, q=0x12469f28,
res=0x7fff4480baa0) at monet_queue.c:342
10 0x00002aaaabc2d66e in doRequest (t=0x2aaaacee3ba0, preference=0x0)
at monet_queue.c:368
11 0x00002aaaabc7f98d in monetInterpreter (status=0x7fff4480bba4) at
monet_process.c:45
12 0x0000000000401f94 in main (argc=4, av=0x7fff4480bcc8) at
Mserver.c:242
0x00002aaab876c549 9886 fake_item =
is_fake_project(batlist[ii]);
## Comment 10891
Date: 2009-02-06 14:18:18 +0100
From: @peterboncz
Om een of andere reden is de "attr_qn" bat van 02FF778C-312B-8F82-26E3-DD737721420F.xml
namelijk verdwenen op het moment supreme.
Op zichzelf krijg ik het probleem niet gereproduceerd, het heeft te maken met concurrent activiteiten. Weet jij wat er verder gaande was tijdens deze test? Zijn er simultane queries? Zo niet, moet het haast wel de logger zijn.
Het verdachte is dat
- de BAT is niet geldaden maar zowel refs=1 als lrefs=1 (!!)
- de BBP status van de verdwenen BAT is 4 (BBPTMP. Dit duidt op een swapout of een commit
- maar de bewuste BAT is een VIEW, de swapout code exit direct als de BAT een view is.
(het is een view want een bat uit de working set is nu altijd een view op een master)
dus het moet haast wel de commit code zijn die de bat heeft weggegooid.
ik vermoed dus dat de logger code een bat vernietigd die al lang weg is en wiens plaats is ingenomen door een nieuwe bat.
kan ook de BBPdecref bug veroorzaken!
## Comment 10892
Date: 2009-02-06 14:18:36 +0100
From: @peterboncz
Om een of andere reden is de "attr_qn" bat van 02FF778C-312B-8F82-26E3-DD737721420F.xml
namelijk verdwenen op het moment supreme.
Op zichzelf krijg ik het probleem niet gereproduceerd, het heeft te maken met concurrent activiteiten. Weet jij wat er verder gaande was tijdens deze test? Zijn er simultane queries? Zo niet, moet het haast wel de logger zijn.
Het verdachte is dat
- de BAT is niet geldaden maar zowel refs=1 als lrefs=1 (!!)
- de BBP status van de verdwenen BAT is 4 (BBPTMP. Dit duidt op een swapout of een commit
- maar de bewuste BAT is een VIEW, de swapout code exit direct als de BAT een view is.
(het is een view want een bat uit de working set is nu altijd een view op een master)
dus het moet haast wel de commit code zijn die de bat heeft weggegooid.
ik vermoed dus dat de logger code een bat vernietigd die al lang weg is en wiens plaats is ingenomen door een nieuwe bat.
kan ook de BBPdecref bug veroorzaken!
## Comment 10893
Date: 2009-02-12 17:05:08 +0100
From: Jens Oehlschlägel <<jens_oehl>>
I find replicable segfaults when repeating a certain sequence of queries after < 20000 queries in total under Win32 (June2008, Nov2009SP2, Feb2009Alpha). Will report how to replicate as soon as I find time. Do you want me to add to this bug or keep seperate?
## Comment 10894
Date: 2009-02-12 19:48:48 +0100
From: @drstmane
Jens,
While the symptoms are very similar, the fact the Floris uses MonetDB(4)/XQuery while you use MonetDB(5)/SQL suggests that the actual problems need not be the same --- the awareness of a potential relation is very much appreciated and might help to further investigate the problem, though.
I'd hence propose to file a new bug report, but add comments to both reports referring to each other to document the *potential* relationship.
Thank you very much!
Stefan
## Comment 10895
Date: 2009-04-07 15:40:54 +0200
From: @peterboncz
According to NFI, since my checkin the problem has not re-appeared.
This race condition is too complicated to recreate in the testweb.
## Comment 10896
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2567316 at http://sourceforge.net/support/tracker.php?aid=2567316
| Segfault after long period of use | https://api.github.com/repos/MonetDB/MonetDB/issues/1936/comments | 0 | 2020-11-30T10:08:53Z | 2024-06-27T11:34:27Z | https://github.com/MonetDB/MonetDB/issues/1936 | 753,340,131 | 1,936 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-03 11:14:42 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @mlkersten
Version: -- development
Last updated: 2009-02-04 12:23:40 +0100
## Comment 10882
Date: 2009-02-03 23:14:42 +0100
From: Jens Oehlschlägel <<jens_oehl>>
sql>select x, case when x<=12 then 1 else 0 end as log from (select 10 as x union select 11 as x union select 12 as x un
ion select 13 as x) sub;
+----+----+
| x |log |
+====+====+
| 10 | 0 |
| 11 | 0 |
| 12 | 1 |
| 13 | 1 |
+----+----+
MonetDB June2008 Win32
select x
, case when x<=12 then 1 else 0 end as log
from (
select 10 as x
union
select 11 as x
union
select 12 as x
union
select 13 as x
) sub
;
## Comment 10883
Date: 2009-02-04 00:10:12 +0100
From: @mlkersten
A rather stupid typo in the special case of comparison of cst and bat.
A test file has been added 'caselessthen.sql'
## Comment 10884
Date: 2009-02-04 00:19:52 +0100
From: @drstmane
test added in the Feb2009 release branch as sql/src/test/BugTracker-2009/Tests/LE_vs_GE_in_CASE.SF-2562264.*
With all three releases, Jun2008, Nov2008 & Feb2009,
"<=" seems to be incorrectly interpreted as ">=", as reported,
while "<", "=", ">=", ">" seem to work fine with all releases.
## Comment 10885
Date: 2009-02-04 00:23:40 +0100
From: @drstmane
[ SF is not ACID ]
Indeed fixed in the Feb2009 branch by
2009/02/03 - mlkersten: MonetDB5/src/modules/kernel/batcalc.mx,1.173.2.1
A rather stupid typo in some of the special cases for constant comparison.
## Comment 10886
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2562264 at http://sourceforge.net/support/tracker.php?aid=2562264
| <= (LE) in CASE interpreted as >= (GE) | https://api.github.com/repos/MonetDB/MonetDB/issues/1935/comments | 0 | 2020-11-30T10:08:49Z | 2024-06-27T11:34:26Z | https://github.com/MonetDB/MonetDB/issues/1935 | 753,340,091 | 1,935 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-03 02:19:24 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:49:45 +0100
## Comment 10876
Date: 2009-02-03 14:19:24 +0100
From: Jens Oehlschlägel <<jens_oehl>>
COPY INTO imports single characters as NULL under June2008 and Nov2008 SP2 under Win32. Replication via attached files.
Cheers
Jens
## Comment 10877
Date: 2009-02-03 14:30:43 +0100
From: @drstmane
same problem in Feb2009 release branch;
works fine without the "NULL as ''"
## Comment 10878
Date: 2009-02-03 14:35:14 +0100
From: @drstmane
... sorry --- wrong check --- in the Feb2009 release branch, it works fine, also WITH the "NULL AS ''" -- hence, the bug exists only in the Jun2008 & Nov2008 (SP2) releases, but no longer in the Feb2009 release branch ...
... with the Jun2008 & Nov2008 (SP2) releases, it works fine without the "NULL AS ''" ...
## Comment 10879
Date: 2009-02-03 23:57:53 +0100
From: @drstmane
test added in the Feb20099 release branch as sql/src/test/BugTracker-2009/Tests/COPY_INTO_char_NULL.SF-2560780.*
## Comment 10880
Date: 2009-02-09 15:49:45 +0100
From: @romulogoncalves
The test is green on both branches so I declare this bug fixed and closed...
## Comment 10881
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2560780 at http://sourceforge.net/support/tracker.php?aid=2560780
| COPY INTO imports single characters as NULL | https://api.github.com/repos/MonetDB/MonetDB/issues/1934/comments | 0 | 2020-11-30T10:08:44Z | 2024-06-27T11:34:25Z | https://github.com/MonetDB/MonetDB/issues/1934 | 753,340,023 | 1,934 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-02 02:34:56 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-03-26 03:48:13 +0100
## Comment 10873
Date: 2009-02-02 14:34:56 +0100
From: @grobian
% merovingian
unable to open '/program-i86pc/var/log/merovingian.log': No such file or directory
Merovingian should just try to create the file, instead of failing when the file is not available.
## Comment 10874
Date: 2009-02-02 14:35:18 +0100
From: @grobian
fixed in CVS
## Comment 10875
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2556973 at http://sourceforge.net/support/tracker.php?aid=2556973
| Merovingian: error when logfile does not exist | https://api.github.com/repos/MonetDB/MonetDB/issues/1933/comments | 0 | 2020-11-30T10:08:41Z | 2024-06-27T11:34:24Z | https://github.com/MonetDB/MonetDB/issues/1933 | 753,339,988 | 1,933 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-02 12:07:12 +0100
From: @romulogoncalves
To: @mlkersten
Version: -- development
Last updated: 2009-02-03 11:48:44 +0100
## Comment 10868
Date: 2009-02-02 12:07:12 +0100
From: @romulogoncalves
The following query crashes the M5-SQL
select * from history;
The crash:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe1433950 (LWP 23049)]
0x00007fffe2520ce2 in rel_projections (sql=0x7fffe200b2a8, rel=0x7fffe1ea7c68, tname=0x0, settname=1, intern=1) at /ufs/goncalve/MonetDB/stable/sql/src/server/rel_select.mx:386
386 for (en = rel->exps->h; en; en = en->next) {
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.3-2.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb)
The tname argument in the function is NULL.
## Comment 10869
Date: 2009-02-02 12:09:44 +0100
From: @romulogoncalves
Sorry
The problem is not with tname, it is the rel->exps :)
386 for (en = rel->exps->h; en; en = en->next) {
(gdb) p rel->exps
$2 = (list *) 0xdbdbdbdbdbdbdbdb
(gdb)
## Comment 10870
Date: 2009-02-02 12:12:30 +0100
From: @romulogoncalves
Test added at:
sql/src/tests/BugTracker-2009/Tests/select_from_history.SF-2556566.sql
## Comment 10871
Date: 2009-02-03 11:48:42 +0100
From: @romulogoncalves
Bug is fixed with the following check in:
[Monetdb-sql-checkins] sql/src/server rel_select.mx, Feb2009, 1.113.2.1, 1.113.2.2
Log Message:
be more protective when looking at sql stack variables
(ie don't intepret simple values as tables)
Solves bug select * from history)
## Comment 10872
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2556566 at http://sourceforge.net/support/tracker.php?aid=2556566
| select from history | https://api.github.com/repos/MonetDB/MonetDB/issues/1932/comments | 0 | 2020-11-30T10:08:36Z | 2024-06-27T11:34:23Z | https://github.com/MonetDB/MonetDB/issues/1932 | 753,339,927 | 1,932 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-02-01 12:00:40 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-02-15 09:23:33 +0100
## Comment 10863
Date: 2009-02-01 00:00:40 +0100
From: Jan Rittinger <<jan.rittinger>>
A large set of queries ran better with the last stable branch. Most of these queries (*mod* and *opt*) are evaluated with mps (which seems to be completely broken now).
The remaining queries (and their cause for failing) I noticed are:
compiler/usageH (debug flag)
modules/pftijah/sigs (more signatures that need to be approved?!?)
tests/BugTracker/predicate_selects_too_few_nodes.SF-1636588 (fix stable output: dbl imprecision)
tests/BugTracker/swizzle-bug.SF-1760811 (fix stable output: nid changes)
tests/StandOff/video/artists distinct-values (fix stable output: implementation-defined order)
runtime/xrpc/admin/backup_restore_noxrpc (fix stable output: element printing)
tests/BugTracker/entities_dtd.SF-1642665 (shredder.mx 1.146 -> 1.147)
tests/W3C_use_cases/XQ/SGML/shred_doc (shredder.mx 1.146 -> 1.147)
In my eyes only the last two tests are real problems that should be fixed before the release.
## Comment 10864
Date: 2009-02-02 11:24:12 +0100
From: Jan Rittinger <<jan.rittinger>>
I fixed the stable output for tests/StandOff/video/artists and tests/BugTracker/predicate_selects_too_few_nodes.SF-1636588. For the latter probably one or more system specific files (e.g. Darwin 32.32) may be needed -- but tomorrows testing will show which systems then still differ.
## Comment 10865
Date: 2009-02-09 11:06:08 +0100
From: Jan Rittinger <<jan.rittinger>>
Shredder is fixed now.
The remaining tests are:
compiler/usageH (debug flag)
modules/pftijah/sigs (more signatures that need to be approved?!?)
tests/BugTracker/swizzle-bug.SF-1760811 (fix stable output: nid changes)
runtime/xrpc/admin/backup_restore_noxrpc (fix stable output: element
## Comment 10866
Date: 2009-02-15 21:23:33 +0100
From: @drstmane
output of
compiler/usageH
modules/pftijah/sigs
tests/BugTracker/swizzle-bug.SF-1760811
has been approved;
for
runtime/xrpc/admin/backup_restore_noxrpc
see
https://sourceforge.net/tracker/index.php?func=detail&aid=2406824&group_id=56967&atid=482468
## Comment 10867
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2553868 at http://sourceforge.net/support/tracker.php?aid=2553868
| PF: queries that ran better on the previous stable branch | https://api.github.com/repos/MonetDB/MonetDB/issues/1931/comments | 0 | 2020-11-30T10:08:32Z | 2024-06-27T11:34:22Z | https://github.com/MonetDB/MonetDB/issues/1931 | 753,339,878 | 1,931 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-31 10:53:18 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-02-14 05:59:12 +0100
## Comment 10860
Date: 2009-01-31 10:53:18 +0100
From: @drstmane
The remote tests fail on Windows:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d.1-Windows5.2/src_modules_mal/remote01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_modules_mal/remote01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d.1-Windows5.2/src_modules_mal/remote02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_modules_mal/remote02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d.1-Windows5.2/src_modules_mal/remote03.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_modules_mal/remote03.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d.1-Windows5.2/src_modules_mal/remote04.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_modules_mal/remote04.out.00.html
Assigning to Fabian, as he was according to CVS the last one who modified these tests and/or their stable output.
## Comment 10861
Date: 2009-02-14 17:59:12 +0100
From: @drstmane
The problem appears to be fixed --- at least the remote tests no also appear to work on Windows.
Closing.
## Comment 10862
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2552013 at http://sourceforge.net/support/tracker.php?aid=2552013
| M5: remote tests fail on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1930/comments | 0 | 2020-11-30T10:08:29Z | 2024-06-27T11:34:21Z | https://github.com/MonetDB/MonetDB/issues/1930 | 753,339,847 | 1,930 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-31 10:39:27 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-01-31 08:01:21 +0100
## Comment 10857
Date: 2009-01-31 10:39:27 +0100
From: @drstmane
There is no expected/stable test output for the test common01.mal in MonetDB5/src/optimizer/Tests/.
There is not much use in running a test without expected/stable test output with nightly testing, as the test will (obviously) always fail.
I'd suggest to either add the missing output or remove/disable this test (at least) in the Feb2009 release branch.
## Comment 10858
Date: 2009-01-31 20:01:21 +0100
From: @mlkersten
files checked in that were laying aroung
## Comment 10859
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2551984 at http://sourceforge.net/support/tracker.php?aid=2551984
| M5: test common01 fails (due to missing stable output) | https://api.github.com/repos/MonetDB/MonetDB/issues/1929/comments | 0 | 2020-11-30T10:08:26Z | 2024-06-27T11:34:20Z | https://github.com/MonetDB/MonetDB/issues/1929 | 753,339,811 | 1,929 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-30 11:03:54 +0100
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-03-28 10:11:12 +0100
## Comment 10854
Date: 2009-01-30 23:03:54 +0100
From: Jan Rittinger <<jan.rittinger>>
In MonetDB4/src/modules/contrib/malalgebra.mx:256 BATnlthetajoin is seeded with a size estimate of BUN_MAX.
In MonetDB/src/gdk/gdk_relop.mx:1614 BATnlthetajoin calls BATnew with size 'estimate+128'.
In MonetDB/src/gdk/gdk_bat.mx:289 BATnew triggers an assertion because of the check: BUN_MAX+128 < BUN_MAX.
A MonetDB expert should decide where to fix this 'miscalculation'.
## Comment 10855
Date: 2009-03-28 10:11:11 +0100
From: @sjoerdmullender
I added overflow checks in both BATnlthetajoin and BATnew.
## Comment 10856
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2550429 at http://sourceforge.net/support/tracker.php?aid=2550429
| nlthetajoin asks for 128 bytes too much memory | https://api.github.com/repos/MonetDB/MonetDB/issues/1928/comments | 0 | 2020-11-30T10:08:23Z | 2024-06-27T11:34:19Z | https://github.com/MonetDB/MonetDB/issues/1928 | 753,339,767 | 1,928 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-30 05:43:07 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 12:15:04 +0200
## Comment 10848
Date: 2009-01-30 17:43:07 +0100
From: Jan Rittinger <<jan.rittinger>>
In Pathfinder generated code the PROC htordered_unique_thetajoin() calls the COMMAND leftthetajoin (located in malalgebra.mx:248). The size estimate there is 'MIN(BATcount(l), BATcount(r)' which is completely different to all other thetajoin estimates in the MonetDB code. (In my case |l|=4728, |r|=12000, and the result contains 7586008 rows. Thus using leftthetajoin costs > 60 seconds whereas using nlthetajoin---based on the same underlying primitive---takes only 2 seconds.)
BTW all other thetajoins ask for an explicit estimate. As this is however a stable branch I'm not sure whether the signature should be changed. Please let me know if there is no easy and meaningful solution. Then I will just replace the leftthetajoin call in the pathfinder code base.
## Comment 10849
Date: 2009-01-30 21:36:32 +0100
From: @sjoerdmullender
I think it would be easy enough to add an extra implementation for leftthetajoin with an additional parameter for the estimate. At this stage of the release cycle that's still an option.
## Comment 10850
Date: 2009-01-30 21:58:22 +0100
From: Jan Rittinger <<jan.rittinger>>
I replaced the leftthetajoin in the pathfinder generated code. A 'performance' fix is thus not necessary for me anymore.
## Comment 10851
Date: 2009-04-07 12:15:04 +0200
From: @peterboncz
added a parameter as desired (better late than never?)
## Comment 10852
Date: 2009-04-07 13:04:23 +0200
From: @drstmane
completed administration
## Comment 10853
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2549582 at http://sourceforge.net/support/tracker.php?aid=2549582
| M4: leftthetajoin estimate way to small | https://api.github.com/repos/MonetDB/MonetDB/issues/1927/comments | 0 | 2020-11-30T10:08:20Z | 2024-06-27T11:34:18Z | https://github.com/MonetDB/MonetDB/issues/1927 | 753,339,724 | 1,927 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 10:31:45 +0100
From: @drstmane
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-01-29 10:49:42 +0100
## Comment 10842
Date: 2009-01-29 22:31:45 +0100
From: @drstmane
.../pathfinder/modules/pftijah/pftijah.mx(5333): error 593: variable "Ai" was set but never used
BATiter Ai, Di;
^
.../pathfinder/modules/pftijah/pftijah.mx(5333): error 593: variable "Di" was set but never used
BATiter Ai, Di;
^
## Comment 10843
Date: 2009-01-29 23:00:50 +0100
From: @drstmane
"closed" with neither a "Resolution" nor a comment??
## Comment 10844
Date: 2009-01-29 23:19:31 +0100
From: @drstmane
Fixed by Henning:
2009/01/29 - hrode: pathfinder/modules/pftijah/pftijah.mx,1.197.2.1
fix bug [ 2546716 ] PFtijah fails to compile with Intel's icc
Thanks!
## Comment 10845
Date: 2009-01-29 23:42:18 +0100
From: Henning Rode <<hrode>>
sorry, i am still not so confident with using the bug tracking system.
i thought i have to close it, when i think i fixed the bug.
since this bug seemed rather simple i was quite sure that my fix would do the job.
what would be a "resolution"?
-henning
## Comment 10846
Date: 2009-01-30 00:05:02 +0100
From: @drstmane
Usually, any change to a bug report should come with a (short) comment to explain the rational of the change.
E.g., when a bug report is "closed" without any comment, no one will/can know, why i was closed: by accicent? fixed? rejected? irrelevant? duplicate?
The 'Resolution' is just like the 'Status' one of the meta-fields of a bug report (see above) with a list of values to chose from ranging from "None", over, e.g, "Accepted", "Duplicate", Rejected", "Invalid", etc. to "Works for me", "Won't fix" and "fixed".
Standard procedure is, e.g., that a developer (the assignee) takes care of the bug, fixed it, and marks it fixed. If he/she is confident that the bug is indeed fixed also for the submitter (e.g., tested it and if applicable added a repective test to the CVS repository), [s]he can close it instantly; otherwise [s]he leaves it open (as a reminder) and either wait for nightly testing to verify the fix or for confirmation by the submitter (both clearly indicated in the comment). The next day when nightly testing has verified the fix the assignee closes the bug report; or once the submitted has verified the fix, [s]he closes it.
## Comment 10847
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2546716 at http://sourceforge.net/support/tracker.php?aid=2546716
| PFtijah fails to compile with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1926/comments | 0 | 2020-11-30T10:08:17Z | 2024-06-27T11:34:17Z | https://github.com/MonetDB/MonetDB/issues/1926 | 753,339,688 | 1,926 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 09:11:54 +0100
From: @swingbit
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-02-11 08:48:48 +0100
## Comment 10837
Date: 2009-01-29 21:11:54 +0100
From: @swingbit
On Feb2009 branch:
CREATE TABLE a(n integer, x varchar(255));
INSERT INTO a VALUES(1, 'ONE');
INSERT INTO a VALUES(2, 'TWO');
INSERT INTO a VALUES(2, 'TWO');
INSERT INTO a VALUES(3, 'THREE');
CREATE VIEW va AS
SELECT DISTINCT n, x
FROM a;
CREATE TABLE b(n integer, x varchar(255));
INSERT INTO b VALUES(1, 'ONE');
INSERT INTO b VALUES(2, 'TWO');
INSERT INTO b VALUES(3, 'THREE');
CREATE VIEW v AS
SELECT va.x, b.x
FROM va, b
WHERE va.n = b.n;
sql>select * from va;
+---+-------+
| n | x |
+===+=======+
| 1 | ONE |
| 2 | TWO |
| 3 | THREE |
+---+-------+
That's ok!
sql>select * from v;
+-------+-------+
| x | x |
+=======+=======+
| ONE | ONE |
| TWO | TWO |
| TWO | TWO |
| THREE | THREE |
+-------+-------+
That's NOT ok!
The DISTINCT on a has been ignored!
## Comment 10838
Date: 2009-01-29 23:24:16 +0100
From: @swingbit
Apparently t is not only about the Join.
DISTINCT works correctly only if it is on a top-level query.
INSERT INTO x
SELECT DISTINCT a from y;
does not work correctly either.
## Comment 10839
Date: 2009-01-30 10:36:10 +0100
From: @swingbit
To be more precise on my previous comment: I'm not sure in which cases the problem occurs.
I will give here an example where it does occur ('insert into t select distinct ...' , where table t has a serial type):
DROP TABLE a;
DROP TABLE b;
DROP TABLE c;
CREATE TABLE a(n integer, x varchar(255));
INSERT INTO a VALUES(1, 'ONE');
INSERT INTO a VALUES(2, 'TWO');
INSERT INTO a VALUES(2, 'TWO');
INSERT INTO a VALUES(3, 'THREE');
CREATE TABLE b(n integer, x varchar(255));
INSERT INTO b SELECT DISTINCT n,x from a;
CREATE TABLE c(n serial, x varchar(255));
INSERT INTO c (x) SELECT DISTINCT x from a;
SELECT * FROM a; -- the initial duplicates are here
SELECT * FROM b; -- here they get removed, correct
SELECT * FROM c; -- here they don't get removed, wrong
## Comment 10840
Date: 2009-02-11 20:48:47 +0100
From: @njnes
Fixed (tests added to BugTracker-2009). In insert (and update) we now detect when need to add an extra project around a distinct-project.
## Comment 10841
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2546483 at http://sourceforge.net/support/tracker.php?aid=2546483
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| DISTINCT does'n work when below a join | https://api.github.com/repos/MonetDB/MonetDB/issues/1925/comments | 0 | 2020-11-30T10:08:13Z | 2024-06-27T11:34:16Z | https://github.com/MonetDB/MonetDB/issues/1925 | 753,339,653 | 1,925 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 06:50:17 +0100
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-02-16 10:01:57 +0100
## Comment 10832
Date: 2009-01-29 18:50:17 +0100
From: @swingbit
On Feb2009 branch:
CREATE TABLE a(n varchar(255));
INSERT INTO a VALUES('ONE');
INSERT INTO a VALUES('TWO');
INSERT INTO a VALUES('THREE');
CREATE VIEW b AS
SELECT row_number() over () AS id, n
FROM a;
sql>select * from b;
+----+-------+
| id | n |
+====+=======+
| 1 | ONE |
| 2 | TWO |
| 3 | THREE |
+----+-------+
sql>SELECT * FROM b
WHERE n = 'TWO';
+----+-----+
| id | n |
+====+=====+
| 1 | TWO |
+----+-----+
I would expect
+====+=====+
| 2 | TWO |
+----+-----+
## Comment 10833
Date: 2009-02-11 20:52:52 +0100
From: @njnes
fixed (we now detect projects which cannot be push up or down). Test added to bugTracker-2009
## Comment 10834
Date: 2009-02-16 10:55:36 +0100
From: @drstmane
Niels,
which is the test that belong to this one?
The is none with number "2546109" ...
Stefan
## Comment 10835
Date: 2009-02-16 22:01:56 +0100
From: @njnes
added test row_number_bug.SF-2546109
## Comment 10836
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2546109 at http://sourceforge.net/support/tracker.php?aid=2546109
| row_number() columns should be materialized after selection | https://api.github.com/repos/MonetDB/MonetDB/issues/1924/comments | 0 | 2020-11-30T10:08:09Z | 2024-06-27T11:34:15Z | https://github.com/MonetDB/MonetDB/issues/1924 | 753,339,620 | 1,924 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 04:25:26 +0100
From: Loredana Afanasiev <<lafanasi>>
To: Jan Flokstra <<jflokstra>>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-04-28 16:39:00 +0200
## Comment 10824
Date: 2009-01-29 16:25:26 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi,
problem with ft-index-info(). See the action sequence below.
mcl = mclient -lx
[lafanasi@zookst4 xq]$ more tijah-index-extend.xq
let $opt := <TijahOptions ft-index="polietiekedata" stemmer="snowball-dutch"/>
let $col := ("KVR-DE")
return
tijah:extend-ft-index($col, $opt)
[lafanasi@zookst4 xq]$ mcl tijah-index-extend.xq
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,KVR-DE" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>,
<ftindex collections="*" tokenizer="flex" stemmer="nostemming">DFLT_FT_INDEX</ftindex>
[lafanasi@zookst4 xq]$ stopMserver
[lafanasi@zookst4 xq]$ startMserver
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>,
<ftindex collections="*" tokenizer="flex" stemmer="nostemming">DFLT_FT_INDEX</ftindex>
cheers,
l.
OS: Linux, 2.6.24.3-50.fc8
Mem: 19GB
Compiler: gcc 4.1.2
Parser tools: ?
autoconf (GNU Autoconf) 2.61
automake (GNU automake) 1.10
ltmain.sh (GNU libtool) 1.5.24
## Comment 10825
Date: 2009-01-30 10:01:56 +0100
From: Jan Flokstra <<jflokstra>>
It looks as if the ft-index vs. pf-collection dependency administration was not properly committed in the case where an extend specifies collections which are not defined yet. It should be fixed in the Stable branch now. It will take some time before it appears in the HEAD which I think Loredana is using. When Loredane confirms it also fixes her problem I will close the case.
JanF.
## Comment 10826
Date: 2009-02-15 21:26:18 +0100
From: @drstmane
Loredana, JanF,
could you please
(1) check whether the problem is indeed fixed
(2) provide/add a test
(3) close the bug report once the fix is confirmed and a test has been added.
Thanks!
Stefan
## Comment 10827
Date: 2009-02-24 01:03:29 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi JanF,
I've tested this problem again on the HEAD and on the stable PS2 versions. Both versions behave erroneously along the lines I've described before. The stable version gives more errors. Below (Part I), I've copied parts of my terminal scripting for the stable version. Further, I've tried to delete and create the ft-index again and it didn't work (Part II).
Part I: working with the stable Nov2008-SP2 version
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,HAN-B,KVR-B" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>
[lafanasi@zookst4 xq]$ more tijah-index-extend.xq
let $opt := <TijahOptions ft-index="polietiekedata" stemmer="snowball-dutch"/>
let $col := ("KVR-DE")
return
tijah:extend-ft-index($col, $opt)
[lafanasi@zookst4 xq]$ mcl tijah-index-extend.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata" stemmer="snowball-dutch"/>
ERROR = !ERROR: interpret_params: insert(param 3): invalid BAT.
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,HAN-B,KVR-B,KVR-DE" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>
[lafanasi@zookst4 xq]$ mcl q2.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"/>
ERROR = !fatal error: Algebra implementation for function `pf:string-value' is missing.
[lafanasi@zookst4 xq]$ more q2.xq
let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"/>
let $c := collection("KVR-DE")
let $qid := tijah:query-id($c, "//ANTWOORD[about(.,Polizei)]", $opt)
for $res in tijah:nodes($qid)
return <pair>{( string($res), tijah:score($qid, $res))}</pair>
[lafanasi@zookst4 xq]$ sudo su ilps_bg
ilps_bg@zookst4:/scratch/PolitiekeData/KVR-DE/xq$ stopMserver
ilps_bg@zookst4:/scratch/PolitiekeData/KVR-DE/xq$ startMserver
exit
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,HAN-B,KVR-B" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>
Part II: the index is corrupt
[lafanasi@zookst4 xq]$ mcl delete-tijah-index.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata"/>
ERROR = !ERROR: interpret_params: persists(param 1): invalid BAT.
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
[lafanasi@zookst4 xq]$ mcl delete-tijah-index.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata"/>
ERROR = !ERROR: tj_get_ft_index, ft-index "polietiekedata" does not exist
[lafanasi@zookst4 xq]$ mcl tijah-index.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata" stemmer="snowball-dutch"/>
ERROR = !ERROR: interpret_params: access(param 1): invalid BAT.
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,HAN-B,KVR-B" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>
[lafanasi@zookst4 xq]$ mcl delete-tijah-index.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata"/>
ERROR = !ERROR: interpret_params: persists(param 1): invalid BAT.
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
[lafanasi@zookst4 xq]$ mcl tijah-index.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions ft-index="polietiekedata" stemmer="snowball-dutch"/>
ERROR = !ERROR: interpret_params: insert(param 3): invalid BAT.
[lafanasi@zookst4 xq]$ mcl -s "tijah:ft-index-info()"
<ftindex collections="MotiesTweedeKamer,HAN,KVR,HAN-B,KVR-B" tokenizer="flex" stemmer="snowball-dutch">polietiekedata</ftindex>
[lafanasi@zookst4 xq]$ more q3.xq
let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"
returnNumber="5" />
let $coll := collection("HAN")
(:let $query := tijah:tokenize("knettergek") :)
let $query := "knettergek"
(: We need the "else" because empty queries are not allowed :)
let $nexi :=
if ($query)
then concat("//spreker[about(.,",$query,")]")
else "//spreker[about(.,bogusqueryblablabl)]"
let $qid := tijah:query-id($coll, $nexi, $opt)
let $nodes := tijah:nodes($qid)
for $res in $nodes
return
<pair>{(string($res/@naam), tijah:score($qid, $res))}</pair>
[lafanasi@zookst4 xq]$ mcl q3.xq
MAPI = monetdb@localhost:50100
QUERY = let $opt := <TijahOptions milfile="/scratch/PolitiekeData/HAN/xq/q3.mil" ft-index="polietiekedata" ir-model="NLLR"
ERROR = !ERROR: CMDtijah_query: tijahParse: parse error.
!ERROR: CMDtijah_query: operation failed.
I hope this helps to fix the problem(s).
cheers,
l.
## Comment 10828
Date: 2009-02-24 02:09:39 +0100
From: @drstmane
Just for the records:
The Nov2008-SP2 version (second and last "service pack" of "bug fix release" of the ("old") Nov2008 branch) was released on 2009/01/23.
Henning checked in Jan's bug fix on 2009/01/30 to the ("new") Feb2009 branch (assuming cvs log message "checked in a bug-fix for Jan F." refers to the fix Jan mentioned below ...).
Sjoerd propagated Henning's checkin (i.e., Jan's fix) on the same day (2009/01/30) from the Feb2009 branch to the CVS HEAD.
In other words:
- Nov2008-SP2 does not contain Jan's fix.
- Feb2009 branch and CVS HEAD contain Jan's fix since 2009/01/30.
- In case Loredana's HEAD is more recent than 2009/01/30, Jan's fix might not be sufficient, yet.
## Comment 10829
Date: 2009-02-24 09:51:28 +0100
From: Jan Flokstra <<jflokstra>>
Loredana,
As Stefan mentioned the fix was indeed not in the Nov2008 Stable. I just checked and it is in the current HEAD so this is no problem. Your problem was reproduced on several architectures and the fix fixed the original problem. Your 'new' problems have other causes.
- PART I: the problem here is that it looks as if the Nov2008 doesn not support pf:string-value(elem) which causes the line "return <pair>{( string($res), tijah:score($qid, $res))}</pair>" to fail. I looked in the current HEAD and there is an algebra version defined for this function
- PART II: this is an older problem and has our attention. I talked about this with Henning also in connection with earlier problems you had. When there have been a lot of problems/crahses there is a chance of a half baked index. The solution for us is to ignore all errors when deleting the index bats and modifying the pftijah adminstration bats. This will be implemented soon. Current best practice is to throw away the monet files ($PREFIX/var/MonetDB4/dbfarm/<DATABASENAME>)
## Comment 10830
Date: 2009-08-14 14:10:52 +0200
From: @drstmane
tagged subject
## Comment 10831
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2545711 at http://sourceforge.net/support/tracker.php?aid=2545711
## Comment 15697
Date: 2011-03-28 17:37:07 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15775
Date: 2011-04-28 16:39:00 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PFtijah: buggy ft-index-info | https://api.github.com/repos/MonetDB/MonetDB/issues/1923/comments | 0 | 2020-11-30T10:08:06Z | 2024-06-28T13:26:53Z | https://github.com/MonetDB/MonetDB/issues/1923 | 753,339,581 | 1,923 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 03:00:41 +0100
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-01-29 03:17:11 +0100
## Comment 10821
Date: 2009-01-29 15:00:41 +0100
From: @swingbit
cc1: warnings being treated as errors
/export/scratch0/roberto/MonetDB/src/pathfinder/modules/pftijah/tjc/tjc_phys_optimize.c: In function 'printTJanode':
/export/scratch0/roberto/MonetDB/src/pathfinder/modules/pftijah/tjc/tjc_phys_optimize.c:212: warning: 'parID' may be used uninitialized in this function
## Comment 10822
Date: 2009-01-29 15:17:11 +0100
From: @sjoerdmullender
Added initialization.
## Comment 10823
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2545523 at http://sourceforge.net/support/tracker.php?aid=2545523
| Feb2009 branch compilation error | https://api.github.com/repos/MonetDB/MonetDB/issues/1922/comments | 0 | 2020-11-30T10:08:03Z | 2024-06-27T11:34:13Z | https://github.com/MonetDB/MonetDB/issues/1922 | 753,339,537 | 1,922 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-29 02:20:51 +0100
From: @swingbit
To: @mlkersten
Version: -- development
Last updated: 2009-01-29 10:34:01 +0100
## Comment 10814
Date: 2009-01-29 14:20:51 +0100
From: @swingbit
cc1: warnings being treated as errors
/export/scratch0/roberto/MonetDB/src/MonetDB5/src/scheduler/run_octopus.mx: In function 'OCTOPUSrun':
/export/scratch0/roberto/MonetDB/src/MonetDB5/src/scheduler/run_octopus.mx:222: warning: 'i' may be used uninitialized in this function
## Comment 10815
Date: 2009-01-29 14:54:51 +0100
From: @sjoerdmullender
Martin, please inititialize variable i.
## Comment 10816
Date: 2009-01-29 15:35:21 +0100
From: @drstmane
With icc, I also get
.../MonetDB5/src/scheduler/run_octopus.mx(136): error 592: variable "b2" is used before its value is set
(void) b2;
^
## Comment 10817
Date: 2009-01-29 17:46:04 +0100
From: @sjoerdmullender
By the way, I seriously doubt that the code (in OCTOPUSexec) does what you think it does. The only time i gets assigned a value is if it is nrsites initially. After the loop i is never changed, so if you get back to the redo label, i will still be != nrsites, so i will not be assigned a different value.
Also, why do you use goto?
## Comment 10818
Date: 2009-01-29 18:22:08 +0100
From: @mlkersten
Gents, be patient.
The octopus run code is indeed in flux, due to the recent
major overhaul of the remote.mx. I will be fixed to compile,
but semantically incomplete! That has to wait for my next
hacker time slot ;)
## Comment 10819
Date: 2009-01-29 22:34:01 +0100
From: @drstmane
Compilation fixed in development trunk by Martin.
Fix back-ported to Feb2009 release branch by me.
## Comment 10820
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2545448 at http://sourceforge.net/support/tracker.php?aid=2545448
| Feb2009 branch compilation error | https://api.github.com/repos/MonetDB/MonetDB/issues/1921/comments | 0 | 2020-11-30T10:08:00Z | 2024-06-27T11:34:12Z | https://github.com/MonetDB/MonetDB/issues/1921 | 753,339,498 | 1,921 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-27 12:42:23 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-02-02 12:38:58 +0100
## Comment 10804
Date: 2009-01-27 12:42:23 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Querying two tables combined with UNION ALL in view accumulates memory leak and crashes the server.
-- 1. fresh installation of MonetDB Win32 Nov 2008 SP2
-- 2. start server with db demo
-- 3. log in as sys
CREATE USER "voc" WITH PASSWORD 'voc' NAME 'VOC Explorer' SCHEMA "sys";
CREATE SCHEMA "voc" AUTHORIZATION "voc";
ALTER USER "voc" SET SCHEMA "voc";
-- 4. log off
-- 5. log in as voc
CREATE TABLE databasetest1 (
"id" INTEGER
, "ubyte1" SMALLINT
, "ubyte2" SMALLINT
, "ubyte3" SMALLINT
, "ubyte4" SMALLINT
, "ubyte5" SMALLINT
, "ubyte6" SMALLINT
, "ubyte7" SMALLINT
, "ubyte8" SMALLINT
, "ubyte9" SMALLINT
, "ubyte10" SMALLINT
, "ubyte11" SMALLINT
, "ubyte12" SMALLINT
, "ubyte13" SMALLINT
, "ubyte14" SMALLINT
, "ubyte15" SMALLINT
, "smallint1" SMALLINT
, "smallint2" SMALLINT
, "smallint3" SMALLINT
, "smallint4" SMALLINT
, "smallint5" SMALLINT
, "smallint6" SMALLINT
, "smallint7" SMALLINT
, "smallint8" SMALLINT
, "smallint9" SMALLINT
, "smallint10" SMALLINT
, "smallint11" SMALLINT
, "smallint12" SMALLINT
, "smallint13" SMALLINT
, "smallint14" SMALLINT
, "smallint15" SMALLINT
, "float1" DOUBLE
, "float2" DOUBLE
, "float3" DOUBLE
, "float4" DOUBLE
, "float5" DOUBLE
, "float6" DOUBLE
, "float7" DOUBLE
, "float8" DOUBLE
, "float9" DOUBLE
, "float10" DOUBLE
, "float11" DOUBLE
, "float12" DOUBLE
, "float13" DOUBLE
, "float14" DOUBLE
, "float15" DOUBLE
, "float16" DOUBLE
, "float17" DOUBLE
, "float18" DOUBLE
, "float19" DOUBLE
, "float20" DOUBLE
)
;
START TRANSACTION;
COPY 1000000 OFFSET 2 RECORDS INTO "voc"."databasetest1" FROM 'D:/tmp/databasetest.csv' USING DELIMITERS ',';
COMMIT;
CREATE TABLE databasetest2 (
"id" INTEGER
, "ubyte1" SMALLINT
, "ubyte2" SMALLINT
, "ubyte3" SMALLINT
, "ubyte4" SMALLINT
, "ubyte5" SMALLINT
, "ubyte6" SMALLINT
, "ubyte7" SMALLINT
, "ubyte8" SMALLINT
, "ubyte9" SMALLINT
, "ubyte10" SMALLINT
, "ubyte11" SMALLINT
, "ubyte12" SMALLINT
, "ubyte13" SMALLINT
, "ubyte14" SMALLINT
, "ubyte15" SMALLINT
, "smallint1" SMALLINT
, "smallint2" SMALLINT
, "smallint3" SMALLINT
, "smallint4" SMALLINT
, "smallint5" SMALLINT
, "smallint6" SMALLINT
, "smallint7" SMALLINT
, "smallint8" SMALLINT
, "smallint9" SMALLINT
, "smallint10" SMALLINT
, "smallint11" SMALLINT
, "smallint12" SMALLINT
, "smallint13" SMALLINT
, "smallint14" SMALLINT
, "smallint15" SMALLINT
, "float1" DOUBLE
, "float2" DOUBLE
, "float3" DOUBLE
, "float4" DOUBLE
, "float5" DOUBLE
, "float6" DOUBLE
, "float7" DOUBLE
, "float8" DOUBLE
, "float9" DOUBLE
, "float10" DOUBLE
, "float11" DOUBLE
, "float12" DOUBLE
, "float13" DOUBLE
, "float14" DOUBLE
, "float15" DOUBLE
, "float16" DOUBLE
, "float17" DOUBLE
, "float18" DOUBLE
, "float19" DOUBLE
, "float20" DOUBLE
)
;
START TRANSACTION;
COPY 1000000 OFFSET 1000002 RECORDS INTO "voc"."databasetest2" FROM 'D:/tmp/databasetest.csv' USING DELIMITERS ',';
COMMIT;
CREATE VIEW databasetest AS
SELECT * FROM databasetest1
UNION ALL
SELECT * FROM databasetest2
;
-- 6. log off
-- 7. shut down server
-- 8. restart server
-- 9. log in as voc
-- 10. each execution of the following SQL consumes additional memory, repeat it until server crash
SELECT sum(float1) AS currencyfloat, sum(float2) AS unitfloat FROM databasetest;
-- The csv file can be created with the following R-script
this is an R comment and you find R at CRAN.r-project.org
filename <- "D:/tmp/databasetest.csv"
create 2Mio rows in 2000 batches of 1000, total of 347MB csv file, takes ~4 minutes
system.time({
b <- 2000L number of batches
n <- 1000L batch size
csvfile <- file(filename, open="w")
for (i in 1:b){
x <- data.frame(
id = ((i-1L)*n+1L):(i*n) 4-byte integer record identifier
, ubyte1 = sample(0:35, n, TRUE, prob=NULL) unsigned byte columns (1 byte)
, ubyte2 = sample(0:1, n, TRUE, prob=NULL)
, ubyte3 = sample(0:3, n, TRUE, prob=NULL)
, ubyte4 = sample(0:9, n, TRUE, prob=NULL)
, ubyte5 = sample(0:24, n, TRUE, prob=NULL)
, ubyte6 = sample(0:99, n, TRUE, prob=NULL)
, ubyte7 = sample(-127:127, n, TRUE, prob=NULL)
, ubyte8 = sample(0:1, n, TRUE, prob=c(0.75, 0.25))
, ubyte9 = sample(0:1, n, TRUE, prob=c(0.9,0.1))
, ubyte10 = sample(0:1, n, TRUE, prob=c(0.96,0.04))
, ubyte11 = sample(0:1, n, TRUE, prob=c(0.99,0.01))
, ubyte12 = sample(0:1, n, TRUE, prob=c(0.996,0.004))
, ubyte13 = sample(0:1, n, TRUE, prob=c(0.999,0.001))
, ubyte14 = sample(0:1, n, TRUE, prob=c(0.9996,0.0004))
, ubyte15 = sample(0:1, n, TRUE, prob=c(0.9999,0.0001))
, smallint1 = sample(1:4000, n, TRUE, prob=NULL) smallint columns (2 bytes)
, smallint2 = sample(1:2, n, TRUE, prob=NULL)
, smallint3 = sample(1:4, n, TRUE, prob=NULL)
, smallint4 = sample(1:10, n, TRUE, prob=NULL)
, smallint5 = sample(1:25, n, TRUE, prob=NULL)
, smallint6 = sample(1:100, n, TRUE, prob=NULL)
, smallint7 = sample(1:256, n, TRUE, prob=NULL)
, smallint8 = sample(1:1000, n, TRUE, prob=NULL)
, smallint9 = sample(1:32000, n, TRUE, prob=NULL)
, smallint10 = sample(0:1, n, TRUE, prob=c(0.75, 0.25))
, smallint11 = sample(0:1, n, TRUE, prob=c(0.9,0.1))
, smallint12 = sample(0:1, n, TRUE, prob=c(0.96,0.04))
, smallint13 = sample(0:1, n, TRUE, prob=c(0.99,0.01))
, smallint14 = sample(0:1, n, TRUE, prob=c(0.996,0.004))
, smallint15 = sample(0:1, n, TRUE, prob=c(0.999,0.001))
, float1 = round(runif(n, 0, 100), 1) float columns (4 bytes)
, float2 = round(runif(n, 0, 100), 1)
, float3 = round(runif(n, 0, 100), 1)
, float4 = round(runif(n, 0, 100), 1)
, float5 = round(runif(n, 0, 100), 1)
, float6 = round(runif(n, 0, 100), 1)
, float7 = round(runif(n, 0, 100), 1)
, float8 = round(runif(n, 0, 100), 1)
, float9 = round(runif(n, 0, 100), 1)
, float10 = round(runif(n, 0, 100), 1)
, float11 = round(runif(n, 0, 100), 1)
, float12 = round(runif(n, 0, 100), 1)
, float13 = round(runif(n, 0, 100), 1)
, float14 = round(runif(n, 0, 100), 1)
, float15 = round(runif(n, 0, 100), 1)
, float16 = round(runif(n, 0, 100), 1)
, float17 = round(runif(n, 0, 100), 1)
, float18 = round(runif(n, 0, 100), 1)
, float19 = round(runif(n, 0, 100), 1)
, float20 = round(runif(n, 0, 100), 1)
)
write.table(x, file=csvfile, row.names=FALSE, col.names=(i==1L), append=i!=1L, dec=".", sep=",")
}
close(csvfile)
})
End R script
-- Machine configuration
Lenovo Thinkcentre with 3 GB RAM under Windows XP Professional SP2
RAM consumption of m5server.exe during load ~300MB according to task manager
Free RAM 2.1 GB
Size of dbfarm finally 1.9 GB
DiskFreeSpace 1.8 TB
[System Summary]
Item Value
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name GEMUN-38396-10-
System Manufacturer LENOVO
System Model 6073AA7
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 11 GenuineIntel ~2992 Mhz
Processor x86 Family 6 Model 15 Stepping 11 GenuineIntel ~2992 Mhz
BIOS Version/Date LENOVO 2RKT41AUS, 3/20/2008
SMBIOS Version 2.5
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale Germany
Hardware Abstraction Layer Version = "5.1.2600.3023 (xpsp_sp2_qfe.061030-0020)"
Time Zone W. Europe Standard Time
Total Physical Memory 3,072.00 MB
Available Physical Memory 1.70 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 5.79 GB
Page File D:\pagefile.sys
## Comment 10805
Date: 2009-01-27 15:47:10 +0100
From: @drstmane
Jens,
no being familiar with R myself, could you please
(a) give a short hint (commandline call) how to use the R script to create the data file and
(b) attach the R-script to this bug report to avoid unwanted line breaks introduced by SF formatting/rendering?
Thanks in advance!
Stefan
## Comment 10806
Date: 2009-01-27 16:57:21 +0100
From: @drstmane
On a 64-bit Linux system (the only one I can quickly check it on) I can reproduce the leaking.
After the first query (i.e., once the data is initially loaded) mserver5 is 628 MB, then it grwos by about 38 MB per query.
(with 8 GB RAM, crashes are "out of reach" ...)
While this is obviously not desirable and needs to be analyzed and fixed,
the question is, why this seems to (quickly?) cause a server crash on a 3 GB (Win32) machines?
Jens,
did you see any error messages on the server console windows, or does it just "disappear"?
## Comment 10807
Date: 2009-01-27 17:48:22 +0100
From: @drstmane
Using the new Algebra back-end of MonetDB/SQL via `mclient -G ...` respectively `\G` on the mclient console --- the new Algebra back-end will be default in the next feature release of MonetDB/SQL (most probably called "Feb2009") --- (only) for the leaking query makes mserver5 grow only to 533 MB (instead of 628 MB) with the first call, but subsequent calls fail with
sql>SELECT sum(float1) AS currencyfloat, sum(float2) AS unitfloat FROM databasetest;
!relational query without result
0 tuples
## Comment 10808
Date: 2009-01-28 09:27:50 +0100
From: Jens Oehlschlägel <<jens_oehl>>
If I remember correctly I saw both: silent crashes or frozen server console with a memory allocation bug shown.
May be it helps to know that this bug was not in the release distributed as MonetDB5-SQL-Installer-i386-20080624.msi
## Comment 10809
Date: 2009-01-31 00:56:35 +0100
From: @drstmane
It took some time, "forensics" and combined forces (THANKS go to Niels, Martin & Sjoerd!), but finally, we located and fixed the reported leak in revision 1.312.2.1 (new Feb2009 release branch) of sql/src/backends/monet5/sql_gencode.mx by making sure that we use the BAT returned by bat.append since
~~~~~~~
2008/08/09 - mlkersten: MonetDB5/src/modules/kernel/bat5.mx,1.37
The access modes of the kernel BAT update operations were not aligned.
This caused the SQL front-end to inject setWriteMode calls before each
append, and possibly trimming it again with an optimizer.
The BAT insert, append, delete, and replace functions now always return
the first argument, which my be a copy with the proper access properties.
This elicits the flow. The side effectness can be checked with the
isUpdateFunction.
The majority of files involve the now visible temporary in the output.
~~~~~~~
I'll add the respective test during the weekend ...
## Comment 10810
Date: 2009-02-02 00:38:58 +0100
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/union_leak.SF-2540169.*
## Comment 10811
Date: 2009-08-13 19:12:21 +0200
From: @drstmane
re-opened as the test fails since checkin on 2009/09/20 and/or 2009/07/21;
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/union_leak.SF-2540169.out.00.html
## Comment 10812
Date: 2009-08-14 09:46:07 +0200
From: @drstmane
appears to be fixed, again, by
===================================================================
2009/08/13 - sjoerd: MonetDB/src/gdk/gdk_heap.mx,1.125.2.1
Experimental checkin.
Memory maps come in two flavors: normal and private
(a.k.a. copy-on-write). The former are more efficient when saving
since less data needs to be copied, but they can be a pain when
dealing with pre-existing heaps, since then a backup needs to be made
before starting to update the data.
When switching from malloced to memory mapped allocation in a heap, we
now see whether the heap file already existed, and if so, we use a
private memory map (as before), but if the file did not exist, we now
use a normal memory map. We don't need to make a backup first,
because there is no pre-existing data to backup, so this should work.
The result of this change is that loading data into fresh bats should
be quicker. Since the new heaps are now "normal" memory maps, less
copying takes place when the data is saved. A quick test suggests
that this is indeed the case: the loading part of the 15M Periscope
test took longer than the timeout (1800 seconds) allowed without this
change, but was finished in about 1000 seconds with the change.
Tonight's testing will hopefully show whether this idea does indeed
work.
===================================================================
## Comment 10813
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2540169 at http://sourceforge.net/support/tracker.php?aid=2540169
| Memory leak and crash with UNION ALL | https://api.github.com/repos/MonetDB/MonetDB/issues/1920/comments | 0 | 2020-11-30T10:07:56Z | 2024-06-27T11:34:11Z | https://github.com/MonetDB/MonetDB/issues/1920 | 753,339,461 | 1,920 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-27 12:11:04 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-01-27 01:15:18 +0100
## Comment 10799
Date: 2009-01-27 00:11:04 +0100
From: @drstmane
With a freshly stated ("virgin") M5/SQL server (`mserver5 --dbinit='include sql;'), the following simple `mclient -lsql` session results in an assertion or segfault in GDKfree, most probably due to an attemt to free already freed or not allocated memory:
$ mclient -lsql
sql>debug select * from tables;
mdb> mdb.start();
mdb>n
mdb> user.s0_1();
mdb>[Crtl-D]
gdb reveals the following:
$ gdb --args mserver5 --dbinit='include sql;'
[...]
(gdb) r
[...]
MonetDB server v5.9.0, based on kernel v1.27.0
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008- MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see .../etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.27.0 loaded
>
mserver5: .../MonetDB/src/gdk/gdk_utils.mx:1110: GDKfree: Assertion `size != 0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe1ca7950 (LWP 25596)]
0x0000003675232f05 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.3-2.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb) bt
0 0x0000003675232f05 in raise () from /lib64/libc.so.6
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
3 0x00007ffff7400b54 in GDKfree (blk=0x12ff8f8) at .../MonetDB/src/gdk/gdk_utils.mx:1110
4 0x00007ffff7d34281 in runScenarioBody (c=0x6049f8) at .../MonetDB5/src/mal/mal_scenario.mx:613
5 0x00007ffff7d34557 in runScenario (c=0x6049f8) at .../MonetDB5/src/mal/mal_scenario.mx:660
6 0x00007ffff7cf844b in MSserveClient (dummy=0x6049f8) at .../MonetDB5/src/mal/mal_session.mx:461
7 0x0000003675e073da in start_thread () from /lib64/libpthread.so.0
8 0x00000036752e62bd in clone () from /lib64/libc.so.6
(gdb) up
1 0x0000003675234a73 in abort () from /lib64/libc.so.6
(gdb)
2 0x000000367522bef9 in __assert_fail () from /lib64/libc.so.6
(gdb)
3 0x00007ffff7400b54 in GDKfree (blk=0x12ff8f8) at .../MonetDB/src/gdk/gdk_utils.mx:1110
1110 assert(size != 0);
(gdb) li
1105 size = GDK_MEM_BLKSIZE(s);
1106
1107 /* check against duplicate free */
1108 assert((size & 2) == 0);
1109
1110 assert(size != 0);
1111
1112 if (size < 0) {
1113 size_t maxsize = (size_t) s[-2];
1114
(gdb) printf "%x\n",*s
dbdbdbdb
(gdb)
## Comment 10800
Date: 2009-01-27 01:15:18 +0100
From: @mlkersten
fixed by resetting the variable after GDKfree
## Comment 10801
Date: 2009-01-27 09:24:37 +0100
From: @mlkersten
fixed by resetting the variable after GDKfree
## Comment 10802
Date: 2009-02-16 12:15:18 +0100
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/segfault_when_quitting_debugger.SF-2538837.*
appears to work fine
## Comment 10803
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2538837 at http://sourceforge.net/support/tracker.php?aid=2538837
| mserver5 segfault (double free) when quitting debugger | https://api.github.com/repos/MonetDB/MonetDB/issues/1919/comments | 0 | 2020-11-30T10:07:53Z | 2024-06-27T11:34:10Z | https://github.com/MonetDB/MonetDB/issues/1919 | 753,339,418 | 1,919 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-26 07:24:56 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2009-01-26 08:16:17 +0100
## Comment 10796
Date: 2009-01-26 07:24:56 +0100
From: @mlkersten
select a.b;
leads to a server crash on the development head.
Test added in BugTracker-2009
## Comment 10797
Date: 2009-01-26 20:16:17 +0100
From: @njnes
fixed (missing condition)
## Comment 10798
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2536893 at http://sourceforge.net/support/tracker.php?aid=2536893
| SQL: Server crash on incomplete statement | https://api.github.com/repos/MonetDB/MonetDB/issues/1918/comments | 0 | 2020-11-30T10:07:49Z | 2024-06-27T11:34:09Z | https://github.com/MonetDB/MonetDB/issues/1918 | 753,339,369 | 1,918 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-22 02:32:28 +0100
From: Andreas Meinl <<andreasmeinl>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 12:05:13 +0200
## Comment 10786
Date: 2009-01-22 14:32:28 +0100
From: Andreas Meinl <<andreasmeinl>>
During the import of some xml files, the server crashed with the error message "MonetDB>!FATAL: GDKmallocmax: failed for 252933552 bytes".
After that the server crashes repeatedly for example executing the very simple xquery "count(collection("test"))".
The output of mclient, where I execute the xquery, is everytime more or less the same:
xquery>count(collection("test"))
more><>
GDKmalloc(210756272) fail => BBPtrim(enter) usage[mem=639556716,vm=1117388800]
GDKmalloc(210756272) fail => BBPtrim(ready) usage[mem=413709780,vm=1096351744]
GDKmallocmax: recovery ok. Continuing..
15831
MAPI = monetdb@localhost:50000
QUERY = count(collection("test"))
ERROR = !ERROR: BBPdecref: 1000000163_rid_level does not have pointer fixes.
xquery>count(collection("test"))
more><>
15831
MAPI = monetdb@localhost:50000
QUERY = count(collection("test"))
ERROR = !ERROR: BBPdecref: 1000000163_rid_level does not have pointer fixes.
!ERROR: BBPdecref: 1000000163_attr_qn does not have pointer fixes.
!ERROR: BBPdecref: 1000000163_attr_prop does not have pointer fixes.
xquery>count(collection("test"))
more><>
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = count(collection("test"))
ERROR = Connection terminated
The environment I use is Windows XP Professional x86 and MonetDB/XQuery server and client, 32 bit, windows installer, version 20081216.
## Comment 10787
Date: 2009-01-22 14:49:01 +0100
From: @yzchang
Hello Andreas,
Would you please provide us some more information:
- How large is your memory? How many memory is still available when you start monet?
- How many files are you trying to add? How large is each document, or how large are they in total?
- Is it possible to provide us your complete set of documents, in a compressed form, as attachment or via a URL?
- How do you exactly add the documents? which command do you use?
- How often does the crash happen (always or sometimes)?
Regards,
Jennie
## Comment 10788
Date: 2009-01-22 15:00:16 +0100
From: @drstmane
Hm, this look as if your Mserver fails to allocate an extra ~200 MB, probably running out of available address spcae on your 32-bit system (or at least not finding a consecutive free 200 MB address range due to excessive memory/address space fragmentation on Windows).
The first question is, why these 200 MB are required, or differently:
How many documents did you (sucessfully) load into how many collections, and how large are the individual documents and the collections you're using?
How much physical and virtual memory does your machine have?
Stefan
## Comment 10789
Date: 2009-01-22 15:25:04 +0100
From: Andreas Meinl <<andreasmeinl>>
- My notebook is equipped with two GB of RAM.
After I have started the server, 1164 MB are still available (and the system cache has 620 MB) - referring to Windows Task-Manager.
- I wanted to import 492086 files (into one collection), but the server crashed after having imported 15831 files (with the message I mentioned before). The size of one file is about 20 to 70 KB.
- Sorry, but these documents represent confidential business documents; I'm not allowed to distribute them.
- For the import I just use a quick & simple Java loop of the form:
statement = connection.createStatement();
statement.executeUpdate("pf:add-doc(\"C:\\[...]\\test.xml\", \"test.xml\", \"test\")");
statement.close();
- The crash seems to happen always in the same way, that is after executing the xquery three times. After the crash there are 1205 MB available and 794 MB are assigned to the system cache.
## Comment 10790
Date: 2009-01-24 18:37:57 +0100
From: Andreas Meinl <<andreasmeinl>>
I wanted to rescue my imported files (or to be more precisely, the time I had to spent for the import) and to backup the database to restore it on another instance of MonetDB/XQuery on another computer.
But unfortunately the backup also failed with the error message I've attached as a PNG file.
Is there any way to repair my database and not having to import all files again?
File Added: monetdb.png
## Comment 10791
Date: 2009-01-26 08:18:23 +0100
From: Andreas Meinl <<andreasmeinl>>
Eventually I did the same import again on a newly installed instance of MonetDB/XQuery on another computer and got the same crash of MonetDB again. The only difference is the first time I had been able to import 15831 xml files and the second time only 12161 files before the crash happened.
Is there any server log I could attach?
## Comment 10792
Date: 2009-02-12 18:04:14 +0100
From: @peterboncz
Hi Jens,
I am sorry that your bug report remained unattended for some time.
There are two problems here:
(1) MXQ is not able apparently to import your dataset (crash)
(2) after crashing in the add-doc, it leaves the collection in a corrupted state
We will be releasing in a few weeks, and the good news about (2) is that we fixed some bugs regarding error handing in a shred.
About (1), the problem is that 32-bits windows only has 2GB of address space, and given your collection size (0.5GB) but taking into account overhead and memory fragmentation, the crash is most likely related to too little address space. This is very hard to fix, because MonetDB is using virtual memory for managing databases.
For large collections like these, we advise using 64-bits windows, and use the 64-bits builds we provide.
You might try to workaround by splitting up your import job in batches, e.g. adding 100 documents at a time to the collection.
## Comment 10793
Date: 2009-04-07 12:05:13 +0200
From: @peterboncz
(1) coherent system state after failed add-doc() is tested already
(2) scalability on 32-bits (windows) is unfixable
closing
## Comment 10794
Date: 2009-04-07 13:03:04 +0200
From: @drstmane
Andreas,
In the MonetDB kernel, memory management in particular for 32-bit Windows has recently been improved and made more robust (as far as possible) against address space fragmentation; hence, you might want to try, again, with the latest Feb2009-SP1 release ...
... otherwise, you'd need to resort to a 64-bit system & 64-bit MonetDB ...
Stefan
## Comment 10795
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2528563 at http://sourceforge.net/support/tracker.php?aid=2528563
| Server crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/1917/comments | 0 | 2020-11-30T10:07:46Z | 2024-06-28T13:27:56Z | https://github.com/MonetDB/MonetDB/issues/1917 | 753,339,338 | 1,917 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-20 12:50:59 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @njnes
Version: -- development
Last updated: 2009-02-11 08:53:49 +0100
## Comment 10781
Date: 2009-01-20 12:50:59 +0100
From: Jens Oehlschlägel <<jens_oehl>>
SQL: IS NULL is accepted silently but handled wrong in searched CASE expression, see the following example
CREATE TABLE "sometable" (
"somecol" INTEGER
)
;
INSERT INTO "sometable" VALUES ( 0);
INSERT INTO "sometable" VALUES ( 1);
INSERT INTO sometable VALUES (NULL);
COMMIT;
SELECT somecol
, CASE
WHEN somecol < 6 THEN 'small'
WHEN somecol = 6 THEN 'six'
WHEN somecol > 6 AND somecol < 9 THEN '78'
WHEN somecol IS NULL THEN 'NULL FOUND'
ELSE 'big'
END AS "NewColumnName"
FROM sometable
;
-- In WHEN "somecol IS NULL" is not evaluted to TRUE and the THEN expression returned, instead NULL is returned
-- workaround with COALESCE does NOT help
## Comment 10782
Date: 2009-01-20 12:56:49 +0100
From: Jens Oehlschlägel <<jens_oehl>>
Works for me if the IS NULL is the first WHEN statement, sorry
## Comment 10783
Date: 2009-02-04 01:18:36 +0100
From: @drstmane
added test in Feb2009 release branch as sql/src/test/BugTracker-2009/Tests/IS_NULL_in_CASE.*
behaves as reported in all three releases, Jun2008, Nov2008, Feb2009.
## Comment 10784
Date: 2009-02-11 20:53:49 +0100
From: @njnes
The case condition column needs its null's removed.
## Comment 10785
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2523442 at http://sourceforge.net/support/tracker.php?aid=2523442
| IS NULL handled wrong in searched CASE | https://api.github.com/repos/MonetDB/MonetDB/issues/1916/comments | 0 | 2020-11-30T10:07:43Z | 2024-06-27T11:34:07Z | https://github.com/MonetDB/MonetDB/issues/1916 | 753,339,302 | 1,916 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-20 11:32:03 +0100
From: Jens Oehlschlägel <<jens_oehl>>
To: @mlkersten
Version: -- development
Last updated: 2009-02-12 11:14:11 +0100
## Comment 10778
Date: 2009-01-20 11:32:03 +0100
From: Jens Oehlschlägel <<jens_oehl>>
The documentation says in
"F261-02 Searched CASE N"
that searched CASE is not supported, but it appears to be supported since I could run statements like
-- searched case expression
SELECT numcol
, CASE
WHEN numcol < 6 THEN 'small'
WHEN numcol = 6 THEN 'six'
WHEN numcol > 6 AND numcol < 9 THEN '78'
WHEN numcol IS NULL THEN 'NULL'
ELSE 'big'
END AS "NewColumnName"
FROM sometable
;
and not only
-- simple case expression
SELECT numcol
, CASE numcol
WHEN 6 THEN 'six'
ELSE 'non-six'
END AS "NewColumnName"
FROM sometable
;
## Comment 10779
Date: 2009-02-12 23:14:11 +0100
From: @mlkersten
fixed in documentation
## Comment 10780
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2523265 at http://sourceforge.net/support/tracker.php?aid=2523265
| SQL searched CASE supported but not documented | https://api.github.com/repos/MonetDB/MonetDB/issues/1915/comments | 0 | 2020-11-30T10:07:40Z | 2024-06-27T11:34:06Z | https://github.com/MonetDB/MonetDB/issues/1915 | 753,339,267 | 1,915 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-19 12:39:50 +0100
From: Loredana Afanasiev <<lafanasi>>
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-03-17 03:34:55 +0100
## Comment 10767
Date: 2009-01-19 00:39:50 +0100
From: Loredana Afanasiev <<lafanasi>>
Dear developers,
When running the simple keyword query below ~100 times, the MServer's memory footprint grows to 100% and the server crashes with no error messages. My collection has ~1GB.
let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"/>
let $c := collection("HAN")
let $qid := tijah:query-id($c, "//spreker[about(.,%KEYWORD%)]", $opt)
for $res in tijah:nodes($qid)
return <pair>{( string($res/@naam), tijah:score($qid, $res))}</pair>
thank you!
l.
OS: Linux, 2.6.24.3-50.fc8
Mem: 19GB
Compiler: gcc 4.1.2
Parser tools: ?
autoconf (GNU Autoconf) 2.61
automake (GNU automake) 1.10
ltmain.sh (GNU libtool) 1.5.24
## Comment 10768
Date: 2009-01-19 16:55:28 +0100
From: Henning Rode <<hrode>>
i just checked it together with jan f..
result: we have indeed a memory leak here.
5K per simple pathfinder query.
1.8M per simple pf/tijah query.
26K per pf/tijah query with new query processor.
the 1.8M are of course quite bad, but since it only occurs in the old version of the query processor, we won't fix that anymore.
the 26K in the new version are now on my todo list. i still have to find out, whether it occurs in the C code of the query processor, or whether we simply do not give enough hints to MonetDB to free MIL vars.
loredana, you can maybe use as an additional option to your queries:
<TijahOptions newversion="true"/>
## Comment 10769
Date: 2009-02-03 11:40:40 +0100
From: Jan Flokstra <<jflokstra>>
I had a more systematic look at the problem here. I think I solved the problem by:
1) removing 2 unnecessary BBPfixes()
2) assigning the nexi_result variable in the generated pftijah script to nil;
This was a very strange error. The bat is removed from the buffer pool when the script is run throught "mclient -lmil" and we thought our generated script was memory leak free. But when we called it from "C" by "monet_exec(script_str);" the bat was not cleared and we have to assign nil manually. To prevent further problems in the futrue we plan to put the entire scripts between { }. This way the MIL interpreter should kill all used variables also when called from "C"
We reduced memory consumption for 'big' queries' (eg. 50.000 results) from 850K to 16K which is about avarage for Pathfinder,
I wait for conformation from Loredana before I close the bug.
JanF.
## Comment 10770
Date: 2009-02-15 21:31:07 +0100
From: @drstmane
Loredana, JanF,
could you please
(1) check whether the problem is indeed fixed
(2) provide/add a test
(3) close the bug report once the fix is confirmed and a test has been
added.
Thanks!
Stefan
## Comment 10771
Date: 2009-02-23 16:36:51 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi all,
the problem is not fixed yet, but Henning seems to have found the problem..
"i was just reformulating your query to this one:
let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR" />
(:let $query := tijah:tokenize("knettergek") :)
let $query := "knettergek"
(: We need the "else" because empty queries are not allowed :)
let $nexi := concat("//spreker[about(.,",$query,")]")
for $res in tijah:queryall($nexi, $opt)
return
<pair>{string($res/@naam)}</pair>
and suddenly there was no memory leak anymore.. "
So it seems that the problem sits in the implementation of query-id() function.
Henning the floor is yours :)
l.
## Comment 10772
Date: 2009-02-25 15:52:39 +0100
From: Henning Rode <<hrode>>
well, the memory leak seems still not fixed :-( but i fixed now a number of related problems, when starting a query from a context node set. at least, we get correct output again, and i don't see crashes anymore, not even after running your query a hundred times on my desktop machine.
## Comment 10773
Date: 2009-02-25 15:53:00 +0100
From: Henning Rode <<hrode>>
well, the memory leak seems still not fixed :-( but i fixed now a number of related problems, when starting a query from a context node set. at least, we get correct output again, and i don't see crashes anymore, not even after running your query a hundred times on my desktop machine.
## Comment 10774
Date: 2009-03-03 15:46:02 +0100
From: Henning Rode <<hrode>>
Jans most recent check-in today seems to finally solve the issue. Now also tested on Loredana's data-set and query.
(However, I better wait for Loredanas OK before closing this bug.)
## Comment 10775
Date: 2009-03-04 17:04:56 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi Henning, hi JanF,
I can't reproduce the reported behavior on the new head. Hurray!
Thank you for the fix!
l.
P.S. btw, there is this small issue with an error message I get when I query a non-existent collection.
mmcl = mclient
bash-3.2$ more q2.xq
let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"/>
let $c := collection("HAN-BE")
let $qid := tijah:query-id($c, "//spreker[about(.,fortis)]", $opt)
for $res in tijah:nodes($qid)
return <pair>{( string($res/@naam), tijah:score($qid, $res))}</pair>
bash-3.2$ mmcl q2.xq
MAPI = monetdb@localhost:50000
QUERY = let $opt := <TijahOptions ft-index="polietiekedata" ir-model="NLLR"/>
ERROR = !ERROR: CMDpf2tijah_node: GDKmalloc() failed.
!ERROR: CMDpf2tijah_node: operation failed.
bash-3.2$ mmcl -s "pf:collections()"
<collection updatable="false" size="125 MiB" numDocs="541">HAN-B</collection>,
So, it there is no collection called "HAN-BE", but I wouldn't guess this from the error message.
## Comment 10776
Date: 2009-03-05 09:39:52 +0100
From: Henning Rode <<hrode>>
I will close this bug since the memory leak issue (at least the main one) is solved. The new problem you report in your last comment will be dealt with by another bugreport.
## Comment 10777
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2518276 at http://sourceforge.net/support/tracker.php?aid=2518276
| memory leak | https://api.github.com/repos/MonetDB/MonetDB/issues/1914/comments | 0 | 2020-11-30T10:07:37Z | 2024-06-28T13:27:55Z | https://github.com/MonetDB/MonetDB/issues/1914 | 753,339,241 | 1,914 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-16 05:23:30 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-11 08:58:53 +0100
## Comment 10763
Date: 2009-01-16 17:23:30 +0100
From: @romulogoncalves
The example crashed the mserver5:
create function f1() RETURNS TABLE (id int, age int) BEGIN return table(select 1, 2); end;
select f1();
drop function f1;
The right message should be:
sql>select f1();
!SELECT: subquery returns a table
0 tuples
sql>
## Comment 10764
Date: 2009-01-27 10:49:25 +0100
From: @romulogoncalves
The test to cover this bug was added:
sql/src/test/BugTracker-2009/Tests/subquery_returns_table_crash.SF-2513620.sql
## Comment 10765
Date: 2009-02-11 20:58:53 +0100
From: @njnes
Properly detect unexpected table results in the selection
## Comment 10766
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2513620 at http://sourceforge.net/support/tracker.php?aid=2513620
| subquery returns a table crash | https://api.github.com/repos/MonetDB/MonetDB/issues/1913/comments | 0 | 2020-11-30T10:07:33Z | 2024-06-27T11:34:04Z | https://github.com/MonetDB/MonetDB/issues/1913 | 753,339,199 | 1,913 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-11 05:41:29 +0100
From: @mlkersten
To: @mlkersten
Version: -- development
Last updated: 2009-02-12 02:50:52 +0100
## Comment 10759
Date: 2009-01-11 17:41:29 +0100
From: @mlkersten
create function in_p_l(p int, l int)
returns boolean
begin
return true;
end;
create table points(p int);
create table lines(l int);
explain select * from points x,lines y
where in_p_l(x.p,y.l);
!Predicate BINOP 95: time to implement some more
test file added to BugTracker-2009
## Comment 10760
Date: 2009-01-26 20:18:44 +0100
From: @njnes
The sql side seems fixed. But there seems to be an optimizer issue.
## Comment 10761
Date: 2009-02-12 14:50:52 +0100
From: @mlkersten
The remap optimizer performed a type check, which showed an error,
but did not abandon the optimization step.
## Comment 10762
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2499537 at http://sourceforge.net/support/tracker.php?aid=2499537
| SQL: time to implement BINOP | https://api.github.com/repos/MonetDB/MonetDB/issues/1912/comments | 0 | 2020-11-30T10:07:30Z | 2024-06-27T11:34:03Z | https://github.com/MonetDB/MonetDB/issues/1912 | 753,339,167 | 1,912 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-01-08 06:27:58 +0100
From: dtstutz <<dtstutz>>
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2009-02-16 10:55:11 +0100
## Comment 10752
Date: 2009-01-08 18:27:58 +0100
From: dtstutz <<dtstutz>>
sql>create table a (b int, c int);
sql>insert into a (b, c) values (10, 100);
Rows affected 1
sql>insert into a (b, c) values (10, 200);
Rows affected 1
sql>select b, count(distinct c) from a group by b having count(distinct c) > 1;
!TypeException:user.s1_2[37]:'group.derive' undefined in: (_50:any, grp50:any) := group.derive(ext49:any, _49:bat[:oid,:oid], _46:bat[:oid,:int])
!TypeException:user.s1_2[38]:'bat.mirror' undefined in: _53:any := bat.mirror(_50:any)
!TypeException:user.s1_2[39]:'algebra.semijoin' undefined in: _54:any := algebra.semijoin(_46:bat[:oid,:int], _53:any)
!TypeException:user.s1_2[40]:'aggr.count_no_nil' undefined in: _55:bat[:any,:int] := aggr.count_no_nil(_54:any, _49:bat[:oid,:oid], _43:bat[:oid,:oid])
!TypeException:user.s1_2[37]:'ext49' may not be used before being initialized
+----+---------------+
| b |count_no_nil_c |
+====+===============+
| 10 | 100 |
+----+---------------+
I'm running Ubuntu 8.04.1.
I'm sorry I can't easily find the details for the precompiled binary I'm using; hopefully this bug report can still be useful. If not, my apologies for cluttering the bug list.
## Comment 10753
Date: 2009-01-26 20:23:54 +0100
From: @njnes
works in the soon to be released devel version. Please try using the mclient -G switch.
## Comment 10754
Date: 2009-02-09 15:02:37 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug can be closed.
## Comment 10755
Date: 2009-02-09 15:09:36 +0100
From: @romulogoncalves
Niels,
There is no test to cover this bug, should it be created?
If yes let me know and I will do it...
## Comment 10756
Date: 2009-02-16 11:54:30 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
... Romulo volunteered ...
## Comment 10757
Date: 2009-02-16 22:55:11 +0100
From: @drstmane
[while Romulo is baking pizza]
added test in sql/src/test/BugTracker-2009/Tests/TypeException_having_count_distinct.SF-2494227.*
appears to work fine.
## Comment 10758
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2494227 at http://sourceforge.net/support/tracker.php?aid=2494227
| TypeException from having count(distinct colname) | https://api.github.com/repos/MonetDB/MonetDB/issues/1911/comments | 0 | 2020-11-30T10:07:27Z | 2024-06-28T13:27:54Z | https://github.com/MonetDB/MonetDB/issues/1911 | 753,339,135 | 1,911 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.