Incorrect sequence owners on dev instance

With !197521 (merged) deployed to our dev instances, I noticed that on dev.gitlab.org some sequences have no owners:

Sequence Name	Current Owner	Expected Owner
public.broadcast_messages_id_seq		public.broadcast_messages.id
public.deploy_keys_projects_id_seq		public.deploy_keys_projects.id
public.emails_id_seq		public.emails.id
public.integrations_id_seq		public.integrations.id
public.issues_id_seq		public.issues.id
public.keys_id_seq		public.keys.id
public.merge_request_diffs_id_seq		public.merge_request_diffs.id
public.merge_requests_id_seq		public.merge_requests.id
public.milestones_id_seq		public.milestones.id
public.namespaces_id_seq		public.namespaces.id
public.projects_id_seq		public.projects.id
public.protected_branches_id_seq		public.protected_branches.id
public.snippets_id_seq		public.snippets.id
public.tags_id_seq		public.tags.id
public.users_id_seq		public.users.id
public.web_hooks_id_seq		public.web_hooks.id

I believe this happens for any old GitLab instances that were created with the original ActiveRecord schema. db/structure.sql usually has a clear owner for a sequence:

CREATE SEQUENCE broadcast_messages_id_seq
ALTER SEQUENCE broadcast_messages_id_seq OWNED BY broadcast_messages.id;