db: fix newly-introduced SINGLEDEL+DELSIZED bug #3088
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In bfb2e6a (#3081) a small refactor the handling of DELSIZED introduced a bug when a DELSIZED shadows a SINGLEDEL. When a DELSIZED and a SINGLEDEL meet in a compaction, we began accidentally emitting a SINGLEDEL rather than a DEL, weakening the tombstone. Previously the problematic code branch was only ever executed when a DELSIZED and DEL met, so iterKey.Kind() was always DEL.
Fix #3087.