Bug 1023560

Summary: Remove steps to install/configure pgtune from installation doc
Product: Red Hat Satellite 5 Reporter: dipu <ddevaraj>
Component: Docs Installation GuideAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: Dan Macpherson <dmacpher>
Severity: medium Docs Contact:
Priority: medium    
Version: 560CC: fdupont, joallen, mmurray, xdmoon, yjog
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-21 02:02:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1018166    

Description dipu 2013-10-25 18:41:31 UTC
Description of problem:
 https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/5.6/html-single/Installation_Guide/index.html#sect-Installation_Guide-External_Database_Requirements given steps to install/configure pgtune but this package is not available in rhn. These instructions were generic ones used for Spacewalk, and looks like it wasn't tested/validated when moved into formal docs.
So this part needs to be remove from the installation document.
-----------------------------
 PostgreSQL requires some tuning to provide the optimal performance of your Red Hat Satellite server. The pgtune tool provides an easy way to tune a PostgreSQL configuration file for performance in different contexts, such as data warehouses, online transactions, web applications, or mixed usage. The following procedure shows how to tune your PostgreSQL External Database for optimal performance with Red Hat Satellite.

Procedure 2.2. To tune your PostgreSQL server

    Install the pgtune package.

    # yum install pgtune

    Run the pgtune command.

    # pgtune --type=web -c 600 -i /var/lib/pgsql/data/postgresql.conf >/tmp/pgtune.conf

    The --type=web parameter configures PostgreSQL for web application use and the -c 600 set the maximum connections to 600. This results in a temporary pgtune.conf configuration file.
    Verify the changes made to the new pgtune.conf.

    # diff -u /var/lib/pgsql/data/postgresql.conf /tmp/pgtune.conf

    Back up your current postgresql.conf settings.

    # cp /var/lib/pgsql/data/postgresql.conf /var/lib/pgsql/data/postgresql.conf.bak

    Copy the pgtune.conf file over the postgresql.conf.

    # cp /tmp/pgtune.conf /var/lib/pgsql/data/postgresql.conf

    Restart the PostgreSQL server for the changes to take effect.

    # service postgresql restart

pgtune has tuned your External Database for optimal performance.
For manual configuration of your /var/lib/pgsql/data/postgresql.conf, set the following parameters:

#shared_buffers = 24MB
maintenance_work_mem = 224MB
checkpoint_completion_target = 0.7
effective_cache_size = 2560MB
work_mem = 6MB
wal_buffers = 4MB
checkpoint_segments = 8
shared_buffers = 896MB
max_connections = 600
------------------------------


Version-Release number of selected component (if applicable):
satellite 5.6 installation guide

Comment 1 Fabien Dupont 2013-10-31 13:36:37 UTC
Couldn't we put optimisation tips instead ? I mean that a DBA should have some information about the resources needed : storage size, number of connexions... so that he could decide on the tuning paramaters he has to set.

Comment 3 Dan Macpherson 2014-01-21 15:19:34 UTC
This bug can be worked on early during the planning stages for Satellite 5.7.

Comment 6 Athene Chan 2014-02-28 05:32:38 UTC
(In reply to Fabien Dupont from comment #1)
> Couldn't we put optimisation tips instead ? I mean that a DBA should have
> some information about the resources needed : storage size, number of
> connexions... so that he could decide on the tuning paramaters he has to set.

I think tuning would have to be another request. That would need to be added in the Reference Guide or one of the other guides unless there is a particular requirement for the database tuning AT installation time.

Comment 9 Clifford Perry 2014-12-01 09:33:26 UTC
*** Bug 1168096 has been marked as a duplicate of this bug. ***