Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1485101[details]
When I have added 'log_min_duration_statement = 10' to the PostgreSQL config and reloaded, this was logged
Description of problem:
Searching for errata when adding errata filter to content view is very slow
Version-Release number of selected component (if applicable):
satellite-6.4.0-14.el7sat.noarch (snap 17 updated to 22)
How reproducible:
always
Steps to Reproduce:
1. Have sat with about 1000 advisories in repo XYZ
2. Create content view
3. Add repository XYZ into that
4. Add yum filter:
Content Type: Erratum - by ID
Inclusion Type: Include
5. Now you are taken to errata searching screen, where I entered:
Start Date: <that every errata matches>
End Date: <that every errata matches>
Actual results:
It takes about 15 seconds to show the results
Expected results:
It should be very fast
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Created attachment 1485101 [details] When I have added 'log_min_duration_statement = 10' to the PostgreSQL config and reloaded, this was logged Description of problem: Searching for errata when adding errata filter to content view is very slow Version-Release number of selected component (if applicable): satellite-6.4.0-14.el7sat.noarch (snap 17 updated to 22) How reproducible: always Steps to Reproduce: 1. Have sat with about 1000 advisories in repo XYZ 2. Create content view 3. Add repository XYZ into that 4. Add yum filter: Content Type: Erratum - by ID Inclusion Type: Include 5. Now you are taken to errata searching screen, where I entered: Start Date: <that every errata matches> End Date: <that every errata matches> Actual results: It takes about 15 seconds to show the results Expected results: It should be very fast