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

Use RWMutex in MemDB #55

Closed
erikgrinaker opened this issue Mar 4, 2020 · 0 comments · Fixed by #56
Closed

Use RWMutex in MemDB #55

erikgrinaker opened this issue Mar 4, 2020 · 0 comments · Fixed by #56
Assignees
Labels
T:breaking Type: Breaking

Comments

@erikgrinaker
Copy link
Contributor

MemDB currently uses a Mutex, but it should use an RWMutex instead. However, the mutex is returned through the public Mutex() method, so it's a breaking change. We should unexport Mutex() in #54 and then change it.

@erikgrinaker erikgrinaker added the T:breaking Type: Breaking label Mar 4, 2020
@erikgrinaker erikgrinaker self-assigned this Mar 4, 2020
faddat pushed a commit to faddat/tm-db that referenced this issue Feb 21, 2024
* Rename section for Go compiler update changelog entry

Signed-off-by: Thane Thomson <[email protected]>

* Add link to PR for grocksdb dependency update

Signed-off-by: Thane Thomson <[email protected]>

* Prepare v0.8.0 release in changelog

Signed-off-by: Thane Thomson <[email protected]>

* Build changelog

Signed-off-by: Thane Thomson <[email protected]>

* go.mod: Remove unused replace directive

Signed-off-by: Thane Thomson <[email protected]>

* Remove unnecessary coverage file

Signed-off-by: Thane Thomson <[email protected]>

* .gitignore: Ignore code coverage artifacts

Signed-off-by: Thane Thomson <[email protected]>

* Update release date

Signed-off-by: Thane Thomson <[email protected]>

---------

Signed-off-by: Thane Thomson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T:breaking Type: Breaking
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant