Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pg_wrapper(1) [debian man page]

PG_WRAPPER(1)						 Debian PostgreSQL infrastructure					     PG_WRAPPER(1)

NAME
pg_wrapper - wrapper for PostgreSQL client commands SYNOPSIS
client-program [--cluster version/cluster] [...] (client-program: psql, createdb, dropuser, and all other client programs installed in /usr/lib/postgresql/version/bin). DESCRIPTION
This program is run only as a link to names which correspond to PostgreSQL programs in /usr/lib/postgresql/version/bin. It determines the configured cluster and database for the user and calls the appropriate version of the desired program to connect to that cluster and database, supplying any specified options to that command. The target cluster is selected by the following means, in descending order of precedence: 1. explicit specification with the --host option 2. explicit specification with the --cluster option 3. if the PGHOST environment variable is set, no further cluster selection is performed. The default PostgreSQL version and port number (from the command line, the environment variable PGPORT, or default 5432) will be used. 4. explicit specification with the PGCLUSTER environment variable 5. matching entry in ~/.postgresqlrc (see postgresqlrc(5)), if that file exists 6. matching entry in /etc/postgresql-common/user_clusters (see user_clusters(5)), if that file exists 7. If only one local cluster exists, that one will be selected. 8. If several local clusters exist, the one listening on the default port 5432 will be selected. If none of these rules match, pg_wrapper aborts with an error. OPTIONS
--cluster version/cluster cluster is either the name of a local cluster, or takes the form host:port for a remote cluster. If port is left empty (i. e. you just specify host:), it defaults to 5432. ENVIRONMENT
PGCLUSTER If $PGCLUSTER is set, its value (of the form version/cluster) specifies the desired cluster, similar to the --cluster option. However, if --cluster is specified, it overrides the value of $PGCLUSTER. PG_CLUSTER_CONF_ROOT This specifies an alternative base directory for cluster configurations. This is usually /etc/postgresql/, but for testing/development purposes you can change this to point to e. g. your home directory, so that you can use the postgresql-common tools without root privileges. FILES
/etc/postgresql-common/user_clusters stores the default cluster and database for users and groups as set by the administrators. $HOME/.postgresqlrc stores defaults set by the user himself. SEE ALSO
user_clusters(5), postgresqlrc(5) AUTHOR
Martin Pitt <mpitt@debian.org> Debian 2013-01-04 PG_WRAPPER(1)

Check Out this Related Man Page

cmruncl(1m)															       cmruncl(1m)

NAME
cmruncl - run a high availability cluster SYNOPSIS
cmruncl [-f] [-v] [-n node_name...] [-t | -w none] DESCRIPTION
cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster. To start a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration file. See access policy in cmquerycl(1m). This command should only be run when the cluster is not active on any of the configured nodes. This command verifies the network configu- ration before causing the nodes to start their cluster daemons. If a cluster is already running on a subset of the nodes, the cmrunnode command should be used to start the remaining nodes and force them to join the existing cluster. If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster. All nodes in the cluster must be available for the cluster to start unless a subset of nodes is specified. Options cmruncl supports the following options: -f Force cluster startup without warning message and continuation prompt that are printed with the -n option. -v Verbose output will be displayed. -t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet any external dependencies such as EMS resources, package subnets, and storage. -n node_name... Start the cluster daemon on the specified subset of node(s). -w none By default network probing is performed to check that the network connectivity is the same as when the cluster was config- ured. Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should only be used if this network configuration is known to be correct from a recent check. RETURN VALUE cmruncl returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Run the cluster daemon: cmruncl Run the cluster daemons on node1 and node2: cmruncl -n node1 -n node2 AUTHOR
cmruncl was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmruncl(1m)
Man Page