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.
Description of problem:
BZ#1749233 is going to set log_min_duration_statement=1000 for PostgreSQL by default. However, this has a possible side effect on a large deployment where /var/lib/pgsql is mounted separately. The /var/lib/pgsql can be easily filled up
when slow queries are identified. For example, a slow query for selecting facts could consume a large space when there are many facts on a host.
Expected results:
A reasonable log_rotation_size should be set to prevent /var/lib/pgsql being filled up.
Comment 3sthirugn@redhat.com
2019-12-12 16:36:40 UTC
As per the email discussion, log_rotation_size of 200MB will be implemented to resolve this issue:
log_rotation_size: 200000
Comment 4sthirugn@redhat.com
2019-12-12 17:48:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1454