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
In purge_history we create a temporary table (events_to_purge, which we drop at the end of the purge) to store events we want to purge, alongside with whether or not we should delete them. It feels like there's room for improvement there, as in theory we should be able to only insert events we want to purge. I'm not sure how complicated this would be in practice, though. According to the code, we seem to use all the events in events_to_purge, even those not slated for deletion, to figure out state groups to remove. However according to comments it also seems to think that all events in that table are slated for deletion.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #13419.
In
purge_history
we create a temporary table (events_to_purge
, which we drop at the end of the purge) to store events we want to purge, alongside with whether or not we should delete them. It feels like there's room for improvement there, as in theory we should be able to only insert events we want to purge. I'm not sure how complicated this would be in practice, though. According to the code, we seem to use all the events inevents_to_purge
, even those not slated for deletion, to figure out state groups to remove. However according to comments it also seems to think that all events in that table are slated for deletion.The text was updated successfully, but these errors were encountered: