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

Fix SQLite database lock on Reader #477

Merged
merged 1 commit into from Jun 30, 2021
Merged

Conversation

thebaer
Copy link
Member

@thebaer thebaer commented Jun 25, 2021

Fetching posts for the Reader involves an additional query on each row, which previously ran into our connection limit to the database and caused it to lock up. This increases the connection limit from 1 to 2, to allow this.

This is meant to be a quick, safe fix, but there could always be a better solution.

Fixes #467


  • ☑ I have signed the CLA

Fetching posts for the Reader involves an additional query on each row,
which previously ran into our connection limit to the database and caused
it to lock up. This increases the connection limit from 1 to 2, to allow
this.

This is meant to be a quick, safe fix, but there could always be a better
solution.

Fixes #467
@thebaer thebaer linked an issue Jun 25, 2021 that may be closed by this pull request
@thebaer
Copy link
Member Author

thebaer commented Jun 30, 2021

Merging now.

@thebaer thebaer added this to the 0.13.1 milestone Jun 30, 2021
@thebaer thebaer merged commit 672fa10 into hotfix-0.13.1 Jun 30, 2021
@thebaer thebaer deleted the fix-sqlite-reader-lock branch June 30, 2021 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

After updating to v0.13.0 /read will not load
1 participant