## Problem Certain PG tables are not going to be replicated. Such as: - `lfs_objects` - `pool_repositories` - `shards` Geo currently assumes that all PG data is replicated. LFS object and Git repo replication will not work if those tables are missing relevant data. ## Proposal Sub-epics: - Develop LFS special handling (replicate LFS object projects and regenerate LFS objects rows) - This will look like adding a "new data type" just for .com. And we'll need custom "sync" logic to regenerate the `lfs_objects` rows as needed. - Develop Git repository replication special handling (shards are different on both sides) - This looks to be mostly Rails work inside of sync jobs. The Postgres dump/restore will need to exclude certain tables or fields though. <!--STATUS NOTE START--> <!--STATUS NOTE END-->