[Satellite6] slower performance followed by bigger foreman postgres DB size due to logs table

Solution Verified - Updated -


  • generic slowness of Satellite/foreman
  • foreman postgres DB consuming lot of disk space
  • large numbers of rows (millions+) in the Foreman 'logs' table
  • optionally, postgres: foreman foreman processes consume a lot of memory
  • further check identified logs table in foreman database consuming majority of disk space


Red Hat Satellite 6
OpenSCAP scanning features of Red Hat Satellite 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content