Database management tables need sharding keys
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
-
loose_foreign_keys_deleted_recordsneeds a sharding key.- If there is data relevant to an org in this table, and if Org Mover doesn't move it, then the deletions won't be performed after the move, and some data will be orphaned in the destination cell. Org Mover can only (efficiently) move PG data that has a sharding key.
-
background_migrationandbatched_background_migrationrelated tables, there are many.- If there is data relevant to an org in these tables, and if Org Mover doesn't move it, then the data migrations won't be completed for that org after the move. Org Mover can only (efficiently) move PG data that has a sharding key.
Edited by 🤖 GitLab Bot 🤖