Sun Cluster Data Service for PostgreSQL Guide for Solaris OS

Configuration Requirements

The configuration requirements in this section apply only to Sun Cluster HA for PostgreSQL.


Caution – Caution –

If your data service configuration does not conform to these requirements, the data service configuration might not be supported.


Dependencies Between Sun Cluster HA for PostgreSQL Components

The dependencies between the Sun Cluster HA for PostgreSQL components are described in the following table.

Table 2 Dependencies Between Sun Cluster HA for PostgreSQL Components

Component 

Dependency 

PostgreSQL resource in a Solaris 10 global zone,zone or in Solaris 9 

SUNW.HAStoragePlus This dependency is required only if the configuration uses a failover file system, of file systems in a zone.

SUNW.LogicalHostName

PostgreSQL resource in a Solaris 10 HA container. 

Sun Cluster HA for the Solaris Container boot resource. 

SUNW.HAStoragePlus

SUNW.LogicalHostName—This dependency is required only if the zones boot resource does not manage the zone's IP address.

You set these dependencies, when you register and configure Sun Cluster HA for PostgreSQL. For more information, see Registering and Configuring Sun Cluster HA for PostgreSQL.

If more elaborate dependencies are required, see the r_properties(5) and rg_properties(5) man pages for further dependencies and affinities settings.

Parameter File for Sun Cluster HA for PostgreSQL

Sun Cluster HA for PostgreSQL requires a parameter file to pass configuration information to the data service. You must create a directory for this file. Because the directory must be available on each node that is to host the PostgreSQL database, place the directory on the shared storage. If Sun Cluster HA for PostgreSQL is configured for an HA container, this file must be available in this zone. The parameter file is created automatically when the resource is registered.

Configuration Requirements for the WAL File Shipping Without Shared Storage Configuration

For the WAL file shipping without shared storage configuration, the rsync utility is required. As an additional requirement, you need to link some PostgreSQL configuration files outside the PGDATA directory. Otherwise these files are destroyed during the resilvering of the primary database. Information about how to perform these steps is available in the comments of the resilver1 script. The PostgreSQL users on both nodes require a nonpassword login on each node.