Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema corruption after several ALTER TABLE statements and server restart #3828

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed
Labels
bug Something isn't working normal SQL

Comments

@monetdb-team
Copy link

Date: 2015-10-21 13:45:22 +0200
From: @hannesmuehleisen
To: SQL devs <>
Version: 11.19.3 (Oct2014)
CC: ajdamico

Last updated: 2015-11-03 10:18:20 +0100

Comment 21362

Date: 2015-10-21 13:45:22 +0200
From: @hannesmuehleisen

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36
Build Identifier:

When performing fairly complex schema manipulation with many ALTER TABLE statements, the database is corrupted after a restart.

Reproducible: Always

Steps to Reproduce:

  1. run attached script

Actual Results:

identifier not found

Expected Results:

query results exactly the same (empty table) as before server restart

Comment 21363

Date: 2015-10-21 13:45:46 +0200
From: @hannesmuehleisen

Created attachment 361
script that provokes the issue

Attached file: hmda-bug.sh (application/octet-stream, 4458 bytes)
Description: script that provokes the issue

Comment 21364

Date: 2015-10-21 14:39:22 +0200
From: MonetDB Mercurial Repository <>

Changeset 68db09afc566 made by Hannes Muehleisen hannes@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=68db09afc566

Changeset description:

Test for Bug #3828

Comment 21368

Date: 2015-10-21 15:18:33 +0200
From: @sjoerdmullender

(In reply to Hannes Muehleisen from comment 0)

Reproducible: Always

I wasn't able to reproduce this always. But I did find that when I have samtools enable, the script does not fail, but when I have samtools disabled, the script fails.
When enabled, samtools causes more catalog changes during database creation. That may have to do with the difference in behavior.

Comment 21421

Date: 2015-10-29 16:57:19 +0100
From: MonetDB Mercurial Repository <>

Changeset 834b9795aa08 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=834b9795aa08

Changeset description:

When a candidate list is non-dense, the join result likely is too.
This fixes bug #3828.

Comment 21440

Date: 2015-11-03 10:18:20 +0100
From: @sjoerdmullender

Jul2015 SP1 has been released.

@monetdb-team monetdb-team added bug Something isn't working normal SQL labels Nov 30, 2020
@sjoerdmullender sjoerdmullender added this to the Ancient Release milestone Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working normal SQL
Projects
None yet
Development

No branches or pull requests

2 participants