ocf:pgsql — Manages a PostgreSQL database instance
[OCF_RESKEY_pgctl=string] [OCF_RESKEY_start_opt=string] [OCF_RESKEY_ctl_opt=string] [OCF_RESKEY_psql=string] [OCF_RESKEY_pgdata=string] [OCF_RESKEY_pgdba=string] [OCF_RESKEY_pghost=string] [OCF_RESKEY_pgport=integer] [OCF_RESKEY_monitor_user=string] [OCF_RESKEY_monitor_password=string] [OCF_RESKEY_monitor_sql=string] [OCF_RESKEY_config=string] [OCF_RESKEY_pgdb=string] [OCF_RESKEY_logfile=string] [OCF_RESKEY_socketdir=string] [OCF_RESKEY_stop_escalate=integer] [OCF_RESKEY_rep_mode=string] [OCF_RESKEY_node_list=string] [OCF_RESKEY_restore_command=string] [OCF_RESKEY_archive_cleanup_command=string] [OCF_RESKEY_recovery_end_command=string] [OCF_RESKEY_master_ip=string] [OCF_RESKEY_repuser=string] [OCF_RESKEY_primary_conninfo_opt=string] [OCF_RESKEY_restart_on_promote=boolean] [OCF_RESKEY_tmpdir=string] [OCF_RESKEY_xlog_check_count=integer] [OCF_RESKEY_crm_attr_timeout=integer] [OCF_RESKEY_stop_escalate_in_slave=integer] [OCF_RESKEY_check_wal_receiver=boolean] pgsql [start | stop | status | monitor | monitor | promote | demote | notify | meta-data | validate-all | methods]
Path to pg_ctl command.
Start options (-o start_opt in pg_ctl). "-i -p 5432" for example.
Additional pg_ctl options (-w, -W etc..).
Path to psql command.
Path to PostgreSQL data directory.
User that owns PostgreSQL.
Hostname/IP address where PostgreSQL is listening
Port where PostgreSQL is listening
PostgreSQL user that pgsql RA will user for monitor operations. If it's not set pgdba user will be used.
Password for monitor user.
SQL script that will be used for monitor operations.
Path to the PostgreSQL configuration file for the instance.
Database that will be used for monitoring.
Path to PostgreSQL server log output file.
Unix socket directory for PostgeSQL
Number of shutdown retries (using -m fast) before resorting to -m immediate
Replication mode may be set to "async" or "sync" or "slave". They require PostgreSQL 9.1 or later. Once set, "async" and "sync" require node_list, master_ip, and restore_command parameters,as well as configuring postgresql for replication (in postgresql.conf and pg_hba.conf). "slave" means that RA only makes recovery.conf before starting to connect to Primary which is running somewhere. It dosen't need Master/Slave setting. It requires master_ip restore_command parameters.
All node names. Please separate each node name with a space. This is required for replication.
restore_command for recovery.conf. This is required for replication.
archive_cleanup_command for recovery.conf. This is used for replication and is optional.
recovery_end_command for recovery.conf. This is used for replication and is optional.
Master's floating IP address to be connected from hot standby. This parameter is used for "primary_conninfo" in recovery.conf. This is required for replication.
User used to connect to the master server. This parameter is used for "primary_conninfo" in recovery.conf. This is required for replication.
primary_conninfo options of recovery.conf except host, port, user and application_name. This is optional for replication.
If this is true, RA deletes recovery.conf and restarts PostgreSQL on promote to keep Timeline ID. It probably makes fail-over slower. It's recommended to set on-fail of promote up as fence. This is optional for replication.
Path to temporary directory. This is optional for replication.
Number of checking xlog on monitor before promote. This is optional for replication.
The timeout of crm_attribute forever update command. Default value is 5 seconds. This is optional for replication.
Number of shutdown retries (using -m fast) before resorting to -m immediate in Slave state. This is optional for replication.
If this is true, RA checks wal_receiver process on monitor and notify its status using "(resource name)-receiver-status" attribute. It's useful for checking whether PostgreSQL(Hot Standby) connects to primary. The attribute shows status as "normal" or "ERROR".