Serviceguard Toolkits for Contrib User Guide Version A.12.00.00

tcpip_socket by listen_address. Depending on the parameter supported by
PostgreSQL, configure tcpip_socket=true or listen_addresses.
listen_addresses = <IP-List> # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
In listen_addresses, specify the IP addresses on which the server is to listen for connections
from client applications. The value takes the form of a comma-separated list of host names
and/or numeric IP addresses. The special entry * corresponds to all available IP interfaces.
Ensure that, the virtual IP is specified in listen_addresses ip-list.
Supported Configuration
This section explains the following supported configurations for PostgreSQL toolkit packages:
• Shared configuration
• Multiple instance configuration
NOTE:
• Each node must have the same version of the PostgreSQL application.
• Each node must have the same configuration directory where identical copies of the
configuration files for each instance are placed in the local or shared hard disk.
• Each node must have the same file system directories to access the same shared storage.
Local Configuration
In a typical local configuration, files are not shared among the nodes. If you opt to store the
configuration files on a local disk, you must replicate the configuration to local disks on all the
nodes configured to run the package. Identical copies of the PostgreSQL server configuration file
must reside in exactly the same locations on each node. If you update the information in a file on
a single node, you must update the files on all the other nodes with the same changes. Ensure that
all the files on all the nodes are identical and always up-to-date.
Shared configuration
In a shared configuration, the configuration and database files are placed all on the shared storage.
The same PostgreSQL data and configuration file are shared between the cluster nodes, so you
need not maintain identical copies on each node. In a cluster environment, each PostgreSQL
database server instance must have unique IP addresses.
When the package is created, one or more relocatable IP addresses are created for each
PostgreSQL database server. When the PostgreSQL database server package switches over from
one node to another, this instance is stopped, IP addresses are removed from the primary node,
IP addresses are reallocated to a standby node, and the instance is started on that node. Clients
are automatically connected or manually reconnected through these IP addresses to the identical
PostgreSQL database server on the standby node.
Multiple PostgreSQL Instances Configuration
PostgreSQL database server supports multiple-instance configuration on the same node. Using the
PostgreSQL toolkit, you can configure multiple PostgreSQL toolkit packages to run on the same
node. Each copy of the PostgreSQL toolkit serves exactly one package. So, to configure multiple
packages, you must create separate directories, one per package, and configure each package
to run a unique database instance.
20 PostgreSQL Toolkit