-
-
Notifications
You must be signed in to change notification settings - Fork 859
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
Don't require superuser permission to run database migrations #2863
Comments
I figured out how to work around this in #2784 (comment). I didn't look at the feasibility of this but maybe some checks can be added around these queries to detect whether this is necessary and do so conditionally. I don't really know how bad the previous performance was, but maybe that PR could simply be reverted. |
Not really sure of a good solution to this one. We shouldn't revert that PR, as its a DB migration. We might possibly be able to just remove that trigger disable. People have mostly upgraded past that point anyway. |
Fixes <LemmyNet#2863> and the problem introduced by the previous commit.
Fixes <LemmyNet#2863> and the problem introduced by the previous commit.
Some admins reported problems installing Lemmy because the db migrations require superuser permissions. This is not available on some cloud hosting providers. So it would be nice if we could get rid of this requirement. Apparently the problem is caused by
disable trigger all
.The text was updated successfully, but these errors were encountered: