You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That was my thinking too, but their numbers are all fairly normal - 184 languages (all of them), 53 community blocks, 31 hidden posts, 89 community follows.
I tried playing around with the query and removing these lines, makes it execute immediately. Modifying the other "and not exists" chunks doesn't help, only this one.
- AND NOT EXISTS (
- SELECT 1 FROM community_block
- WHERE post_aggregates.community_id = community_block.community_id
- AND community_block.person_id = 458479
- )
However the users data in that table looks normal. I even deleted all their rows and it didn't impact performance at all. Maybe this isn't related, and it's just pushing the postgres query optimizer into some other direction?
I tried dropping to a single language as well, no change. I've done a vacuum as well.
Requirements
Summary
One of our users has been reporting repeated timeouts / issues and it's reproducible under their user account only.
I haven't received any other user reports and I can reproduce it by logging into their account, but not my own account.
Steps to Reproduce
Technical Details
The query at fault is a beefy one, and my attempts to decipher what's going on haven't gotten anywhere yet.
This takes about 2-3 minutes to run as the affected user, and under 1s for myself.
Version
0.19.8
Lemmy Instance URL
lemmy.ca
The text was updated successfully, but these errors were encountered: