Note:

• If you already have a PostgreSQL database set up, you can skip to the section Configuring and Starting the PostgreSQL Server to verify that your PostgreSQL configurations meet the requirements for Cloudera Manager.
• Make sure that the data directory, which by default is /var/lib/postgresql/data/, is on a partition that has sufficient free space.
• Cloudera Manager 5.8.x and higher supports the use of a custom schema name. For more information, see https://www.postgresql.org/docs/current/static/ddl-schemas.html.

1. Use one or more of the following commands to set the locale:

   export LANGUAGE=en_US.UTF-8
   export LANG=en_US.UTF-8
   export LC_ALL=en_US.UTF-8
   locale-gen en_US.UTF-8
   dpkg-reconfigure locales

2. Install PostgreSQL packages:
   • RHEL

     $ sudo yum install postgresql-server

   • SLES

     $ sudo zypper install postgresql91-server

       Note: This command will install PostgreSQL 9.1. If you want to install a different version, you can use zypper search postgresql to search for an available supported version. See CDH and Cloudera Manager Supported Databases.
   • Debian/Ubuntu

     $ sudo apt-get install postgresql

By default, PostgreSQL only accepts connections on the loopback interface. You must reconfigure PostgreSQL to accept connections from the Fully Qualified Domain Name (FQDN) of the hosts hosting the management roles. If you do not make these changes, the management processes cannot connect to and use the database on which they depend.

1. Enable MD5 authentication. Edit pg_hba.conf, which is usually found in /var/lib/pgsql/data or /etc/postgresql/8.4/main. Add the following line:

   host all all 127.0.0.1/32 md5

   If the default pg_hba.conf file contains the following line:

   host all all 127.0.0.1/32 ident

   then the host line specifying md5 authentication shown above must be inserted before this ident line. Failure to do so may cause an authentication error when running the scm_prepare_database.sh script. You can modify the contents of the md5 line shown above to support different configurations. For example, if you want to access PostgreSQL from a different host, replace 127.0.0.1 with your IP address and update postgresql.conf, which is typically found in the same place as pg_hba.conf, to include:

   listen_addresses = '*'

2. Initialize the external PostgreSQL database. For some versions of PostgreSQL, this occurs automatically the first time that you start the PostgreSQL server. In this case, issue the command:

   $ sudo service postgresql start

   In other versions, you must explicitly initialize the database using one of the following commands:
   • If the PostgreSQL database uses the SLES 12 operating system:

     $ sudo service postgresql initdb --pgdata=/var/lib/pgsql/data --encoding=UTF-8
     

   • All other operating systems:

     $ sudo service postgresql initdb

   See the PostgreSQL documentation for more details.
3. Configure settings to ensure your system performs as expected. Update these settings in the /var/lib/pgsql/data/postgresql.conf or /var/lib/postgresql/data/postgresql.conf file. Settings vary based on cluster size and resources as follows:
   • Small to mid-sized clusters - Consider the following settings as starting points. If resources are limited, consider reducing the buffer sizes and checkpoint segments further. Ongoing tuning may be required based on each host's resource utilization. For example, if the Cloudera Manager Server is running on the same host as other roles, the following values may be acceptable:
     • shared_buffers - 256MB
     • wal_buffers - 8MB
     • checkpoint_segments - 16
     • checkpoint_completion_target - 0.9
   • Large clusters - Can contain up to 1000 hosts. Consider the following settings as starting points.
     • max_connection - For large clusters, each database is typically hosted on a different host. In general, allow each database on a host 100 maximum connections and then add 50 extra connections. You may have to increase the system resources available to PostgreSQL, as described at Connection Settings.
     • shared_buffers - 1024 MB. This requires that the operating system can allocate sufficient shared memory. See PostgreSQL information on Managing Kernel Resources for more information on setting kernel resources.
     • wal_buffers - 16 MB. This value is derived from the shared_buffers value. Setting wal_buffers to be approximately 3% of shared_buffers up to a maximum of approximately 16 MB is sufficient in most cases.
     • checkpoint_segments - 128. The PostgreSQL Tuning Guide recommends values between 32 and 256 for write-intensive systems, such as this one.
     • checkpoint_completion_target - 0.9. This setting is only available in PostgreSQL versions 8.3 and higher, which are highly recommended.
4. Configure the PostgreSQL server to start at boot.
   • RHEL

     $ sudo /sbin/chkconfig postgresql on
     $ sudo /sbin/chkconfig --list postgresql
     postgresql          0:off   1:off   2:on    3:on    4:on    5:on    6:off

   • SLES

     $ sudo chkconfig --add postgresql

   • Debian/Ubuntu

     $ sudo chkconfig postgresql on

5. Start or restart the PostgreSQL database:

   $ sudo service postgresql restart

To install and configure PostgreSQL for Hue, see Connect Hue to PostgreSQL.