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

DB content massacrated when opening a 2.1.214 DB with current master #3637

Closed
wburzyns opened this issue Oct 6, 2022 · 3 comments · Fixed by #3644
Closed

DB content massacrated when opening a 2.1.214 DB with current master #3637

wburzyns opened this issue Oct 6, 2022 · 3 comments · Fixed by #3644

Comments

@wburzyns
Copy link

wburzyns commented Oct 6, 2022

As the title says. It looks like all the LOBS are gone. Has the on-disk-format been changed?

@andreitokar
Copy link
Contributor

At least I can say, that there is no such intention. It would be greatly appreciated, if yo can provide a test case - a simple database file or java program, which would create such file (using 2.1.214), and then it fails with the current master build.

@wburzyns
Copy link
Author

wburzyns commented Oct 7, 2022

Here you go. Use _1 with 214 and _2 with current master.
Be advised that the issue is not reproducible with smaller values of NUM_PUSHES in _1. I had to set it to 100 to reproduce the problem. I don't know if all the steps in _1 are necessary for reproduction - I just tried to mimic what's happening on my production.
H2_LOB_massacre_1.java.txt
H2_LOB_massacre_2.java.txt

@andreitokar
Copy link
Contributor

Thank you @wburzyns !
I can recreate the problem now, and I think I know what is broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants