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.

After upgrading from Satellite 6.1 to Satellite 6.2, we experienced severe performance issues in Satellite. We managed to track the problem down to a specific query related to Tasks which seemed to hit a degenerate corner case in postgres that caused the query to run extremely slowly.

We've temporarily corrected the issue by flushing all of the Tasks in Satellite to clear out the Tasks tables.  However, it would probably be a good idea to have the Satellite engineering team look at this issue and see if there is anything they can do to prevent the issue from recurring.  For example, perhaps the query can be rewritten or a new index can be created to avoid hitting this degenerate corner case in postgres?

We happen to have an EnterpriseDB support contract, so we also plan to ask EnterpriseDB to look into this problem.  Specifically, we would like EnterpriseDB to determine whether this degenerate corner case should be considered a bug in postgres.