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
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
device_inbox can have a huge number of rows when deleting a user, which makes user deletion slow and costly. Instead, we should do the deletion of rows in device_inbox as a background task (potentially using #15891).
The text was updated successfully, but these errors were encountered:
erikjohnston
added
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
labels
Aug 10, 2023
I think we can use the new TaskScheduler class to add a task in the background to delete all to-device messages for the device after deletion. The best way of doing that would likely be to just repeatedly do DELETE FROM device_inbox WHERE user_id = ? AND device_id = ? AND stream_ordering < ? LIMIT 100. Care should be taken to only delete to-device messages from before the deletion, to handle the case where the device logs back in again with the same device ID.
device_inbox
can have a huge number of rows when deleting a user, which makes user deletion slow and costly. Instead, we should do the deletion of rows indevice_inbox
as a background task (potentially using #15891).The text was updated successfully, but these errors were encountered: