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

LMDB: Fix GC and record count for deletions #4954

Closed
kenwenzel opened this issue Apr 17, 2024 · 0 comments
Closed

LMDB: Fix GC and record count for deletions #4954

kenwenzel opened this issue Apr 17, 2024 · 0 comments
Assignees
Labels
🐞 bug issue is a bug
Milestone

Comments

@kenwenzel
Copy link
Contributor

Current Behavior

The LmdbStore does not correctly count records for deletions and GC may not work in case of auto-growing the database.

Expected Behavior

Correctly count deleted records and always support correct GC of values.

Steps To Reproduce

No response

Version

5.0.0

Are you interested in contributing a solution yourself?

None

Anything else?

No response

@kenwenzel kenwenzel added the 🐞 bug issue is a bug label Apr 17, 2024
kenwenzel added a commit to kenwenzel/rdf4j that referenced this issue Apr 17, 2024
Ensures that GC is also working if triple store needs to grow
and that the correct count is returned for statement removals.
kenwenzel added a commit to kenwenzel/rdf4j that referenced this issue Apr 18, 2024
Ensures that GC is also working if triple store needs to grow
and that the correct count is returned for statement removals.
kenwenzel added a commit to kenwenzel/rdf4j that referenced this issue Apr 22, 2024
Ensures that GC is also working if triple store needs to grow
and that the correct count is returned for statement removals.
kenwenzel added a commit to kenwenzel/rdf4j that referenced this issue Apr 22, 2024
@hmottestad hmottestad added this to the 5.0.0 milestone May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug issue is a bug
Projects
None yet
Development

No branches or pull requests

2 participants