publish task fails for repository with 267000 RPMs

[dkliban]

Version
3.83.0

Describe the bug
I synced packages from https://download.copr.fedorainfracloud.org/results/@rubygems/rubygems/fedora-rawhide-x86_64/ using the on_demand policy. Then I tried to create a publication. The following error occurred:

$ pulp -p prod task show --href /api/pulp/dkliban-test/api/v3/tasks/0197f8e4-85ed-792d-abd8-6fee51e192cb/
{
  "pulp_href": "/api/pulp/dkliban-test/api/v3/tasks/0197f8e4-85ed-792d-abd8-6fee51e192cb/",
  "prn": "prn:core.task:0197f8e4-85ed-792d-abd8-6fee51e192cb",
  "pulp_created": "2025-07-11T09:50:15.534397Z",
  "pulp_last_updated": "2025-07-11T09:50:15.534418Z",
  "state": "failed",
  "name": "pulp_rpm.app.tasks.publishing.publish",
  "logging_cid": "60e21812c95140f4beb2d684ffcfcd23",
  "created_by": null,
  "unblocked_at": "2025-07-11T09:50:15.622027Z",
  "started_at": "2025-07-11T09:50:15.714680Z",
  "finished_at": "2025-07-11T09:50:23.477677Z",
  "error": {
    "traceback": "  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/pulpcore/tasking/tasks.py\", line 95, in _execute_task\n    func(*args, **kwargs)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/pulp_rpm/app/tasks/publishing.py\", line 385, in publish\n    publication_data.populate()\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/pulp_rpm/app/tasks/publishing.py\", line 283, in populate\n    self.publish_artifacts(main_content)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/pulp_rpm/app/tasks/publishing.py\", line 159, in publish_artifacts\n    for content_artifact in contentartifact_qs.values(*fields).iterator():\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/models/query.py\", line 516, in _iterator\n    yield from iterable\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/models/query.py\", line 208, in __iter__\n    for row in compiler.results_iter(\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/models/sql/compiler.py\", line 1513, in results_iter\n    results = self.execute_sql(\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/models/sql/compiler.py\", line 1562, in execute_sql\n    cursor.execute(sql, params)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/sentry_sdk/utils.py\", line 1811, in runner\n    return sentry_patched_function(*args, **kwargs)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/sentry_sdk/integrations/django/__init__.py\", line 651, in execute\n    result = real_execute(self, sql, params)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/backends/utils.py\", line 67, in execute\n    return self._execute_with_wrappers(\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/backends/utils.py\", line 80, in _execute_with_wrappers\n    return executor(sql, params, many, context)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/backends/utils.py\", line 89, in _execute\n    return self.cursor.execute(sql, params)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/utils.py\", line 91, in __exit__\n    raise dj_exc_value.with_traceback(traceback) from exc_value\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/backends/utils.py\", line 89, in _execute\n    return self.cursor.execute(sql, params)\n  File \"/usr/local/lib/pulp/lib64/python3.9/site-packages/psycopg/_server_cursor.py\", line 106, in execute\n    raise ex.with_traceback(None)\n",
    "description": "sending query and params failed: number of parameters must be between 0 and 65535"
  },
  "worker": "/api/pulp/default/api/v3/workers/0197f567-264a-708f-a70b-a24204c96bc1/",
  "parent_task": null,
  "child_tasks": [],
  "task_group": null,
  "progress_reports": [],
  "created_resources": [],
  "reserved_resources_record": [
    "shared:prn:rpm.rpmrepository:0197f718-f387-7d23-b4d1-40eba14ef45b",
    "shared:prn:core.domain:01978321-c5c6-7b4c-87be-032074049001"
  ]
}

[pedro-psb]

I'm not sure what exactly query is causing this, but there is some advice about this problem on postgres channels: https://www.postgresql.org/message-id/3728363.1669229253%40sss.pgh.pa.us