1. Installing and Configuring HA for PostgreSQL
Overview of Installing and Configuring HA for PostgreSQL
Planning the HA for PostgreSQL Installation and Configuration
PostgreSQL and Solaris Containers
Restriction for the Location of the Database Cluster
Restriction for the Listening Policy of the PostgreSQL Database Server
Restriction for the PostgreSQL postgresql.conf File
Restriction for the Password Policy for the HA for PostgreSQL Monitoring Database
Restriction for the PostgreSQL smf Service Name in an HA Container
Restriction for the PostgreSQL WAL File Shipping Without Shared Storage
Dependencies Between HA for PostgreSQL Components
Parameter File for HA for PostgreSQL
Configuration Requirements for the WAL File Shipping Without Shared Storage Configuration
Installing and Configuring PostgreSQL
How to Enable a PostgreSQL Database to Run in a Global Zone Configuration
How to Install and Configure PostgreSQL in a Global Zone
How to Enable a Zone to Run PostgreSQL in a Zone Configuration
How to Install and Configure PostgreSQL in a Zone
How to Enable a Zone to Run PostgreSQL in an HA Container Configuration
How to Install and Configure PostgreSQL in an HA Container
Verifying the Installation and Configuration of PostgreSQL
How to Verify the Installation and Configuration of PostgreSQL
Installing the HA for PostgreSQL Packages
How to Install the HA for PostgreSQL Packages
Registering and Configuring HA for PostgreSQL
Specifying Configuration Parameters for the PostgreSQL Resource
Specifying the Parameters for the Rolechanger Resource.
Specifying Configuration Files for WAL File Shipping Without Shared Storage
Preparing Your PostgreSQL Installation for Cluster Control
Creating and Enabling Resources for PostgreSQL
How to Create and Enable Resources for PostgreSQL
How to Modify Parameters in the HA for PostgreSQL Manifest
How to Remove a HA for PostgreSQL Resource From an HA Container
How to Create and Enable Resources for PostgreSQL Rolechanger
Verifying the HA for PostgreSQL Installation and Configuration
How to Verify the HA for PostgreSQL Installation and Configuration
How to Verify the Solaris Cluster HA for PostgreSQL WAL File Shipping Installation and Configuration
Tuning the HA for PostgreSQL Fault Monitor
Operation of the HA for PostgreSQL Parameter File
Operation of the Fault Monitor for HA for PostgreSQL
A. Files for Configuring Solaris Cluster HA for Solaris PostgreSQL Resources
B. Deployment Example: Installing PostgreSQL in the Global Zone
C. Deployment Example: Installing PostgreSQL in a Non-Global HA Container
D. Deployment Example: Installing PostgreSQL in a Non-Global Zone
E. Deployment Example: Installing PostgreSQL in the Global Zone Using WAL File Shipping
HA for PostgreSQL has a file named config that enables you to activate debugging for PostgreSQL resources. This file is in the /opt/SUNWscPostgreSQL/etc directory.
If your operating system is Solaris 10 and your PostgreSQL resource is dependent on a Solaris Container boot component resource, you are in an HA container configuration. In any other case, especially on a Solaris 9 system , you are in a global zone configuration.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
If debugging is inactive, daemon.notice is set in the file /etc/syslog.conf of the appropriate zone.
If debugging is active, daemon.debug is set in the file /etc/syslog.conf.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.debug;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
If your operating system is Solaris 9, type:
# pkill -1 syslogd
If your operating system is Solaris 10, type:
# svcadm refresh svc:/system/system-log:default
DEBUG=ALL
DEBUG=resource name
DEBUG=resource name,resource name, ...
# cat /opt/SUNWscPostgreSQL/etc/config # # Copyright 2006 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # Usage: # DEBUG=<RESOURCE_NAME> or ALL # DEBUG=ALL #
Note - To deactivate debugging, repeat step 1 to 6, changing daemon.debug to daemon.notice and changing the DEBUG variable to DEBUG=.