I have some problems for deleting reccords on a table of 20000000 rows.
I've created a table 'test' and inserted in one operation 20000000 rows on this table.
There is only one column in this table : 'id' and values are 'BIGINT' from 1 to 20000000.
When I delete first row of the table 'test' it work, but when I try to delete the last reccord, it seem the delete did not work:
I try to insert data on other table with 'order by desc' and it's the opposite (can't delete value 1).
Reproducible: Always
Steps to Reproduce:
1.create table test(id bigint);
2.insert into test(id) SELECT ROW_NUMBER () OVER () FROM bigtable limit 20000000; (generate a serie of BIGINT from 1 to 20000000)
3.delete from test where id = 1;
4.delete from test where id = 20000000;
Actual Results:
select count(*) from test
19999999 rows
Expected Results:
select count(*) from test
19999998 rows
I never encounter this problem on table with less of 2 millions reccords.
I try to insert 1 million reccord step by step, the bug appear at 2 million (nearly).
Sometimes, after fews manipulations on data (insert/delete), the problem disapear but appear again when I stop and restart the database.
I think it's related to the BAT files and transaction process, but I need some specific information in order to know what to do to solve this bug.
I can reproduce the problem in the Aug2011 branch.
A select * from test where id = {1, 20000000}; (two individual queries) do give the expected results before and after the deletes: one value before, no value after.
The query
select * from test where id in (1, 20000000);
gives an unexpected result: the value 20000000.
Added test for bug #2882.
This test runs fine when running single threaded.
It results in a timeout and totally bogus results when running
multi-threaded.
Date: 2011-09-14 17:55:17 +0200
From: seriousman
To: SQL devs <>
Version: 11.5.1 (Aug2011) [obsolete]
Depends on: #2883
Last updated: 2011-09-30 10:58:45 +0200
Comment 16219
Date: 2011-09-14 17:55:17 +0200
From: seriousman
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110816 Fedora/3.6.20-1.fc14 Firefox/3.6.20
Build Identifier:
I have some problems for deleting reccords on a table of 20000000 rows.
I've created a table 'test' and inserted in one operation 20000000 rows on this table.
There is only one column in this table : 'id' and values are 'BIGINT' from 1 to 20000000.
When I delete first row of the table 'test' it work, but when I try to delete the last reccord, it seem the delete did not work:
I try to insert data on other table with 'order by desc' and it's the opposite (can't delete value 1).
Reproducible: Always
Steps to Reproduce:
1.create table test(id bigint);
2.insert into test(id) SELECT ROW_NUMBER () OVER () FROM bigtable limit 20000000; (generate a serie of BIGINT from 1 to 20000000)
3.delete from test where id = 1;
4.delete from test where id = 20000000;
Actual Results:
select count(*) from test
19999999 rows
Expected Results:
select count(*) from test
19999998 rows
I never encounter this problem on table with less of 2 millions reccords.
I try to insert 1 million reccord step by step, the bug appear at 2 million (nearly).
Sometimes, after fews manipulations on data (insert/delete), the problem disapear but appear again when I stop and restart the database.
I think it's related to the BAT files and transaction process, but I need some specific information in order to know what to do to solve this bug.
Comment 16223
Date: 2011-09-15 10:19:28 +0200
From: @sjoerdmullender
I can reproduce the problem in the Aug2011 branch.
A select * from test where id = {1, 20000000}; (two individual queries) do give the expected results before and after the deletes: one value before, no value after.
The query
select * from test where id in (1, 20000000);
gives an unexpected result: the value 20000000.
Comment 16224
Date: 2011-09-15 11:04:56 +0200
From: @sjoerdmullender
Changeset 08a38dbbbd3f 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=08a38dbbbd3f
Changeset description:
Comment 16226
Date: 2011-09-15 15:47:09 +0200
From: @sjoerdmullender
The test that I checked in fails among other reasons because of bug #2883.
Comment 16277
Date: 2011-09-16 15:10:39 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
Comment 16285
Date: 2011-09-16 15:48:57 +0200
From: @sjoerdmullender
Changeset c22ffd42d642 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=c22ffd42d642
Changeset description:
Comment 16288
Date: 2011-09-16 15:50:52 +0200
From: @sjoerdmullender
Changeset 88185cfea41c fixes the problem.
Comment 16352
Date: 2011-09-30 10:58:45 +0200
From: @grobian
Released in Aug2011-SP1
The text was updated successfully, but these errors were encountered: