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

A better error message attempting to use ATTACH DATABASE #419

Closed
manadart opened this issue Oct 20, 2022 · 3 comments · Fixed by #440
Closed

A better error message attempting to use ATTACH DATABASE #419

manadart opened this issue Oct 20, 2022 · 3 comments · Fixed by #440
Assignees

Comments

@manadart
Copy link

When attempting to use ATTACH DATABASE, not supported by Dqlite, the error reports:

disk I/O error

A more descriptive error would benefit users.

@freeekanayaka
Copy link
Contributor

Out of curiosity, why did you try to use ATTACH DATABASE? Do you have a use case for that or were you just playing around?

@manadart
Copy link
Author

For Juju's use-case, we are looking at having a DB per model.

We were looking at ATTACH DATABASE under the assumption that each DB connection would consume an OS thread. We've been told since that this is not the case, so we don't actually need it.

@cole-miller cole-miller self-assigned this Nov 21, 2022
@cole-miller
Copy link
Contributor

It's possible that the same underlying problem is cropping up in #435, because one of the first things that happens in the implementation of VACUUM is an ATTACH DATABASE. In that instance the ATTACH DATABASE appears to succeed, though.

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

Successfully merging a pull request may close this issue.

3 participants