Migrate geo package_file_registry package_file_id and id to bigint
While checking the Geo tracking database for columns that are defined as int4
while there are defined as bigint
in the primary GitLab database we found the following discrepancy:
package_file_registry.package_file_id
is defined as an integer even though packages_package_files.id
is defined as a bigint
in the primary database.
package_file_registry.id
is also defined as an integer, and it can scale proportionally with packages_package_files.id
.
Definition of Done
-
A migration is created to transition package_file_registry.id
to a bigint -
A migration is created to transition package_file_registry.package_file_id
to a bigint
Considerations
Since there's no write access to the primary database, we'll need to use a different type of background migration to do this. Or add something to support the new kind in geo.
Edited by Michael Kozono