Bug #21290
Updated by Peter Amstutz 5 months ago
If a collection has a very large number of past versions (in this case, 2000), operations involving @sync_past_versions@ (moving, trashing) will time out.
The current implementation loads each record, updates attributes, and saves it back.
We probably want to update the fields directly with SQL UPDATE.
The fields that get synchronized are:
['uuid', 'owner_uuid', 'delete_at', 'trash_at', 'is_trashed', 'replication_desired', 'storage_classes_desired']