Query interfering with next query in same transaction, after SP4 #3377
Last updated: 2013-10-22 14:42:10 +0200
Date: 2013-09-30 11:44:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36
I have data and scripts ready to reproduce this, but the data is quite big (14g uncompressed), so I cannot attach it here. I also tried on smaller data samples, but then I cannot reproduce it.
Please write me an email to get a link to data and scripts, I rather not make it public.
The bug seems to pop up only in Feb2013_SP4 (it works fine on another installation that is up to changeset 49170:c0bf1946fc19), and this is its summary:
Two queries, Q1 and Q2, are executed within the same transaction. They both (although slightly differently) join a small table against a large table, and take the "top" 2 tuples. They both have no side-effects, they are simple SELECT queries.
Compiled from Mercurial repo, changeset 49170:c0bf1946fc19
MonetDB 5 server v11.15.16 (64-bit, 64-bit oids)
Date: 2013-10-02 16:56:38 +0200
fixed by making sure a view only shares a hash with its parent if this
The text was updated successfully, but these errors were encountered: