lol yes we have a "vacuum problem" rn, it's not clear what the issue is but we're getting errors about it
-
This Tweet is unavailable.
-
This Tweet is unavailable.
It's a 15k row table w/ 0 deletions and no column changes, so it shouldn't be needing to get vacuumed
-
-
This Tweet is unavailable.
-
I even shut down the background worker that was conflicting with the exclusive lock and then manually ran a vacuum full on it (took 1.5s since it's a tiny table). Same deal.
- 9 more replies
-
-
-
Our main problem table is `version_downloads` (which is keyed by `(version_id, date)`) -- will definitely get partitioned eventually, not anywhere close to that though
-
/me nods
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.