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.

Sign up for GitHub

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

Jump to bottom

Fix Potential Btree Corruption Bug #986

Closed
mlucy opened this issue Jun 12, 2013 · 2 comments
Closed

Fix Potential Btree Corruption Bug #986

mlucy opened this issue Jun 12, 2013 · 2 comments
Assignees
@mlucy
Milestone
1.7

Comments

@mlucy
Copy link
Member

mlucy commented Jun 12, 2013

There's currently a bug where, if someone issues an update or replace that handles an empty kv_location and returns an object with the wrong primary key, we'll might end up with a btree that has rows in the wrong spot.

We should fix this by checking the print_primary value of the primary key of the new object to be inserted against the actual value on disk.
@ghost ghost assigned mlucy Jun 12, 2013
@mlucy
Copy link
Member Author

mlucy commented Jun 25, 2013

This is in code-review 664 by @Tryneus.

@mlucy
Copy link
Member Author

mlucy commented Jun 26, 2013

This is in next.

@mlucy mlucy closed this as completed Jun 26, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mlucy mlucy

Labels
None yet
Projects
None yet
Milestone
1.7
Development

No branches or pull requests
1 participant
@mlucy