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 a connection pool #567

Open
Tracked by #664
jbearer opened this issue May 6, 2024 · 0 comments
Open
Tracked by #664

Use a connection pool #567

jbearer opened this issue May 6, 2024 · 0 comments
Assignees

Comments

@jbearer
Copy link
Member

jbearer commented May 6, 2024

We should have a pool of connections which we use for queries, which will open up more concurrency. We should also have a single, separate connection used for updates (SqlStorage::transaction should use this connection). Since queries will no longer use the same connection as updates, there is no longer a risk of concurrent queries seeing a partially updated state. Thus, this is a step towards #400 .

Sqlx has connection pooling built in, so it may be best to wait and do this after #271

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant