We have seen reports about having some _seq has reached their max value, and that is because there is a large amount of data in the table and their datatype was set to integer (and so as for the relevant primary key e.g. id).

Almost every time, the fix was to change the datatype for the main primary id of the table, as well as the relevant sequence to be bigint, which is also the Rails default.

Instead of users reporting these issues for different tables at different occasions and needing to apply the same fix again and again through new migrations, it would be good to invest some time, check the possible tables that have the potential to store a huge amount of data, and fix that table's primary key and the related sequence datatype to be bigint.

For reference, here are some related bugs that have already been reported:

SAT-34624 ERROR: nextval: reached maximum value of sequence "katello_erratum_packages_id_seq" during concurrent repository sync plan executions

SAT-38813 ERROR: nextval: reached maximum value of sequence "logs_id_seq"

SAT-38887 'Katello::Errors::Pulp3Error: nextval: reached maximum value of sequence "container_blobmanifest_id_seq"' during container image sync

SAT-35478 Client failed to register to the Satellite with "integer out of range" error

SAT-24878 Content view publish failing with katello_repository_rpms_id_seq reached maximum value error